Hi,
after implementing a SalTimerProc similar to 2.0.4 win32
implementation, I found a strange deadlock situation.
In my .3 source code, I was using a similar code which was not testing
the mbInTimerProc flag, thus allowing recursive calls to the timer
callback.
Now I discovered some situations leading to unpainted windows; e.g.
draw a circle object in a writer document, then right click on it and
choose 'lines...' from popup menu: the dialog opens but is not painted
at all, the same applies to OOo document window. Closing this dialog
restores painting for doc window.
debugging the code, showed that the second paint events is triggered by
a timer callback while the first one (again started from the timer
callback) is not complete.
what do you think?
is it safe for me to skip checking the mbInTimerProc flag as in .3
code? or should I investigate why the painting is taking a so long
time? or others?
TIA,
Bye,
Yuri Dario
/*
* member of TeamOS/2 - Italy
* http://www.os2power.com/yuri
* http://www.teamos2.it
*/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
