> > > So what if the worker thread posts a custom message to say the windows > > message queue. Surely that wouldn't cause the thread to be suspended. > > The GUI control then simply needs to know about the custom message, > > to process it correctly. Could this work, well on Windows at least? > > Using messages works on windows, but GTK is the most thread unsafe of > all widgetsets, when i tried to port an app that worked fine on > windows to GTK1/2 it was quite unstable, even now with a StringList > based messages queue there are times when the app simply crashes with > strange gtk resize warning but this is probably a GTK stability issue. > Being able to do GUI calls in secondary threads is nice to have.
I must confess I don't know too much of GTK1/2 but, for example if fpGUI is a framework from scratch indipendent from GTK, simply sending asynchronous messages to the main thread should work well ? It can elaborate the messages when the main loop will intercept them. In Windows it should work well; with Linux or other operating system I have no idea but I suppose yes. -- Antonio Sanguigni alias slapshot ---------------------------------------------------------------------- GioveLUG (Linux User Group) - http://www.giovelug.org Edupup (Educational distro) - http://www.edupup.org
