visualpython-users

Re: [Visualpython-users] Switch from vpython 3 to vpython 4

[<fre...@gb...>]

On mercredi 26 d=E9cembre 2007, Bruce Sherwood wrote:

> Thanks for the detailed report.
>
> crossproduct and planar: These had the same problem as some other
> examples -- the workaround is simply to add rate(100) immediately
> following the while statement. I simply failed to catch these further
> examples of the problem of quitting from a tight loop. (But I should say
> I only saw a problem with quitting, not any sluggishness.) I've checked
> in corrected versions to CVS.
>
> glinfo: It's not clear to me whether this has ever worked properly on
> Linux. Note the statement in the program, "This test of OpenGL options
> is useful mainly on Windows."
>
> randombox: I believe the poor performance is due to incomplete
> implementation of improved handling of lighting of boxes. There needs to
> be variable level of detail in splitting a side into a number of
> triangles, dependent on how far away the box is, as is in the case for
> spheres. I'm aware of the issue. As was the case with curve, box needs
> work to cut the render speed significantly.

Ok.

> texturetest and Tk-Visual: I can't reproduce any problem with these
> examples.

Strange... BTW, you didn't tell me how (if it is possible) to quit a=20
vpython app without using the exit button?

> I'm delighted that the changes made a big improvement in the performance
> of your app.

:o)

=2D-=20
   Fr=E9d=E9ric

   http://www.gbiloba.org

Re: [Visualpython-users] Camera point of vue

[Bruce S. <Bru...@nc...>]

Study the program "movecamera.py" in the contributed section of 
vpython.org. I think it will answer your question.

Bruce Sherwood

Frédéric Mantegazza wrote:
> Hello,
>
> I have a question related to the vpython camera usage.
>
> I simulate a photo panohead, where a DSLR is fixed. I would like to 
> simulate the view I have from that DSLR. So, I need to set the vpython 
> camera position, and update the direction it is point at.
>
> But I don't know how to do that. Using the center attribute only sets the 
> point the camera *looks*.
>
> Is there a way to set the camera position, say to (0, 0, 0), and only use 
> the forward attribute to rotate it? A 'from' camera attribute could be 
> usefull...
>
> Thanks,
>
>   

Re: [Visualpython-users] Switch from vpython 3 to vpython 4

[Bruce S. <Bru...@nc...>]

Thanks for the detailed report.

crossproduct and planar: These had the same problem as some other 
examples -- the workaround is simply to add rate(100) immediately 
following the while statement. I simply failed to catch these further 
examples of the problem of quitting from a tight loop. (But I should say 
I only saw a problem with quitting, not any sluggishness.) I've checked 
in corrected versions to CVS.

glinfo: It's not clear to me whether this has ever worked properly on 
Linux. Note the statement in the program, "This test of OpenGL options 
is useful mainly on Windows."

randombox: I believe the poor performance is due to incomplete 
implementation of improved handling of lighting of boxes. There needs to 
be variable level of detail in splitting a side into a number of 
triangles, dependent on how far away the box is, as is in the case for 
spheres. I'm aware of the issue. As was the case with curve, box needs 
work to cut the render speed significantly.

texturetest and Tk-Visual: I can't reproduce any problem with these 
examples.

I'm delighted that the changes made a big improvement in the performance 
of your app.

Bruce Sherwood

Frédéric Mantegazza wrote:
> On dimanche 23 décembre 2007, Frédéric Mantegazza wrote:
>
> Ok, I tested the new beta:
>
>   
>> - controlstest.py: closing the main window using the window x box only
>>                    closes the 3D view, and freezes the main view.
>>     
>
> Fixed.
>
>   
>> - crossproduct.py: 100% CPU usage. very Slow.
>>     
>
> No change.
>
>   
>> - glinfo.py: freezes after printing the infos
>>     
>
> No change.
>
>   
>> - planar.py: CPU 100% usage
>>     
>
> No change.
>
>   
>> - randombox.py: 80% CPU usage
>>     
>
> 50% only.
>
>   
>> - texturetest.py: freeze if closed using the window x box
>>     
>
> No change.
>
>   
>> - tictac.py: 100% CPU usage
>>     
>
> Fixed.
>
>   
>> - Tk-Visual.py: freezes if 3D view closed using the window x box
>>     
>
> No change.
>
>   
>> - toroid_drag.py: 100% CPU usage
>>     
>
> Fixed.
>
>   
>> 3) my app is much more slower (drag/move), and I'hve now 60-70% CPU
>> usage (vs 10-15% with vpython 3). It also freezes if I close the 3D view
>> using the window x box.
>>     
>
> My 3D view is now as quick as with previous versions!
>
> Great job :o)
>
>   

Re: [Visualpython-users] 4.beta21

[Bruce S. <Bru...@nc...>]

I don't know why you conclude that graphing has been neglected or even 
abandoned. Significant effort was expended to make graphing as fast on 
Visual 4 as it was on Visual 3. Moreover, the new points object makes 
gdot plots much faster than before.

Graphing does work on Windows and (Ubuntu) Linux. It is possible that 
you need to update your graphics card driver.

Because graphing works as well or better in Visual 4 as it did in Visual 
3, making improvements to this part of Visual necessarily must have much 
lower priority for my own work than actual problem areas (e.g. poor 
performance for some kinds of scenes). However, if you feel strongly 
about implementing for example PostScript output in order to permit 
high-quality printing, please go ahead and do this work. The graphing 
module is written in Python, not C++, and all you need to do is generate 
a PostScript text file based on the objects created for the graph.

Bruce Sherwood

Jose Antonio Martin H wrote:
> Dear Bruce,
>  
> What about : Plotting Graphs of Functions or Data
>  
> It seems that this thread of development has been left ?
>  
> I have tested the beta version on windows xp, but  I get crtical 
> erros, not only not displaying the plot, indeed the program crashes, 
> that is, this module does not work on this version..
>  
> The module for plotting is very usefull, and I think it should not be 
> abandoned, istead improving the plotting module will be very usefull, 
> for instance, adding the possibility to export the plot to a graphics 
> file or to export the plot into a plot for another graphing tool in 
> order to improve its functionality.
>  
> Why not to add 3D ploting capabilities ? like surfaces ?
>  
> For instance, matplotlib does a good job, but it is intended not for 
> realtime graphics but instead for final graph production.
>  
> Best whishes, and happy new year for all.
>  
> jose.
>  
> ** 
> ** 
> ----- Original Message -----
> From: "Bruce Sherwood" <Bru...@nc... 
> <mailto:Bru...@nc...>>
> To: "vpusers" <vis...@li... 
> <mailto:vis...@li...>>
> Sent: Tuesday, December 25, 2007 7:08 AM
> Subject: [Visualpython-users] 4.beta21
>
> > Now available at sourceforge.net is VPython 4.beta21 for Windows and 
> Linux:
> >
> > *Default window now 600x600, which includes titlebar, toolbar, and
> > borders. For the first time on Linux, you can place a window at a
> > specific desired x,y position, as was always possible on Windows.
> > *Now display max 10000 points of a curve (old Visual did max 1000; see
> > below).
> > *Implement and document curve.retain=N, meaning retain only the N most
> > recently appended points.This is a convenient way to leave a tail 
> behind
> > a moving object.
> > *Significantly improved tuning of the balance between the computational
> > thread and the render thread.
> > *Implemented toolbar option to restore to standard values center,
> > forward, and up.
> > *Documentation for new display.get_titlebar_height(),
> > display.get_toolbar_height().
> > *Added rate statements to tictac.py, hanoi.py, and toroid_drag.py as a
> > workaround for a problem with quitting a program with a loop that
> > contains very little computation. (I haven't yet figured out why it is
> > difficult to quit such programs.)
> > *The statement scene.show_rendertime = True triggers a display in the
> > bottom left corner of the screen of the cycle time (milliseconds 
> between
> > rendering of the scene) and render time (milliseconds required to 
> render
> > the scene). The cycle time minus the render time is the approximate
> > number of milliseconds in the cycle devoted to your Python computations.
> >
> > All of the standard example programs seem to run well on both Windows
> > and Ubuntu Linux except for stonehenge.py which is sluggish compared to
> > the production version. Rendering of the complex scene is slow on my 
> not
> > very powerful Windows/Linux laptop (1 GHz, 500 MB). I hope to study 
> this
> > further and try to bring the performance up to expectations.
> >
> > I would appreciate it if some adventuresome souls would try this
> > version, as a significant number of outstanding issues have been 
> addressed.
> >
> > I should offer some explanation of the need to display a maximum number
> > of points in a curve. In Visual 3 a maximum of 1000 points were
> > displayed for a curve, no matter how many points it actually contained.
> > The points chosen to display were spaced as uniformly as possible over
> > the entire curve. The bad thing about this scheme is that a curve 
> with a
> > very large number of points may display in a bizarre way. For example,
> > if you repeatedly add points to a curve representing the elliptical
> > orbit of a planet, eventually you'll see points connected to each other
> > by straight-line segments from one side of the ellipse to another, 
> which
> > is very confusing. However, if we try to display all of the points, the
> > longer the orbit runs the slower the rendering becomes. Some very 
> simple
> > standard orbit programs ran unacceptably slowly. So I've reverted to 
> the
> > old scheme of displaying only up to a maximum number of points. But
> > recognizing the large increase in speed of computers since the
> > beginnings of VPython in 2000, I made the limit 10000 instead of 1000,
> > which seems to work fine and makes it 10 times less likely you'll see
> > strange displays of a many-point curve. The philosophy underlying this
> > kind of compromise was articulated very clearly by David Scherer, the
> > originator of VPython, as "Go fast, be wrong!" The effect is that one
> > gets almost always sensible and good performance, at the penalty of
> > sometimes going wrong.
> >
> > There is a highly technical problem which has been identified but for
> > which there is currently no known solution. In the old Numeric module
> > used in Visual 3, sqrt(5.5) was a float, but in numpy used in the beta
> > version sqrt(5.5) is numpy.float64, with the highly unfortunate result
> > that sqrt(5.5)*vector isn't a VPython vector but rather a numpy array.
> > I've asked for help on this from both the numpy and Boost discussion
> > lists but so far not gotten any assistance. In some existing physics
> > programs the effect is to double the time required to update an orbit,
> > so this is serious. I'll mention that vector*sqrt(5.5) works fine -- 
> the
> > result is a vector.
> >
> > Bruce
> >
> > 
> -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Microsoft
> > Defy all challenges. Microsoft(R) Visual Studio 2005.
> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > _______________________________________________
> > Visualpython-users mailing list
> > Vis...@li... 
> <mailto:Vis...@li...>
> > https://lists.sourceforge.net/lists/listinfo/visualpython-users
> >
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> ------------------------------------------------------------------------
>
> _______________________________________________
> Visualpython-users mailing list
> Vis...@li...
> https://lists.sourceforge.net/lists/listinfo/visualpython-users
>   

[Visualpython-users] Camera point of vue

[<fre...@gb...>]

Hello,

I have a question related to the vpython camera usage.

I simulate a photo panohead, where a DSLR is fixed. I would like to=20
simulate the view I have from that DSLR. So, I need to set the vpython=20
camera position, and update the direction it is point at.

But I don't know how to do that. Using the center attribute only sets the=20
point the camera *looks*.

Is there a way to set the camera position, say to (0, 0, 0), and only use=20
the forward attribute to rotate it? A 'from' camera attribute could be=20
usefull...

Thanks,

=2D-=20
   Fr=E9d=E9ric

   http://www.gbiloba.org

Re: [Visualpython-users] Switch from vpython 3 to vpython 4

[<fre...@gb...>]

On dimanche 23 d=E9cembre 2007, Fr=E9d=E9ric Mantegazza wrote:

Ok, I tested the new beta:

> - controlstest.py: closing the main window using the window x box only
>                    closes the 3D view, and freezes the main view.

=46ixed.

> - crossproduct.py: 100% CPU usage. very Slow.

No change.

> - glinfo.py: freezes after printing the infos

No change.

> - planar.py: CPU 100% usage

No change.

> - randombox.py: 80% CPU usage

50% only.

> - texturetest.py: freeze if closed using the window x box

No change.

> - tictac.py: 100% CPU usage

=46ixed.

> - Tk-Visual.py: freezes if 3D view closed using the window x box

No change.

> - toroid_drag.py: 100% CPU usage

=46ixed.

> 3) my app is much more slower (drag/move), and I'hve now 60-70% CPU
> usage (vs 10-15% with vpython 3). It also freezes if I close the 3D view
> using the window x box.

My 3D view is now as quick as with previous versions!

Great job :o)

=2D-=20
   Fr=E9d=E9ric

   http://www.gbiloba.org

Re: [Visualpython-users] Switch from vpython 3 to vpython 4

[<fre...@gb...>]

On mardi 25 d=E9cembre 2007, Bruce Sherwood wrote:

> Do try the new 4.beta21, which addresses many problems, some of which
> are those you mention. In particular, the problems with tictac.py and
> toroid_drag.py (and also hanoi.py) have to do with loops containing
> almost no computation, a case where the multithreading is not doing the
> right job for reasons not understood. As a workaround, those programs
> now contain rate statements, which don't harm perfomance but make the
> programs work properly.
>
> As mentioned in the announcement of 4.beta21, there are various
> performance problems with rendering, and I hope to address them. I've
> already made a big improvement in handling curves containing large
> numbers of points.

Ok, I'll give it a try.

> At the moment there is no way to texture the inside of a sphere, but
> that's an interesting suggestion. I suppose you've already noticed that
> in either Visual 3 or 4 you can move inside an object.

Yes, I use this behaviour: I'm in a big sphere, simulating the sky. In=20
fact, when I apply the texture on it, I can see it rom the inside. So,=20
there is nothing to do :o) The texture is reversed, but it is not really a=
=20
problem.

=2D-=20
   Fr=E9d=E9ric

   http://www.gbiloba.org

Re: [Visualpython-users] 4.beta21

[Jose A. M. H <jam...@fd...>]

Dear Bruce,=20

What about : Plotting Graphs of Functions or Data

It seems that this thread of development has been left ?

I have tested the beta version on windows xp, but  I get crtical erros, =
not only not displaying the plot, indeed the program crashes, that is, =
this module does not work on this version..

The module for plotting is very usefull, and I think it should not be =
abandoned, istead improving the plotting module will be very usefull, =
for instance, adding the possibility to export the plot to a graphics =
file or to export the plot into a plot for another graphing tool in =
order to improve its functionality.

Why not to add 3D ploting capabilities ? like surfaces ?=20

For instance, matplotlib does a good job, but it is intended not for =
realtime graphics but instead for final graph production.

Best whishes, and happy new year for all.=20

jose.



----- Original Message -----=20
From: "Bruce Sherwood" <Bru...@nc...>
To: "vpusers" <vis...@li...>
Sent: Tuesday, December 25, 2007 7:08 AM
Subject: [Visualpython-users] 4.beta21


> Now available at sourceforge.net is VPython 4.beta21 for Windows and =
Linux:
>=20
> *Default window now 600x600, which includes titlebar, toolbar, and=20
> borders. For the first time on Linux, you can place a window at a=20
> specific desired x,y position, as was always possible on Windows.
> *Now display max 10000 points of a curve (old Visual did max 1000; see =

> below).
> *Implement and document curve.retain=3DN, meaning retain only the N =
most=20
> recently appended points.This is a convenient way to leave a tail =
behind=20
> a moving object.
> *Significantly improved tuning of the balance between the =
computational=20
> thread and the render thread.
> *Implemented toolbar option to restore to standard values center,=20
> forward, and up.
> *Documentation for new display.get_titlebar_height(),=20
> display.get_toolbar_height().
> *Added rate statements to tictac.py, hanoi.py, and toroid_drag.py as a =

> workaround for a problem with quitting a program with a loop that=20
> contains very little computation. (I haven't yet figured out why it is =

> difficult to quit such programs.)
> *The statement scene.show_rendertime =3D True triggers a display in =
the=20
> bottom left corner of the screen of the cycle time (milliseconds =
between=20
> rendering of the scene) and render time (milliseconds required to =
render=20
> the scene). The cycle time minus the render time is the approximate=20
> number of milliseconds in the cycle devoted to your Python =
computations.
>=20
> All of the standard example programs seem to run well on both Windows=20
> and Ubuntu Linux except for stonehenge.py which is sluggish compared =
to=20
> the production version. Rendering of the complex scene is slow on my =
not=20
> very powerful Windows/Linux laptop (1 GHz, 500 MB). I hope to study =
this=20
> further and try to bring the performance up to expectations.
>=20
> I would appreciate it if some adventuresome souls would try this=20
> version, as a significant number of outstanding issues have been =
addressed.
>=20
> I should offer some explanation of the need to display a maximum =
number=20
> of points in a curve. In Visual 3 a maximum of 1000 points were=20
> displayed for a curve, no matter how many points it actually =
contained.=20
> The points chosen to display were spaced as uniformly as possible over =

> the entire curve. The bad thing about this scheme is that a curve with =
a=20
> very large number of points may display in a bizarre way. For example, =

> if you repeatedly add points to a curve representing the elliptical=20
> orbit of a planet, eventually you'll see points connected to each =
other=20
> by straight-line segments from one side of the ellipse to another, =
which=20
> is very confusing. However, if we try to display all of the points, =
the=20
> longer the orbit runs the slower the rendering becomes. Some very =
simple=20
> standard orbit programs ran unacceptably slowly. So I've reverted to =
the=20
> old scheme of displaying only up to a maximum number of points. But=20
> recognizing the large increase in speed of computers since the=20
> beginnings of VPython in 2000, I made the limit 10000 instead of 1000, =

> which seems to work fine and makes it 10 times less likely you'll see=20
> strange displays of a many-point curve. The philosophy underlying this =

> kind of compromise was articulated very clearly by David Scherer, the=20
> originator of VPython, as "Go fast, be wrong!" The effect is that one=20
> gets almost always sensible and good performance, at the penalty of=20
> sometimes going wrong.
>=20
> There is a highly technical problem which has been identified but for=20
> which there is currently no known solution. In the old Numeric module=20
> used in Visual 3, sqrt(5.5) was a float, but in numpy used in the beta =

> version sqrt(5.5) is numpy.float64, with the highly unfortunate result =

> that sqrt(5.5)*vector isn't a VPython vector but rather a numpy array. =

> I've asked for help on this from both the numpy and Boost discussion=20
> lists but so far not gotten any assistance. In some existing physics=20
> programs the effect is to double the time required to update an orbit, =

> so this is serious. I'll mention that vector*sqrt(5.5) works fine -- =
the=20
> result is a vector.
>=20
> Bruce
>=20
> =
-------------------------------------------------------------------------=

> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Visualpython-users mailing list
> Vis...@li...
> https://lists.sourceforge.net/lists/listinfo/visualpython-users
>

Re: [Visualpython-users] compiling vpython 4 (was Crash when quit)

[Bruce S. <Bru...@nc...>]

There are two different issues: where is Python, and where will visual 
be installed. If you said --prefix=/usr/local but didn't specify that 
Python was to be found in /usr, you would have a problem. From the Linux 
download page at vpython.org:

*which python* (find out where Python is located)*
*   Make a note of the /prefix/ preceding /bin/python, such as /usr or 
/usr/local.
(a) If /prefix/ is /usr/local, execute
     *../visual-x.x.x/configure*
(b) If /prefix/ is something else, and Visual can go into 
prefix/lib/python/site-packages, execute
   *  ../visual-x.x.x/configure --prefix=*/prefix/
(c) If you want to use a different version of Python than the one found 
with "which python",
   or (b) is not appropriate, specify both the particular Python and 
where to install Visual:
   *   PYTHON=/somewhere1/bin/python ../visual-x.x.x/configure 
--prefix=/somewhere2*
   If "somewhere1" and "somewhere2" are different, you must also add the 
"somewhere2"
   directory to Python's module search path. For details, at 
www.python.org <http://www.python.org> read section 4.1
   (Modifying Python's Search Path) in the section Installing Python 
Modules of the Python 2.3
   on-line documentation.

Bruce Sherwood

Frédéric Mantegazza wrote:
> On mardi 25 décembre 2007, Bruce Sherwood wrote:
>
>   
>> Thanks for the detailed report. I don't expect to be able very soon to
>> address the issue of better reporting of precisely which libraries are
>> missing, but some day.... I'm puzzled about the boost libraries, as I
>> thought those were checked.
>>     
>
> Ok.
>
>   
>> The problem with numpy sounds like an error 
>> in issuing the configure command: you need configure --prefix=/usr if
>> Python and its site-packages are in /usr. As is documented in the
>> install instructions, by default configure assumes the target Python is
>> in /usr/local.
>>     
>
> I understand, but I want to install manually compiled packages 
> in /usr/local, so I set --prefix to that dir. I may have to give another 
> param to tell configure to search dependent libs? Anyway, it is not a big 
> problem.
>
>   

Re: [Visualpython-users] Switch from vpython 3 to vpython 4

[<fre...@gb...>]

On mardi 25 d=E9cembre 2007, Bruce Sherwood wrote:

> Could you give a more complete statement of your suggestion? It is
> already the case that there are several different anaglyph modes
> (redblue, redcyan). Are you saying that given particular red-cyan
> filters, whose "red" and "cyan" are of course just approximations, you
> might hope to achieve better color separation by using red+some+green"
> (say) and "cyan+some_red"?

Yes, that's the point. I can also be a work-arround for non-calibrated=20
monitors...

> Note that while red-blue has large=20
> separation, it is essentially monochrome, whereas the red-cyan version
> provides some colors by adding white to both views, thus giving pastel
> colors but avoiding the case of a red ball having no image for the cyan
> eye.

I didn't know that. Stereo is really a very interesting point, and I'm sure=
=20
in will be the next image revolution.

> Some months ago someone pointed out various failings of the current
> anaglyph implementation (for which I'm responsible), and at some point
> I'd like to follow up on that critique. But it's currently VERY low
> priority.....

I understand!

=2D-=20
   Fr=E9d=E9ric

   http://www.gbiloba.org

Re: [Visualpython-users] compiling vpython 4 (was Crash when quit)

[<fre...@gb...>]

On mardi 25 d=E9cembre 2007, Bruce Sherwood wrote:

> Thanks for the detailed report. I don't expect to be able very soon to
> address the issue of better reporting of precisely which libraries are
> missing, but some day.... I'm puzzled about the boost libraries, as I
> thought those were checked.

Ok.

> The problem with numpy sounds like an error=20
> in issuing the configure command: you need configure --prefix=3D/usr if
> Python and its site-packages are in /usr. As is documented in the
> install instructions, by default configure assumes the target Python is
> in /usr/local.

I understand, but I want to install manually compiled packages=20
in /usr/local, so I set --prefix to that dir. I may have to give another=20
param to tell configure to search dependent libs? Anyway, it is not a big=20
problem.

=2D-=20
   Fr=E9d=E9ric

   http://www.gbiloba.org

Re: [Visualpython-users] Switch from vpython 3 to vpython 4

[Bruce S. <Bru...@nc...>]

Could you give a more complete statement of your suggestion? It is 
already the case that there are several different anaglyph modes 
(redblue, redcyan). Are you saying that given particular red-cyan 
filters, whose "red" and "cyan" are of course just approximations, you 
might hope to achieve better color separation by using red+some+green" 
(say) and "cyan+some_red"? Note that while red-blue has large 
separation, it is essentially monochrome, whereas the red-cyan version 
provides some colors by adding white to both views, thus giving pastel 
colors but avoiding the case of a red ball having no image for the cyan eye.

Some months ago someone pointed out various failings of the current 
anaglyph implementation (for which I'm responsible), and at some point 
I'd like to follow up on that critique. But it's currently VERY low 
priority.....

Bruce Sherwood

Frédéric Mantegazza wrote:
> Another question (more a feature request): could it be possible to 
> precisely select the color (giving RGB values) for stereo mode? That way, 
> it would be possible to adjust it according to the glasses used...
>
>   

Re: [Visualpython-users] Switch from vpython 3 to vpython 4

[Bruce S. <Bru...@nc...>]

Do try the new 4.beta21, which addresses many problems, some of which 
are those you mention. In particular, the problems with tictac.py and 
toroid_drag.py (and also hanoi.py) have to do with loops containing 
almost no computation, a case where the multithreading is not doing the 
right job for reasons not understood. As a workaround, those programs 
now contain rate statements, which don't harm perfomance but make the 
programs work properly.

As mentioned in the announcement of 4.beta21, there are various 
performance problems with rendering, and I hope to address them. I've 
already made a big improvement in handling curves containing large 
numbers of points.

At the moment there is no way to texture the inside of a sphere, but 
that's an interesting suggestion. I suppose you've already noticed that 
in either Visual 3 or 4 you can move inside an object.

Bruce Sherwood

Frédéric Mantegazza wrote:
> Ok, so I'm now using vpython 4...
>
> 1) it fixed the crash when quit/hide display :o))))
>
> 2) all examples passed, but some have strange behaviour:
>
> - controlstest.py: closing the main window using the window x box only 
>                    closes the 3D view, and freezes the main view.
> - convex.py: closing the window using the window x box freezes.
> - crossproduct.py: 100% CPU usage. very Slow.
> - glinfo.py: freezes after printing the infos
> - planar.py: CPU 100% usage
> - randombox.py: 80% CPU usage
> - texturetest.py: freeze if closed using the window x box
> - tictac.py: 100% CPU usage
> - Tk-Visual.py: freezes if 3D view closed using the window x box
> - toroid_drag.py: 100% CPU usage
>
> 3) my app is much more slower (drag/move), and I'hve now 60-70% CPU usage 
> (vs 10-15% with vpython 3). It also freezes if I close the 3D view using 
> the window x box.
>
> I have a general question: how do I cleanly stop the vpython mainloop from 
> my app? I mean, without the need to click on the GTK close button?
>
> Last, I'm very impressed by the texture feature: in fact, this is why I 
> switched to vpython 4. I'm developping a pano head simulation, and I want 
> to apply a 360°x180° pano on a vpython sphere, to simulate the real word. 
> BTW, is it possible to map the image *inside* a sphere? 
>
>   
>
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> ------------------------------------------------------------------------
>
> _______________________________________________
> Visualpython-users mailing list
> Vis...@li...
> https://lists.sourceforge.net/lists/listinfo/visualpython-users
>   

Re: [Visualpython-users] compiling vpython 4 (was Crash when quit)

[Bruce S. <Bru...@nc...>]

Thanks for the detailed report. I don't expect to be able very soon to 
address the issue of better reporting of precisely which libraries are 
missing, but some day.... I'm puzzled about the boost libraries, as I 
thought those were checked. The problem with numpy sounds like an error 
in issuing the configure command: you need configure --prefix=/usr if 
Python and its site-packages are in /usr. As is documented in the 
install instructions, by default configure assumes the target Python is 
in /usr/local.

Bruce Sherwood

Frédéric Mantegazza wrote:
> On dimanche 23 décembre 2007, Bruce Sherwood wrote:
>
>   
>> I think some of your missing libraries are included in some of those
>> listed in the INSTALL file, but if you find that not to be the case I'd
>> appreciate knowing so that the file can be improved.
>>     
>
> In fact, the only package missing was gtkglextmm; all others where 
> correctly installed. The problem comes from the configure script. When it 
> call pkg-config, to check mising packages, it gets:
>
> configure:19706: checking for pkg-config
> configure:19724: found /usr/bin/pkg-config
> configure:19736: result: /usr/bin/pkg-config
> configure:19765: checking pkg-config is at least version 0.9.0
> configure:19768: result: yes
> configure:19792: checking for GTK
> configure:19800: $PKG_CONFIG --exists --print-errors "gtkglextmm-1.2 >= 1.2
>   pangoft2 glibmm-2.4 pangomm-1.4 libglademm-2.4 freetype2"
> Package gtkglextmm-1.2 was not found in the pkg-config search path.
> Perhaps you should add the directory containing `gtkglextmm-1.2.pc'
> to the PKG_CONFIG_PATH environment variable
> No package 'gtkglextmm-1.2' found
> configure:19803: $? = 1
> configure:19818: $PKG_CONFIG --exists --print-errors "gtkglextmm-1.2 >= 1.2 
> pangoft2 glibmm-2.4 pangomm-1.4 libglademm-2.4 freetype2"
> Package gtkglextmm-1.2 was not found in the pkg-config search path.
> Perhaps you should add the directory containing `gtkglextmm-1.2.pc'
> to the PKG_CONFIG_PATH environment variable
> No package 'gtkglextmm-1.2' found
> configure:19821: $? = 1
> No package 'gtkglextmm-1.2' found
> configure:19849: result: no
> configure:19851: error: gtkglextmm 1.2, pangoft2, glibmm-2.4, and 
> pangomm-1.4 libglademm-2.4 are required on Unix-like systems
>
> As you can see, it outputs all libs, even if the only missing is 
> gtkglextmm. I compiled and installed it, and it now works fine :o)
>
> But during the compilation phase, I still had problems of missing libs: 
> libboost-python (and -thread) is not checked in the configure. Once 
> installed, it works (it was the same in previous vpython versions).
>
> And I have a another problem: vpython can't find the numpy/arrayobject.h 
> (imported from include/python/num_util.hpp). This file is in:
>
> python-numpy:
>    usr/lib/python2.4/site-packages/numpy/core/include/numpy/arrayobject.h
>
> But the configure script found an incorrect path:
>  
> g++ -I/usr/include/python2.4 -I/usr/local/lib/python2.4/site-packages/numpy/core/include -DHAVE_CONFIG_H -I../include -I../include -I/usr/local/includ
> e/gtkglextmm-1.2 -I/usr/local/lib/gtkglextmm-1.2/include -I/usr/include/gtkglext-1.0 -I/usr/include/gtkmm-2.4 -I/usr/lib/gtkmm-2.4/include -I/usr/lib/g
> tkglext-1.0/include -I/usr/include/gdkmm-2.4 -I/usr/lib/gdkmm-2.4/include -I/usr/include/pangomm-1.4 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include
> -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/cairo -I/usr/include/freetype2 -I/usr/include/libpng12 -I/u
> sr/include/glibmm-2.4 -I/usr/lib/glibmm-2.4/include -I/usr/include/cairomm-1.0 -I/usr/include/sigc++-2.0 -I/usr/lib/sigc++-2.0/include -I/usr/include/a
> tk-1.0 -I/usr/include/atkmm-1.6 -I/usr/include/libglademm-2.4 -I/usr/lib/libglademm-2.4/include -I/usr/include/libglade-2.0 -I/usr/include/libxml2 -I..
> /include/gtk2 -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/python2.4 -I/usr/local/lib/python2.4/site-packages/numpy/core
> /include -fpic -DPIC -g -O2 -ftemplate-depth-120 -MMD -MF 
> convex.d -MT "convex.d 
> convex.lo" -c ./python/convex.cpp  -fPIC -DPIC -o .libs/convex.o
> In file included from ../include/python/convex.hpp:12,
>                  from ./python/convex.cpp:6:
> ../include/python/num_util.hpp:68:31: warning: numpy/arrayobject.h: No such 
>   file or directory
>
> It gave /usr/local/lib/..., instead of /usr/lib/... I don't have any numpy 
> package in /usr/local/lib... I made a symbolic link, and it compiled, but 
> it is not very clean.
>
>   

[Visualpython-users] 4.beta21

[Bruce S. <Bru...@nc...>]

Now available at sourceforge.net is VPython 4.beta21 for Windows and Linux:

*Default window now 600x600, which includes titlebar, toolbar, and 
borders. For the first time on Linux, you can place a window at a 
specific desired x,y position, as was always possible on Windows.
*Now display max 10000 points of a curve (old Visual did max 1000; see 
below).
*Implement and document curve.retain=N, meaning retain only the N most 
recently appended points.This is a convenient way to leave a tail behind 
a moving object.
*Significantly improved tuning of the balance between the computational 
thread and the render thread.
*Implemented toolbar option to restore to standard values center, 
forward, and up.
*Documentation for new display.get_titlebar_height(), 
display.get_toolbar_height().
*Added rate statements to tictac.py, hanoi.py, and toroid_drag.py as a 
workaround for a problem with quitting a program with a loop that 
contains very little computation. (I haven't yet figured out why it is 
difficult to quit such programs.)
*The statement scene.show_rendertime = True triggers a display in the 
bottom left corner of the screen of the cycle time (milliseconds between 
rendering of the scene) and render time (milliseconds required to render 
the scene). The cycle time minus the render time is the approximate 
number of milliseconds in the cycle devoted to your Python computations.

All of the standard example programs seem to run well on both Windows 
and Ubuntu Linux except for stonehenge.py which is sluggish compared to 
the production version. Rendering of the complex scene is slow on my not 
very powerful Windows/Linux laptop (1 GHz, 500 MB). I hope to study this 
further and try to bring the performance up to expectations.

I would appreciate it if some adventuresome souls would try this 
version, as a significant number of outstanding issues have been addressed.

I should offer some explanation of the need to display a maximum number 
of points in a curve. In Visual 3 a maximum of 1000 points were 
displayed for a curve, no matter how many points it actually contained. 
The points chosen to display were spaced as uniformly as possible over 
the entire curve. The bad thing about this scheme is that a curve with a 
very large number of points may display in a bizarre way. For example, 
if you repeatedly add points to a curve representing the elliptical 
orbit of a planet, eventually you'll see points connected to each other 
by straight-line segments from one side of the ellipse to another, which 
is very confusing. However, if we try to display all of the points, the 
longer the orbit runs the slower the rendering becomes. Some very simple 
standard orbit programs ran unacceptably slowly. So I've reverted to the 
old scheme of displaying only up to a maximum number of points. But 
recognizing the large increase in speed of computers since the 
beginnings of VPython in 2000, I made the limit 10000 instead of 1000, 
which seems to work fine and makes it 10 times less likely you'll see 
strange displays of a many-point curve. The philosophy underlying this 
kind of compromise was articulated very clearly by David Scherer, the 
originator of VPython, as "Go fast, be wrong!" The effect is that one 
gets almost always sensible and good performance, at the penalty of 
sometimes going wrong.

There is a highly technical problem which has been identified but for 
which there is currently no known solution. In the old Numeric module 
used in Visual 3, sqrt(5.5) was a float, but in numpy used in the beta 
version sqrt(5.5) is numpy.float64, with the highly unfortunate result 
that sqrt(5.5)*vector isn't a VPython vector but rather a numpy array. 
I've asked for help on this from both the numpy and Boost discussion 
lists but so far not gotten any assistance. In some existing physics 
programs the effect is to double the time required to update an orbit, 
so this is serious. I'll mention that vector*sqrt(5.5) works fine -- the 
result is a vector.

Bruce

Re: [Visualpython-users] Switch from vpython 3 to vpython 4

[<fre...@gb...>]

Another question (more a feature request): could it be possible to=20
precisely select the color (giving RGB values) for stereo mode? That way,=20
it would be possible to adjust it according to the glasses used...

=2D-=20
   Fr=E9d=E9ric

   http://www.gbiloba.org

[Visualpython-users] Switch from vpython 3 to vpython 4

[<fre...@gb...>]

Ok, so I'm now using vpython 4...

1) it fixed the crash when quit/hide display :o))))

2) all examples passed, but some have strange behaviour:

=2D controlstest.py: closing the main window using the window x box only=20
                   closes the 3D view, and freezes the main view.
=2D convex.py: closing the window using the window x box freezes.
=2D crossproduct.py: 100% CPU usage. very Slow.
=2D glinfo.py: freezes after printing the infos
=2D planar.py: CPU 100% usage
=2D randombox.py: 80% CPU usage
=2D texturetest.py: freeze if closed using the window x box
=2D tictac.py: 100% CPU usage
=2D Tk-Visual.py: freezes if 3D view closed using the window x box
=2D toroid_drag.py: 100% CPU usage

3) my app is much more slower (drag/move), and I'hve now 60-70% CPU usage=20
(vs 10-15% with vpython 3). It also freezes if I close the 3D view using=20
the window x box.

I have a general question: how do I cleanly stop the vpython mainloop from=
=20
my app? I mean, without the need to click on the GTK close button?

Last, I'm very impressed by the texture feature: in fact, this is why I=20
switched to vpython 4. I'm developping a pano head simulation, and I want=20
to apply a 360=B0x180=B0 pano on a vpython sphere, to simulate the real wor=
d.=20
BTW, is it possible to map the image *inside* a sphere?=20

=2D-=20
   Fr=E9d=E9ric

   http://www.gbiloba.org

Re: [Visualpython-users] compiling vpython 4 (was Crash when quit)

[<fre...@gb...>]

On dimanche 23 d=E9cembre 2007, Bruce Sherwood wrote:

> I think some of your missing libraries are included in some of those
> listed in the INSTALL file, but if you find that not to be the case I'd
> appreciate knowing so that the file can be improved.

In fact, the only package missing was gtkglextmm; all others where=20
correctly installed. The problem comes from the configure script. When it=20
call pkg-config, to check mising packages, it gets:

configure:19706: checking for pkg-config
configure:19724: found /usr/bin/pkg-config
configure:19736: result: /usr/bin/pkg-config
configure:19765: checking pkg-config is at least version 0.9.0
configure:19768: result: yes
configure:19792: checking for GTK
configure:19800: $PKG_CONFIG --exists --print-errors "gtkglextmm-1.2 >=3D 1=
=2E2
  pangoft2 glibmm-2.4 pangomm-1.4 libglademm-2.4 freetype2"
Package gtkglextmm-1.2 was not found in the pkg-config search path.
Perhaps you should add the directory containing `gtkglextmm-1.2.pc'
to the PKG_CONFIG_PATH environment variable
No package 'gtkglextmm-1.2' found
configure:19803: $? =3D 1
configure:19818: $PKG_CONFIG --exists --print-errors "gtkglextmm-1.2 >=3D 1=
=2E2=20
pangoft2 glibmm-2.4 pangomm-1.4 libglademm-2.4 freetype2"
Package gtkglextmm-1.2 was not found in the pkg-config search path.
Perhaps you should add the directory containing `gtkglextmm-1.2.pc'
to the PKG_CONFIG_PATH environment variable
No package 'gtkglextmm-1.2' found
configure:19821: $? =3D 1
No package 'gtkglextmm-1.2' found
configure:19849: result: no
configure:19851: error: gtkglextmm 1.2, pangoft2, glibmm-2.4, and=20
pangomm-1.4 libglademm-2.4 are required on Unix-like systems

As you can see, it outputs all libs, even if the only missing is=20
gtkglextmm. I compiled and installed it, and it now works fine :o)

But during the compilation phase, I still had problems of missing libs:=20
libboost-python (and -thread) is not checked in the configure. Once=20
installed, it works (it was the same in previous vpython versions).

And I have a another problem: vpython can't find the numpy/arrayobject.h=20
(imported from include/python/num_util.hpp). This file is in:

python-numpy:
   usr/lib/python2.4/site-packages/numpy/core/include/numpy/arrayobject.h

But the configure script found an incorrect path:
=20
g++ -I/usr/include/python2.4 -I/usr/local/lib/python2.4/site-packages/numpy=
/core/include -DHAVE_CONFIG_H -I../include -I../include -I/usr/local/includ
e/gtkglextmm-1.2 -I/usr/local/lib/gtkglextmm-1.2/include -I/usr/include/gtk=
glext-1.0 -I/usr/include/gtkmm-2.4 -I/usr/lib/gtkmm-2.4/include -I/usr/lib/g
tkglext-1.0/include -I/usr/include/gdkmm-2.4 -I/usr/lib/gdkmm-2.4/include -=
I/usr/include/pangomm-1.4 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include
=2DI/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/incl=
ude -I/usr/include/cairo -I/usr/include/freetype2 -I/usr/include/libpng12 -=
I/u
sr/include/glibmm-2.4 -I/usr/lib/glibmm-2.4/include -I/usr/include/cairomm-=
1.0 -I/usr/include/sigc++-2.0 -I/usr/lib/sigc++-2.0/include -I/usr/include/a
tk-1.0 -I/usr/include/atkmm-1.6 -I/usr/include/libglademm-2.4 -I/usr/lib/li=
bglademm-2.4/include -I/usr/include/libglade-2.0 -I/usr/include/libxml2 -I..
/include/gtk2 -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include =
=2DI/usr/include/python2.4 -I/usr/local/lib/python2.4/site-packages/numpy/c=
ore
/include -fpic -DPIC -g -O2 -ftemplate-depth-120 -MMD -MF=20
convex.d -MT "convex.d=20
convex.lo" -c ./python/convex.cpp  -fPIC -DPIC -o .libs/convex.o
In file included from ../include/python/convex.hpp:12,
                 from ./python/convex.cpp:6:
=2E./include/python/num_util.hpp:68:31: warning: numpy/arrayobject.h: No su=
ch=20
  file or directory

It gave /usr/local/lib/..., instead of /usr/lib/... I don't have any numpy=
=20
package in /usr/local/lib... I made a symbolic link, and it compiled, but=20
it is not very clean.

=2D-=20
   Fr=E9d=E9ric

   http://www.gbiloba.org

Re: [Visualpython-users] Crash when quit

[Bruce S. <Bru...@nc...>]

Here is a link to updated instructions for installing the beta version: 
http://vpython.org/INSTALL.html

This may be a bit more up to date than the INSTALL.txt file included in 
the tarball. It tries to do a better job of listing dependencies and how 
to deal with them.

I don't think there's any debugging code you can put in the Visual 
source code that would help you with what is almost certainly a graphics 
driver problem.

I think some of your missing libraries are included in some of those 
listed in the INSTALL file, but if you find that not to be the case I'd 
appreciate knowing so that the file can be improved.

Bruce Sherwood

Frédéric Mantegazza wrote:
> On samedi 22 décembre 2007, Bruce Sherwood wrote:
>
>   
>> Definitely an interesting situation. Presumably there's something wrong
>> with your graphics card driver, as you say, and the only fix is probably
>> an updated driver (which of course may not exist).
>>     
>
> Well, I'm always up-to-date with debian testing...
>
>   
>> Perhaps VPython runs as a remote display because the timing is somewhat 
>> different. 
>>     
>
> No idea how I can dig the problem? Where can I add debug outputs in your 
> code to find what happens? 
>
>   
>> Concerning trying the beta version, what libraries are you missing?
>>     
>
> configure: error: gtkglextmm 1.2, pangoft2, glibmm-2.4, and pangomm-1.4 
> libglademm-2.4 are required on Unix-like systems
>
>   

Re: [Visualpython-users] Crash when quit

[<fre...@gb...>]

On samedi 22 d=E9cembre 2007, Bruce Sherwood wrote:

> Definitely an interesting situation. Presumably there's something wrong
> with your graphics card driver, as you say, and the only fix is probably
> an updated driver (which of course may not exist).

Well, I'm always up-to-date with debian testing...

> Perhaps VPython runs as a remote display because the timing is somewhat=20
> different.=20

No idea how I can dig the problem? Where can I add debug outputs in your=20
code to find what happens?=20

> Concerning trying the beta version, what libraries are you missing?

configure: error: gtkglextmm 1.2, pangoft2, glibmm-2.4, and pangomm-1.4=20
libglademm-2.4 are required on Unix-like systems

=2D-=20
   Fr=E9d=E9ric

   http://www.gbiloba.org

Re: [Visualpython-users] Crash when quit

[Bruce S. <Bru...@nc...>]

Definitely an interesting situation. Presumably there's something wrong 
with your graphics card driver, as you say, and the only fix is probably 
an updated driver (which of course may not exist). Perhaps VPython runs 
as a remote display because the timing is somewhat different.

Concerning trying the beta version, what libraries are you missing?

Bruce Sherwood

Frédéric Mantegazza wrote:
> On samedi 22 décembre 2007, Bruce Sherwood wrote:
>
>   
>> This isn't a familiar-sounding problem. What version of VPython is this?
>> Did you build it from a tarball or obtain it from an existing Debian
>> package? When you say "the display hide() method", do you mean
>> scene.visible = False, or something else?
>>
>> VPython is known to work on a variety of Linux platforms, so it isn't
>> something as simple as "it doesn't work on Linux".
>>     
>
> Ok, I made some more tests. My wife as the same computer, same debian lenny 
> up-to-date, but a different graphics card. Mine is a ATI Radeon M9 (r200) 
> (working with free radeon driver), hers is a NVidia, with NVidia drivers.
>
> Here are the results:
>
> - vpython works fine on her computer
> - vpython works fine if I connect to my computer from hers (using ssh -X)
> - vpython works fine if I connect to her computer from mine (using ssh -X)
> - vpython crashes if I launch it from my computer
>
> So, there is something related to my video card driver, but I don't know 
> what. I would have understood if vpython always crashed when I *display* 
> it on *my* computer (directly running it on my computer, or running it on 
> my wife's one, throught ssh -X), as OpenGL stuff used is the one where the 
> display occurs... But here, it is a little different.
>
> Does someone has an idea? How can I make further tests to find the problem?
>
> Thanks,
>
>   

Re: [Visualpython-users] Crash when quit

[<fre...@gb...>]

On samedi 22 d=E9cembre 2007, Bruce Sherwood wrote:

> This isn't a familiar-sounding problem. What version of VPython is this?
> Did you build it from a tarball or obtain it from an existing Debian
> package? When you say "the display hide() method", do you mean
> scene.visible =3D False, or something else?
>
> VPython is known to work on a variety of Linux platforms, so it isn't
> something as simple as "it doesn't work on Linux".

Ok, I made some more tests. My wife as the same computer, same debian lenny=
=20
up-to-date, but a different graphics card. Mine is a ATI Radeon M9 (r200)=20
(working with free radeon driver), hers is a NVidia, with NVidia drivers.

Here are the results:

=2D vpython works fine on her computer
=2D vpython works fine if I connect to my computer from hers (using ssh -X)
=2D vpython works fine if I connect to her computer from mine (using ssh -X)
=2D vpython crashes if I launch it from my computer

So, there is something related to my video card driver, but I don't know=20
what. I would have understood if vpython always crashed when I *display*=20
it on *my* computer (directly running it on my computer, or running it on=20
my wife's one, throught ssh -X), as OpenGL stuff used is the one where the=
=20
display occurs... But here, it is a little different.

Does someone has an idea? How can I make further tests to find the problem?

Thanks,

=2D-=20
   Fr=E9d=E9ric

   http://www.gbiloba.org

Re: [Visualpython-users] Crash when quit

[<fre...@gb...>]

On samedi 22 d=E9cembre 2007, Bruce Sherwood wrote:

> This isn't a familiar-sounding problem. What version of VPython is this?
> Did you build it from a tarball or obtain it from an existing Debian
> package? When you say "the display hide() method", do you mean
> scene.visible =3D False, or something else?

Sorry, I forgot all that usefull informations. I'm using vpython 3.2.9,=20
compiled from source (I would like to try version 4, but some lib are=20
missing under debian; I'll have to get them from sources).

The crash occurs as soon as I click on the window close box, or if I call=20
scene.hide() or use scene.visible =3D False, but only if there is at least=
=20
one object in the scene; an empty scene does not crash the program.

I may make a mistake using vpython, but the same code runs fine under=20
Windows.

> VPython is known to work on a variety of Linux platforms, so it isn't
> something as simple as "it doesn't work on Linux".

As I said, I'm using debian (lenny). And I'm sure I had this problem some=20
years ago, when I first used vpython (also under debian, but stable sarge)=
=20
for my work: a student made a great 3D view of a complete neutron=20
spectrometer, with real time refresh:

    http://www.gbiloba.org/download/SNP-definitif-640x480.avi
    http://www.gbiloba.org/download/LPA-definitif-640x480.avi

He used it for its presentation, and people where amazed ;o)

Ok. I attached all build logs, and a simple script which fails. I ran it=20
with strace -f (to see all threads).

Thanks for you help.

=2D-=20
   Fr=E9d=E9ric

   http://www.gbiloba.org

Re: [Visualpython-users] Crash when quit

[Bruce S. <Bru...@nc...>]

This isn't a familiar-sounding problem. What version of VPython is this? 
Did you build it from a tarball or obtain it from an existing Debian 
package? When you say "the display hide() method", do you mean 
scene.visible = False, or something else?

VPython is known to work on a variety of Linux platforms, so it isn't 
something as simple as "it doesn't work on Linux".

Bruce Sherwood

Frédéric Mantegazza wrote:
> On samedi 22 décembre 2007, Frédéric Mantegazza wrote:
>
>   
>> I'm using vpython under debian lenny, and as soon as I close the window,
>> or call the display hide() method, my app crash with the following
>> error:
>>
>> Gdk-ERROR **: BadValue (integer parameter out of range for operation)
>>   serial 1309 error_code 2 request_code 129 minor_code 9
>>
>> Am I doing something wrong? ASFAIR, I had this problem long ago, when I
>> tried vptyhon for the first time...
>>     
>
> I just checked on a Windows XP running under VirtualBox: no crash there. 
> This is a linux-only problem...
>
>   

Re: [Visualpython-users] Crash when quit

[<fre...@gb...>]

On samedi 22 d=E9cembre 2007, Fr=E9d=E9ric Mantegazza wrote:

> I'm using vpython under debian lenny, and as soon as I close the window,
> or call the display hide() method, my app crash with the following
> error:
>
> Gdk-ERROR **: BadValue (integer parameter out of range for operation)
>   serial 1309 error_code 2 request_code 129 minor_code 9
>
> Am I doing something wrong? ASFAIR, I had this problem long ago, when I
> tried vptyhon for the first time...

I just checked on a Windows XP running under VirtualBox: no crash there.=20
This is a linux-only problem...

=2D-=20
   Fr=E9d=E9ric

   http://www.gbiloba.org