Pritpal Bedi escreveu:
It appears multi-threading support in QT
is sadly limited and does not go with all-the-powerful
offering in Harbour.
These are my first experiments and so I may be wrong.
I am trying to execute wvtext.prg with -mt option and
executing F10<New Window> which should be executed
in a separate thread. I can see new window opened but
then the inkey() loop, and also applctn loop, gets
cofused.
Yet I do not know what is causing such abnormality,
QT or gtqtc.c architect. QT documentation suggests that
appln always run in a single event loop.
If someone has any clues to this paradigm then please
speakup, otherwise, to me it seems to be show stopper.
I don´t tested gtqtc yet, but Qt have the class QEventLoop:
"Detailed Description
The QEventLoop class provides a means of entering and leaving an event loop.
At any time, you can create a QEventLoop object and call exec() on it to
start a local event loop. From within the event loop, calling exit()
will force exec() to return."
Can each Window in gtqtc have your own event loop ?
Regards,
Marcos Gambeta
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
