Subject: RE: BeOS version of AbiWord (plz read)
From: Bruce Pearson (BruceP@wn.com.au)
Date: Sat Jul 08 2000 - 21:32:38 CDT
Hi Ithamar,
Under WIN32 the timer event goes through the message queue and are not
handled until there are no more messages in the queue. Therefore timer
events have a very low priority and are only executed one after the other.
The AbiWord code I assume was never meant to be re-entrant in this case.
Regards,
Bruce Pearson.
-----Original Message-----
From: owner-abiword-dev@abisource.com
[mailto:owner-abiword-dev@abisource.com]On Behalf Of Ithamar R. Adema
Sent: Sunday, 09 July, 2000 04:53
To: abiword-dev@abisource.com
Subject: BeOS version of AbiWord (plz read)
Hi All,
There are some relatively large issues still pending for the BeOS build, but
I think I found a big one (concerning all crashes entered into Bugzilla for
BeOS build) which happens to be related to the Timer mechanism used...
Now I'm no win32 expert (anymore), but I was wondering if it is possible in
Win32 to trigger 2 timer functions at virtually the same time.....
It looks like the screen redraw code path of AbiWord gets called from the
timer fire methods before an earlier fire was finished. This means that the
screen redraw code gets called before it was finished and I've got a feeling
that that code is not re-entrant.
Can anybody give a clear explanation on the timer mechanism and/or whether
AbiWord code is (meant to be) re-entrant?
Regards,
Ithamar.
This archive was generated by hypermail 2b25 : Sat Jul 08 2000 - 21:38:16 CDT