| |
|
|
- Page 1 - |
|
E.T. | there Yes here: [...] no reaction To verzeichnen was, would like I the Topic again aufgreifen. I Have there under "Mit Settimer funktionierts..." posted, the it with "Settimer" functions.
unfortunately scheind the still not so To his !!!
Have me today time hingesetzt, and my own Prog time again tested: and see there, sometime (so ex 250 Durchläufen) becomes too The Loop ("Mit Settimer funktionierts..." ) always faster (and faster, and faster...).
or ought to there one bow in the XProfan his ??
Werd's jetz time with a "Killtimer" in the Loop try... |
|
|
| Grüße aus Sachsen... Mario WinXP, Win7 (64 Bit),Win8(.1),Win10, Win 11, Profan 6 - X4, XPSE, und 'nen schwarzes, blinkendes Dingens, wo ich das alles reinschütte... | 11/09/10 ▲ |
|
|
|
|
« this Posting watts as Solution marked. » |
|
RGH | Hi, I have your Programmausschnitt time the Notwendige minimizes and to that complete Program extended:
The Timer versieht unbeirrt its service. too to over 400 Durchläufen remaining it with its 2 sec! The problem must well into others Programmteilen from you lying, The I Yes not exist and therefore its appeal removes have.
Also reicht it in this example, whom Timer once outside the Loop to settle and subsequently again To Remove (see Listing). The Timer runs such a long time, To it by a renewed SetTimer-commands supplant becomes or with KillTimer deleted becomes. (One SetTimer-commands contains too always a KillTimer-commands.)
Greeting Roland |
|
|
| Intel Duo E8400 3,0 GHz / 4 GB RAM / 1000 GB HDD - ATI Radeon HD 4770 512 MB - Windows 7 Home Premium 32Bit - XProfan X4 | 11/23/10 ▲ |
|
|
|
|
|
RGH | E.T. (09.11.10)
Werd's jetz time with a "Killtimer" in the Loop try...
the ought to in the doing the trouble solve:
The Number of possible Timer in the System is terminable and each SetTimer-commands beget You a new Timer. your KillTimer standing but outside the äußeren Loop, so that it inside the Loop never called becomes.
After one SetTimer must one KillTimer called go, before one new SetTimer called becomes!
Greeting Roland |
|
|
| Intel Duo E8400 3,0 GHz / 4 GB RAM / 1000 GB HDD - ATI Radeon HD 4770 512 MB - Windows 7 Home Premium 32Bit - XProfan X4 | 11/09/10 ▲ |
|
|
|
|
| RGH (09.11.10)
E.T. (09.11.10) Werd's jetz time with a "Killtimer" in the Loop try...
the ought to in the doing the trouble solve:
then is it systemisch seen one XProfan-bow. |
|
|
| |
|
|
|
RGH | iF (09.11.10)
then is But one XProfan-bow... at least systemisch seen.
well hardly: with SetTimer becomes one Timer created. the power one in the rule outside the incident-Loop, The z.B. too the Timer-incident abfragt. After termination the Loop must the Timer naturally again "entsorgt" go. the happens in the program but not. in the example is around the incident-Loop another further Loop. After this äußeren Loop standing first the KillTimer. as long as the program in the äußeren Loop is, becomes each appeal one Timer created, but none removes. first to the äußeren Loop becomes the lastly begot Timer removes. the KillTimer standing definitiv to the incorrect EndWhile!
another thing is the (yet undokumentierte) WaitInput n%. here ought to XProfan this intern begot Timer naturally against at the latest at next WaitInput n% again Remove. there must I once more look ...
Greeting Roland |
|
|
| Intel Duo E8400 3,0 GHz / 4 GB RAM / 1000 GB HDD - ATI Radeon HD 4770 512 MB - Windows 7 Home Premium 32Bit - XProfan X4 | 11/09/10 ▲ |
|
|
|
|
| Hm No we write together past, I plapper today evening time Why it one bow is. |
|
|
| |
|
|
|
| RGH (09.11.10)
iF (09.11.10) then is But one XProfan-bow... at least systemisch seen.
well hardly: with SetTimer becomes one Timer created.
The Help moreover says it Yes already: "Mit SetTimer becomes one Zeitgeber tuned"And "Es is thoroughly statthaft, whom Zeitgeber with a renewed SetTimer new einzustellen.".
the a is hold API and the others XProfan and E.T. I ment not around the API - but too The API... "existing timer, that timer wants be replaced".
One bow is But nevertheless sooner therefore, there one no Timerhandles sustain and therefore not of it go out must, itself circa such concern To must - particularly if The Help too of 1 by SetTimer einstellbaren Zeitgeber speaks.
Optimal would it still if SetTimer on itself self aufpasst and (solely-) intern used Handles too self treats. |
|
|
| |
|
|
|
E.T. | Jo, IF. so have I this too from the Help interprets. If man's wisely, isses Yes well (or not ). |
|
|
| Grüße aus Sachsen... Mario WinXP, Win7 (64 Bit),Win8(.1),Win10, Win 11, Profan 6 - X4, XPSE, und 'nen schwarzes, blinkendes Dingens, wo ich das alles reinschütte... | 11/10/10 ▲ |
|
|
|
|
E.T. | I must to Rückfragen unfortunately this issue again hervorkramen: after I (How Roland indeed aussagte) the Killtimer into "richtige" While-Loop gepackt have, reached me today a Mail, "warum because The SlideShow still starting To run..." (not any more so bad, but the "außenstehendem Betrachter" entgeht naturally nothing).
naturally same probiert, Loop rebuilt (everything with '***), so The times of SetTimer are to that "auslösen" transcribed go: CompileMarkSeparation now becomes Yes m.M. to the Timer too over ands over again tidy "gekillt", before one new staid becomes. The (mitgeschriebene) File brought really the following to that Vorschein:
Timer-Mitschnitt
Durchlauf : 1 = 2.0000sec Durchlauf : 2 = 2.0000sec Durchlauf : 3 = 2.0310sec ... Durchlauf : 191 = 2.0000sec Durchlauf : 192 = 2.0000sec Durchlauf : 193 = 0.7650sec Durchlauf : 194 = 0.9220sec Durchlauf : 195 = 0.9220sec Durchlauf : 196 = 0.8910sec Durchlauf : 197 = 0.9370sec
How one see can, is ex Durchlauf 193 suddenly a completely others display-Time (ShowTime% = Timer-Time) To vermerken. Screen saver & Monitor-Abschalt-Time I had vorsorglich everything deaktiviert (power my Prog anyhow, but sure is sure...).
is now the Timer "Wirr " or I or XProfan ??? or what could otherwise yet the waitinput durchbrechen and something like trigger ?? it was too no other Prog on the walk, which z.B. one wm_paint in my Program prompted having could...
somehow scheind the Timer "immer yet from the Reihe" To walk...
[OFFTOPIC]Gibts because To waitinput n already what new ??[/OFFTOPIC] |
|
|
| Grüße aus Sachsen... Mario WinXP, Win7 (64 Bit),Win8(.1),Win10, Win 11, Profan 6 - X4, XPSE, und 'nen schwarzes, blinkendes Dingens, wo ich das alles reinschütte... | 11/23/10 ▲ |
|
|
|
|
RGH | Hi, I have your Programmausschnitt time the Notwendige minimizes and to that complete Program extended:
The Timer versieht unbeirrt its service. too to over 400 Durchläufen remaining it with its 2 sec! The problem must well into others Programmteilen from you lying, The I Yes not exist and therefore its appeal removes have.
Also reicht it in this example, whom Timer once outside the Loop to settle and subsequently again To Remove (see Listing). The Timer runs such a long time, To it by a renewed SetTimer-commands supplant becomes or with KillTimer deleted becomes. (One SetTimer-commands contains too always a KillTimer-commands.)
Greeting Roland |
|
|
| Intel Duo E8400 3,0 GHz / 4 GB RAM / 1000 GB HDD - ATI Radeon HD 4770 512 MB - Windows 7 Home Premium 32Bit - XProfan X4 | 11/23/10 ▲ |
|
|
|
|
RGH | ... and The Variante with SetTimer n& runs unbeirrt too yet to over 800 Durchläufen: CompileMarkSeparation circa on your question to the Verwirrtheit something einzugrenzen: Weder windows yet XProfan shine here muddy To his.
Greeting Roland |
|
|
| Intel Duo E8400 3,0 GHz / 4 GB RAM / 1000 GB HDD - ATI Radeon HD 4770 512 MB - Windows 7 Home Premium 32Bit - XProfan X4 | 11/23/10 ▲ |
|
|
|
|
E.T. | thanks, Roland, that you tested have. Have now time my "Log-Datei" dahingehend extended, the too The Message, which the waitinput to that leave prompted, transcribed becomes:
log-File
Durchlauf : 191 = 2.0150sec >> Message: 275 | Window: 2294598 | wParam: 1 | lParam: 0 Durchlauf : 192 = 2.0160sec >> Message: 275 | Window: 2294598 | wParam: 1 | lParam: 0 Durchlauf : 193 = 0.3750sec >> Message: 273 | Window: 2294598 | wParam: 61808 | lParam: 0 Durchlauf : 194 = 0.8900sec >> Message: 273 | Window: 2294598 | wParam: 61808 | lParam: 0 Durchlauf : 195 = 0.8440sec >> Message: 273 | Window: 2294598 | wParam: 61808 | lParam: 0
The confounding Message is 273 (not 275, means not the Timer), gesendet on the Mainwindow. unfortunately can I in the momentum not nachschauen, what these Message means, can me time quick someone on The Sprünge help ??
thanks... |
|
|
| Grüße aus Sachsen... Mario WinXP, Win7 (64 Bit),Win8(.1),Win10, Win 11, Profan 6 - X4, XPSE, und 'nen schwarzes, blinkendes Dingens, wo ich das alles reinschütte... | 11/24/10 ▲ |
|
|
|
|
| |
|
| |
|
|