On 05/26/2014 05:02 PM, Dmitry Boyarintsev wrote:
Using a threading for GUI control is generally bad idea. Most of
standard GUI APIs (OSX, Windows, *nixes) have a note in 90% of their
functions - "do not use in multiple threads". Introducing threads to
handle GUI is potentially dangerous (due to all threading syncing
issues) and an overhead. Most of solutions doesn't really need
threads, as well as usage of threads increases resources consumption.
Some time ago I did some tests on that behalf.
Trying to do a multithreaded GUI (i.e. accessing multiple instances of
the OS'es widgets set from a single application) might be possible but a
lot of hassle and dangerous indeed. But it does make sense, as you would
allow multiple processors to work concurrently on the Library code (in
the application) and the WidgetSet code (outside of the application)
Here supposedly the more promising way is to start multiple "display"
applications and have them communicate in a decent way with a "business
logic" application..
-Michael
_______________________________________________
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
