On 02/06/2014 02:13 PM, Hans-Peter Diettrich wrote:
When an application relies on high speed updates, it should serialize
these requests itself, as required, instead of leaving this to the
desktop manager and its arbitrary request scheduling.
Once again, this is not about serializing "requests" but about allowing
as much code as possible to be distributed on multiple CPUs as possible.
The "Widget Provider" (including X or whatever) does a fine job
serializing the requests to the graphics driver, as you can see when
doing the same stuff in multiple applications instead of multiple threads.
( On top of that you are right that serializing the GUI inputs (i.e. the
event queue handling) could benefit from multiple threads as well, as
with that e.g. events from a certain Windows could be handled in a
higher priority queue than others, but this is a different issue ).
-Michael
--
_______________________________________________
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
