Project JEDI - Issue Tracker
Mantis Bugtracker

Viewing Issue Simple Details Jump to Notes ] View Advanced ] Issue History ] Print ]
ID Category Severity Reproducibility Date Submitted Last Update
0004319 [JEDI VCL] 00 JVCL Components tweak always 2007-12-18 06:03 2008-10-26 05:37
Reporter ZENsan View Status public  
Assigned To AHUser
Priority normal Resolution fixed  
Status resolved   Product Version Daily / GIT
Summary 0004319: TJvTimerThread incompatibility
Description TTimer works in this way:

You set Timer.Enabled := True;
And then if interval is one minute - it runs only after minute.
But TJvTimer runs immidietly when enabled is set to true.
To solve this problem I suggest to move some part code below to top of loop.
Additional Information JvTimer.pas [Line 181]

    if not ThreadClosed and not ThreadClosed and FOwner.FEnabled then
      if FOwner.SyncEvent then
          on E: Exception do
            FException := E;
    CurrentDuration := 0;
    while not ThreadClosed and (CurrentDuration < FInterval) do
      SleepEx(Step, False);
      Inc(CurrentDuration, Step);
Tags No tags attached.
Attached Files zip file icon [^] (1,254 bytes) 2008-07-25 02:45

- Relationships

-  Notes
ZENsan (reporter)
2007-12-23 08:14

This means that TJvTimer.Enabled method (SetEnabled) must NOT pause thread, but terminate (with wait if need).. And when when enabling - create thread again. Only then timer will work like good TTimer.
obones (administrator)
2008-02-20 09:17

I'm having a hard time understanding your note. Can you give me more details?
obones (administrator)
2008-07-23 07:22

Hello? Any comments?
ZENsan (reporter)
2008-07-25 02:48
edited on: 2008-07-25 02:49

First button is CodeGears's TTimer - and the appeareance how it MUST work. But all Jedi timer works wrong when in Threaded mode.

"{FOLLOWING BLOCK MUST BE FIRST!}" I suggested to change blocks, put delay in the beginning and execution after - as it must be.

anudedeus (reporter)
2008-08-07 05:35
edited on: 2008-08-07 05:43

I agree with ZENsan, just moving that block to the start would make the code equivalent to TTimer.
However, this will affect the functionallity of every single application that makes use of TThreadedTimer, as all developers using it already expect the event to happen when its status is set to true, not after 1,5 or 10 minutes later.
I, for example, would have huge problems if that happenned in my apps, so I'd prefer that the code stays at it is, but add a note/comment around it informing of this difference to the TTimer behaviour.

ZENsan (reporter)
2008-08-07 06:50

Maybe easier and better to add TJvTimerEventTime = (tetPre, tetPost)
Where property EventTime will determine how event is called (precalling or postcalling)
obones (administrator)
2008-10-10 05:05

Ok, thanks for the comments.
Issue available for anyone to look at, I quite like the idea of the enumeration indicating pre or post trigger
AHUser (developer)
2008-10-26 05:35

Added property EventTime default tetPre

- Issue History
Date Modified Username Field Change
2007-12-18 06:03 ZENsan New Issue
2007-12-23 08:14 ZENsan Note Added: 0014093
2008-02-20 09:17 obones Note Added: 0014184
2008-02-20 09:17 obones Status new => feedback
2008-07-23 07:22 obones Note Added: 0014438
2008-07-25 02:45 ZENsan File Added:
2008-07-25 02:48 ZENsan Note Added: 0014458
2008-07-25 02:49 ZENsan Note Edited: 0014458
2008-08-07 05:35 anudedeus Note Added: 0014476
2008-08-07 05:43 anudedeus Note Edited: 0014476
2008-08-07 05:44 anudedeus Issue Monitored: anudedeus
2008-08-07 06:50 ZENsan Note Added: 0014477
2008-10-10 05:05 obones Note Added: 0014809
2008-10-10 05:05 obones Status feedback => acknowledged
2008-10-26 05:35 AHUser Status acknowledged => resolved
2008-10-26 05:35 AHUser Fixed in Version => Daily / SVN
2008-10-26 05:35 AHUser Resolution open => fixed
2008-10-26 05:35 AHUser Assigned To => AHUser
2008-10-26 05:35 AHUser Note Added: 0014910

Mantis 1.1.6[^]
Copyright © 2000 - 2008 Mantis Group
Powered by Mantis Bugtracker