Hi Gary!
I found the source of the problem with the timer demo program:
the static libraries cause the timer to sleep when its owner
window loses focus.
To help you to fix the timer problem, I attached WinX.zip file,
which contains all what you need:
A tiny script to refresh your WinX dev. environment with:
Run deploy_WinX.txt before any compile.
(Well, not right out of the box: you have to change its extension
to DOS batch file)
As a bonus, I added the static version of WinX:
but...I never use static libraries in my programs (They are also installed by "deploy_WinX.**t").
Let me know if this solves the timer bug; in the mean time: Happy
Xbliting.
-- Bye! Guy
--
You received this message because you are subscribed to the Google Groups "xblite" group.
To unsubscribe from this group and stop receiving emails from it, send an email to xblite+un...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/xblite/bcb2e2e0-75b1-4923-9aac-cad0428a7b65n%40googlegroups.com.
-- Bye! Guy
Hi Gary!
I'm glad you solved your TIMER problem, but I'm skeptical about your solution.
Especially because I noticed a deprecated version of the WinXDoEvents function.
Indeed, I experimented passing the handle of an accelerator table to use as a default: "FUNCTION WinXDoEvents (passed_accel)".
10 years ago, it seemed to me like a good idea to pass an accelerator table to the event loop, but in fact, it was not.
Regarding the TIMER control, I never experienced any problems with it.Bye! Guy
--
You received this message because you are subscribed to the Google Groups "xblite" group.
To unsubscribe from this group and stop receiving emails from it, send an email to xblite+un...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/xblite/4587e549-4fb2-49ad-84cd-37ccc3d34730n%40googlegroups.com.