On 01/27/2011 08:56 PM, Marco van de Voort wrote:
This happens to be the case on Windows (where both plug into Windows message system, and thus have the same message loop), but not on other systems.
I never said anything otherwise. But this does not require that there could be a central unit and class that provides an API for this: a common function (that could be just Application.QueueAsyncCall) used by Application.QueueAsyncCall, TThread.Synchronize, TThread.Queue, and PostMessage, that handles the the communication with the GUI implementation (id present). Thus, In Windows - other than in Linux - , this Class would not implement it's own Event queue, but just use use the Windows Message queue.
-Michael -- _______________________________________________ Lazarus mailing list [email protected] http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
