RE: pyROOT - geometry again

Hello Michal,

In my mind the PyROOT creates the separate
"hidden" thread to manage the
ROOT event loop. If your application by some reason works in
the "wrong
thread" you may have observe the dead lock. See the
mail-thread:
https://lists.bnl.gov/pipermail/qt-root-l/2007
-January/000067.html 

It may help.


Best Regards
                         Valeri Fine
---------------
Brookhaven National Laboratory
Upton, NY 11973, USA
Phone: +1 631 344 7806
Fax:     +1 631 344 4206
E-mail: finebnl.gov

> -----Original Message-----
> From: owner-roottalkroot.cern.ch
[mailto:owner-roottalkroot.cern.ch]
On
> Behalf Of Michal Dwuznik
> Sent: Thursday, March 27, 2008 12:54 PM
> To: roottalkcern.ch
> Subject: Fwd: [ROOT] pyROOT - geometry again
> 
> ---------- Forwarded message ----------
> From: Michal Dwuznik <Michal.Dwuznikcern.ch>
> Date: 27-03-2008 17:20
> Subject: Re: [ROOT] pyROOT - geometry again
> To: Rene Brun <Rene.Bruncern.ch>
> 
> 
> Hi again Rene,
> 
> > >>  In case of pyroot, you can do the same.
However after top.Draw
you
> must exit
>  >  >>  python to get the mouse control in the
GL viewer.
>  >  >>
>  >  > Well, just a few days ago I remember
getting the _interactive_
> viewer
>  >  > from inside
>  >  > an interactive python shell (no matter if
python -i or ipython).
I
> was
>  >  > hit by "display-list registration
failed only recently, but, I
must
>  >  > admit I do not know what change triggered
that...
>  >  > Can I ask what do you mean by "exiting
python"? If I really
Ctrl-D
> the
>  >  > python shell I kill all the windows created
"from inside" this
> python
>  >  > session, including the 3D viewer created.
>  >  >
>  >
>  > I was assuming that you were executing your
python commands
following a
>  >   TPython::Prompt();
>  >
> 
> Ok, I understand now.
> 
>  Actually looking at
$ROOTSYS/tutorials/pyroot/shapes.py
> 
>  I observe the following -
>  running directly
> 
>  $python shapes.py (in the mentioned dir)
> 
>  I see a nice canvas with all the mentioned shapes, and
after
>  View->ViewWith->OpenGL
>  I get an entirely interactive 3D opengl viewer window,
but if I
replace
>  Draw('gl') with Draw('ogl') inside (which I, probably
wrong, assume
>  shall do the same thing
>  as rawing on the canvas, and then going to view with
opengl) I get a
>  "frozen" view I cannot manipulate. There's
obviously some difference
I
>  cound't grasp yet...
> 
> 
>  Regards
> 
> Michal