FAIK this is the expected behavior so, yes, I'd say the application is
relying on widgetset-depedent/buggy behavior.
In my experience Delphi behaves exactly the way you describe; maybe
your application is receiving window messages it shouldn't?
Best regards,
Flávio
On 6/21/07, Felipe Monteiro de Carvalho
<[EMAIL PROTECTED]> wrote:
Hi,
I have an graphics32 example using Application.OnIdle to draw images
as fast as possible.
It turns out that on Carbon widgetset OnIdle event will not be fired
unless something happens on the application, like moving the mouse
over it, unlike Delphi, where it is just fired non-stop.
So, I wonder if the application is relying in a widgetset dependent
behavior, or if the carbon interface should be fixed to have this
behavior on OnIdle.
thanks,
--
Felipe Monteiro de Carvalho
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
