AW: [ROOT] GUI, threads and CINT

From: Essel Dr.Hans-Georg (H.Essel@gsi.de)
Date: Thu Jun 13 2002 - 14:14:43 MEST


Hi Matt,
your requirements are pretty similar to some requirements we had when we
started the Go4 project, i.e. a non-blocking GUI with asynchronous graphical
updates from an independently running analysis. The solution was not that
easy, but Go4 v1.0 has been released recently at GSI for a first test phase
with real users. You may have a look to
http://go4.gsi.de
If you have further questions, you may contact us directly. 
Hans

-----Ursprüngliche Nachricht-----
Von: Matt Palmer [mailto:palmer@hep.phy.cam.ac.uk]
Gesendet: Donnerstag, 13. Juni 2002 12:54
An: roottalk@pcroot.cern.ch
Betreff: [ROOT] GUI, threads and CINT


Hi,
I would like to know if the following is possible:
I want to write a GUI for some analysis code that is interpreted by CINT.  
This analysis code typically sits in a loop, so rarely exits.  I would like 
to present status information, logging etc in a GUI.  So, in order for the 
GUI to remain responsive to the user, I assume I would need to run the GUI
in 
a separate thread.  Is it enough to simply create a separate thread and then

within that, create my main GUI object (a sub-class of TGMainFrame) ?  I 
would then presumably make this object global so it can be accessed in the 
analysis code.

I was worried by the statement in the TThread documentation saying that CINT

will block all threads while it executes.  Is this still true?  If so, would

moving the analysis code to compiled (something that I'm probably unable to 
do) code fix this?  Is there any other way of doing this which I've totally 
missed?

Thanks very much

Matt



This archive was generated by hypermail 2b29 : Sat Jan 04 2003 - 23:50:56 MET