You can subscribe to this list here.
2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(4) |
Jul
(1) |
Aug
|
Sep
(15) |
Oct
(32) |
Nov
(35) |
Dec
(48) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
(46) |
Feb
(22) |
Mar
(65) |
Apr
(49) |
May
(22) |
Jun
(29) |
Jul
(51) |
Aug
(34) |
Sep
(32) |
Oct
(46) |
Nov
(30) |
Dec
(32) |
2002 |
Jan
(48) |
Feb
(4) |
Mar
(20) |
Apr
(28) |
May
(13) |
Jun
(34) |
Jul
(51) |
Aug
(15) |
Sep
(15) |
Oct
(35) |
Nov
(15) |
Dec
(20) |
2003 |
Jan
(31) |
Feb
(111) |
Mar
(41) |
Apr
(28) |
May
(36) |
Jun
(29) |
Jul
(27) |
Aug
(29) |
Sep
(47) |
Oct
(28) |
Nov
(7) |
Dec
(26) |
2004 |
Jan
(44) |
Feb
(9) |
Mar
(17) |
Apr
(26) |
May
(58) |
Jun
(13) |
Jul
(44) |
Aug
(64) |
Sep
(30) |
Oct
(11) |
Nov
(21) |
Dec
(28) |
2005 |
Jan
(29) |
Feb
(11) |
Mar
(11) |
Apr
(22) |
May
(85) |
Jun
(46) |
Jul
(17) |
Aug
(18) |
Sep
(14) |
Oct
(22) |
Nov
(1) |
Dec
(45) |
2006 |
Jan
(20) |
Feb
(36) |
Mar
(18) |
Apr
(24) |
May
(21) |
Jun
(48) |
Jul
(23) |
Aug
(20) |
Sep
(10) |
Oct
(41) |
Nov
(46) |
Dec
(40) |
2007 |
Jan
(40) |
Feb
(20) |
Mar
(13) |
Apr
(6) |
May
(24) |
Jun
(31) |
Jul
(30) |
Aug
(11) |
Sep
(11) |
Oct
(10) |
Nov
(56) |
Dec
(64) |
2008 |
Jan
(64) |
Feb
(22) |
Mar
(63) |
Apr
(28) |
May
(25) |
Jun
(36) |
Jul
(11) |
Aug
(9) |
Sep
(14) |
Oct
(41) |
Nov
(46) |
Dec
(130) |
2009 |
Jan
(95) |
Feb
(41) |
Mar
(24) |
Apr
(35) |
May
(53) |
Jun
(67) |
Jul
(48) |
Aug
(48) |
Sep
(86) |
Oct
(75) |
Nov
(64) |
Dec
(52) |
2010 |
Jan
(57) |
Feb
(31) |
Mar
(28) |
Apr
(40) |
May
(25) |
Jun
(42) |
Jul
(79) |
Aug
(31) |
Sep
(49) |
Oct
(66) |
Nov
(38) |
Dec
(25) |
2011 |
Jan
(29) |
Feb
(18) |
Mar
(44) |
Apr
(6) |
May
(28) |
Jun
(31) |
Jul
(36) |
Aug
(24) |
Sep
(30) |
Oct
(23) |
Nov
(21) |
Dec
(27) |
2012 |
Jan
(14) |
Feb
(11) |
Mar
(2) |
Apr
(48) |
May
(7) |
Jun
(32) |
Jul
(22) |
Aug
(25) |
Sep
(31) |
Oct
(32) |
Nov
(21) |
Dec
(17) |
2013 |
Jan
(44) |
Feb
(27) |
Mar
(3) |
Apr
(1) |
May
|
Jun
|
Jul
(3) |
Aug
(4) |
Sep
(1) |
Oct
(7) |
Nov
(5) |
Dec
(5) |
2014 |
Jan
|
Feb
|
Mar
|
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(3) |
Dec
(2) |
2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
2017 |
Jan
(7) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2019 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Stef M. <s.m...@ru...> - 2009-01-14 18:41:11
|
Emanuele Gissi wrote: > I am developing a small multiplatform application for data visualisation. > Could someone point me to a simple example on how to integrate a > wxpython GUI with vpython 3d visualisation? look here, http://mientki.ruhosting.nl/data_www/pylab_works/pw_vpython_docking.html but it will only work for VPython-3. In VPython-5 there are "features" that will crash the application, and from Bruce I understood that these "features" will not be removed on a short term. cheers, Stef > Thank you. > Emanuele Gissi > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by: > SourcForge Community > SourceForge wants to tell your story. > http://p.sf.net/sfu/sf-spreadtheword > ------------------------------------------------------------------------ > > _______________________________________________ > Visualpython-users mailing list > Vis...@li... > https://lists.sourceforge.net/lists/listinfo/visualpython-users > |
From: Bruce S. <Bru...@nc...> - 2009-01-14 18:24:30
|
In the Visual 5 section of vpython.org there's a document on new features to which I've added more information about known bugs and incompatibilities, with suggested workarounds. Bruce Sherwood |
From: Emanuele G. <ema...@gm...> - 2009-01-14 13:20:46
|
I am developing a small multiplatform application for data visualisation. Could someone point me to a simple example on how to integrate a wxpython GUI with vpython 3d visualisation? Thank you. Emanuele Gissi |
From: Suman C. <su...@ss...> - 2009-01-14 13:08:16
|
Dear all, I am trying to compile visual-3.2.9 on a 64 bit Ubuntu 8.10 and getting the following problem at the "make" step: ============================================================================= <snip> Updating dependancy information for ../../visual-3.2.9/src/arrow.cpp ... make[1]: Leaving directory `/home/suman/Softwares/VPython/src' make[1]: Entering directory `/home/suman/Softwares/VPython/src' This is a quiet Makefile. If make exits with an error, check src/build.log to see the complete error message(s). In the event of an error that you cannot debug, please send a message to vis...@li..., including the files config.log and src/build.log, requesting assistance. Compiling ../../visual-3.2.9/src/arrow.cpp ... make[1]: *** [arrow.lo] Error 1 make[1]: Leaving directory `/home/suman/Softwares/VPython/src' make: *** [all-recursive] Error 1 ============================================================================== Last two lines containing error messages in build.log: ../../visual-3.2.9/include/platlinux.h:27: error: declaration of 'typedef class visual::lock<visual::mutex> visual::mutex::lock' ../../visual-3.2.9/include/vthread.h:13: error: changes meaning of 'lock' from 'class visual::lock<visual::mutex>' =============================================================================== Since I have no clue about how to debug this problem, I have attached the config.log and build.log files. It will be much appreciated if somebody can help me get through this. Thanks and regards, Suman Chakrabarty. |
From: Bruce S. <Bru...@nc...> - 2009-01-14 04:42:10
|
Have you tried updating your graphics driver? This is unfamiliar behavior. You might also try changing site-settings.py as discussed in the materials section of the documentation for Visual 5. Bruce Sherwood Roberto Aguirre Maturana wrote: > Bruce: > > I have a notebook with Windows XP Proffesional and a Pentium 4 HT > processor and VPython just doesn't semm to work with it. The display is > extremely slow, lights doesn't seem to be working (object appear as > silhouettes) and if a program has a box object (for instance bounce.py) it > crashes with the following error: > > VPython ***CRITICAL ERROR***: ..\src\core\display_kernel.cpp:909: > cvisual::display_kernel::render_scene: OpenGL error: > .\src\core\box.cpp:68 operación no válida, aborting. > > I have seen some old threads in google which refer too a simmilar problem > affecting Pentium 4 HT. > > Best regards, > Roberto Aguirre Maturana > Santiago, Chile > |
From: Roberto A. M. <rha...@ho...> - 2009-01-14 03:20:33
|
Bruce: I have a notebook with Windows XP Proffesional and a Pentium 4 HT processor and VPython just doesn't semm to work with it. The display is extremely slow, lights doesn't seem to be working (object appear as silhouettes) and if a program has a box object (for instance bounce.py) it crashes with the following error: VPython ***CRITICAL ERROR***: ..\src\core\display_kernel.cpp:909: cvisual::display_kernel::render_scene: OpenGL error: .\src\core\box.cpp:68 operación no válida, aborting. I have seen some old threads in google which refer too a simmilar problem affecting Pentium 4 HT. Best regards, Roberto Aguirre Maturana Santiago, Chile -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ |
From: Bruce S. <Bru...@nc...> - 2009-01-13 00:48:24
|
Don't I wish it were that simple. No, objects are created with opacity=1.0 by default. That's why a scene contains opaque objects if you don't explicitly set the opacity to something different. b = box() print b.opacity # shows 1.0 Bruce Sherwood Lenore Horner wrote: > Very naively,... > > This looks to me like the need is to create things with some opacity (it > doesn't maybe matter what since both 0.5 and 0.99 work). Does this mean > there is no default value for opacity and somewhere a number, any > number, is needed to figure out what to put on the screen and all for > the want of a number the program crashes? > > Lenore > > On Jan 12, 2009, at 13:44 PM, Bruce Sherwood wrote: > >> Thanks, Scott! Your observation should be a good big hint at where the >> problem lies, though I don't yet see where this leads. >> >> Bruce Sherwood >> >> Scott David Daniels wrote: >>> Bruce Sherwood wrote: >>> >>>> .... Here's the nub of the problem: >>>> The following crashes hard, at least on Vista (and on XP): >>>> f = frame() >>>> b = box(frame=f) >>>> b.opacity=0.3 >>>> The following doesn't crash: >>>> f = frame() >>>> b = box(frame=f, opacity=0.5) >>>> b.opacity=0.3 >>>> >>> Checking a bit further, the following crashes: >>> > f = frame() >>> > p = sphere(frame=f, opacity=1) >>> > p.opacity = 0.99 >>> > The following doesn't crash: >>> > f = frame() >>> > p = sphere(frame=f, opacity=0.99) >>> > p.opacity = 1 >>> > p.opacity = .3 >>> > p.opacity = 0 >>> >>> So, a work-around is to create things you expect to tweak opacity >>> on as .99 opacity. This doesn't get to the root cause, but does let >>> you move on. >>> >>> --Scott David Daniels >>> Sco...@Ac... >>> >>> >>> ------------------------------------------------------------------------------ >>> This SF.net email is sponsored by: >>> SourcForge Community >>> SourceForge wants to tell your story. >>> http://p.sf.net/sfu/sf-spreadtheword >>> _______________________________________________ >>> Visualpython-users mailing list >>> Vis...@li... >>> https://lists.sourceforge.net/lists/listinfo/visualpython-users >>> >> ------------------------------------------------------------------------------ >> This SF.net email is sponsored by: >> SourcForge Community >> SourceForge wants to tell your story. >> http://p.sf.net/sfu/sf-spreadtheword_______________________________________________ >> Visualpython-users mailing list >> Vis...@li... >> https://lists.sourceforge.net/lists/listinfo/visualpython-users > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by: > SourcForge Community > SourceForge wants to tell your story. > http://p.sf.net/sfu/sf-spreadtheword > > > ------------------------------------------------------------------------ > > _______________________________________________ > Visualpython-users mailing list > Vis...@li... > https://lists.sourceforge.net/lists/listinfo/visualpython-users |
From: Lenore H. <lh...@si...> - 2009-01-13 00:34:51
|
Very naively,... This looks to me like the need is to create things with some opacity (it doesn't maybe matter what since both 0.5 and 0.99 work). Does this mean there is no default value for opacity and somewhere a number, any number, is needed to figure out what to put on the screen and all for the want of a number the program crashes? Lenore On Jan 12, 2009, at 13:44 PM, Bruce Sherwood wrote: > Thanks, Scott! Your observation should be a good big hint at where > the problem lies, though I don't yet see where this leads. > > Bruce Sherwood > > Scott David Daniels wrote: >> >> Bruce Sherwood wrote: >> >>> .... Here's the nub of the problem: >>> The following crashes hard, at least on Vista (and on XP): >>> f = frame() >>> b = box(frame=f) >>> b.opacity=0.3 >>> The following doesn't crash: >>> f = frame() >>> b = box(frame=f, opacity=0.5) >>> b.opacity=0.3 >>> >> Checking a bit further, the following crashes: >> > f = frame() >> > p = sphere(frame=f, opacity=1) >> > p.opacity = 0.99 >> > The following doesn't crash: >> > f = frame() >> > p = sphere(frame=f, opacity=0.99) >> > p.opacity = 1 >> > p.opacity = .3 >> > p.opacity = 0 >> >> So, a work-around is to create things you expect to tweak opacity >> on as .99 opacity. This doesn't get to the root cause, but does let >> you move on. >> >> --Scott David Daniels >> Sco...@Ac... >> >> >> ------------------------------------------------------------------------------ >> This SF.net email is sponsored by: >> SourcForge Community >> SourceForge wants to tell your story. >> http://p.sf.net/sfu/sf-spreadtheword >> _______________________________________________ >> Visualpython-users mailing list >> Vis...@li... >> https://lists.sourceforge.net/lists/listinfo/visualpython-users >> > ------------------------------------------------------------------------------ > This SF.net email is sponsored by: > SourcForge Community > SourceForge wants to tell your story. > http://p.sf.net/sfu/sf-spreadtheword_______________________________________________ > Visualpython-users mailing list > Vis...@li... > https://lists.sourceforge.net/lists/listinfo/visualpython-users |
From: Bruce S. <Bru...@nc...> - 2009-01-12 19:44:30
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> Thanks, Scott! Your observation should be a good big hint at where the problem lies, though I don't yet see where this leads.<br> <br> Bruce Sherwood<br> <br> Scott David Daniels wrote: <blockquote cite="mid:gkg29d$dlo$1...@ge..." type="cite"> <pre wrap="">Bruce Sherwood wrote: </pre> <blockquote type="cite"> <pre wrap="">.... Here's the nub of the problem: The following crashes hard, at least on Vista (and on XP): f = frame() b = box(frame=f) b.opacity=0.3 The following doesn't crash: f = frame() b = box(frame=f, opacity=0.5) b.opacity=0.3 </pre> </blockquote> <pre wrap=""><!----> Checking a bit further, the following crashes: > f = frame() > p = sphere(frame=f, opacity=1) > p.opacity = 0.99 > The following doesn't crash: > f = frame() > p = sphere(frame=f, opacity=0.99) > p.opacity = 1 > p.opacity = .3 > p.opacity = 0 So, a work-around is to create things you expect to tweak opacity on as .99 opacity. This doesn't get to the root cause, but does let you move on. --Scott David Daniels <a class="moz-txt-link-abbreviated" href="mailto:Sco...@Ac...">Sco...@Ac...</a> ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. <a class="moz-txt-link-freetext" href="http://p.sf.net/sfu/sf-spreadtheword">http://p.sf.net/sfu/sf-spreadtheword</a> _______________________________________________ Visualpython-users mailing list <a class="moz-txt-link-abbreviated" href="mailto:Vis...@li...">Vis...@li...</a> <a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/visualpython-users">https://lists.sourceforge.net/lists/listinfo/visualpython-users</a> </pre> </blockquote> </body> </html> |
From: Scott D. D. <Sco...@Ac...> - 2009-01-12 18:31:35
|
Bruce Sherwood wrote: > .... Here's the nub of the problem: > The following crashes hard, at least on Vista (and on XP): > f = frame() > b = box(frame=f) > b.opacity=0.3 > The following doesn't crash: > f = frame() > b = box(frame=f, opacity=0.5) > b.opacity=0.3 Checking a bit further, the following crashes: > f = frame() > p = sphere(frame=f, opacity=1) > p.opacity = 0.99 > The following doesn't crash: > f = frame() > p = sphere(frame=f, opacity=0.99) > p.opacity = 1 > p.opacity = .3 > p.opacity = 0 So, a work-around is to create things you expect to tweak opacity on as .99 opacity. This doesn't get to the root cause, but does let you move on. --Scott David Daniels Sco...@Ac... |
From: Bruce S. <Bru...@nc...> - 2009-01-12 17:07:45
|
Thanks for the report. Here's the nub of the problem: The following crashes hard, at least on Vista: f = frame() b = box(frame=f) b.opacity=0.3 But the following doesn't crash: f = frame() b = box(frame=f, opacity=0.5) b.opacity=0.3 I have no idea what causes this. Bruce Sherwood symion wrote: > The following program generates a Microsoft Visual C++ Assertion error > message! > It has something to do with a box in a frame and changing opacity! > > Symion > |
From: symion <sy...@pr...> - 2009-01-12 11:07:28
|
The following program generates a Microsoft Visual C++ Assertion error message! It has something to do with a box in a frame and changing opacity! Symion from __future__ import division from visual import * from random import uniform,random # Derek Harrison, The Knoware Archive, December 2008 def wireframe(w,h,d): # For point, curve and convex Object position. x=w/2.0 y=h/2.0 z=d/2.0 mat=[(-x,-y,-z),(x,-y,-z),(x,y,-z),(-x,y,-z), (-x,-y,-z),(-x,-y,z),(x,-y,z),(x,y,z), (-x,y,z),(-x,-y,z),(x,-y,z),(x,-y,-z), (x,y,-z),(x,y,z),(-x,y,z),(-x,y,-z)] return mat def start(): scene.visible=0 scene.range=4.0 scene.fov=1.103 scene.ambient=0.5 scene.userzoom=1 scene.userspin=1 scene.x=0 scene.y=0 scene.width=600 scene.height=400 scene.title='Project : Symion 2008' scene.forward=vector(0.622, 0.638, -0.455) start() # old=False f1=frame(pos=(0,0,0)) f2=frame(pos=(0,0,0)) f3=frame(pos=(0,0,0)) f4=frame(pos=(0,0,0)) # if old: curve(frame=f1,pos=wireframe(1/4,4,4),color=color.orange) convex(frame=f1,pos=wireframe(1/4,4,4),color=color.red) curve(frame=f2,pos=wireframe(1/3,3,3),color=color.yellow) convex(frame=f2,pos=wireframe(1/3,3,3),color=color.orange) curve(frame=f3,pos=wireframe(1/2,2,2),color=color.white) convex(frame=f3,pos=wireframe(1/2,2,2),color=color.yellow) curve(frame=f4,pos=wireframe(1,1,1),color=color.blue) convex(frame=f4,pos=wireframe(1,1,1),color=color.white) else: box(frame=f1,size=(1/4,4,4),color=color.orange) box(frame=f2,size=(1/3,3,3),color=color.yellow) box(frame=f3,size=(1/2,2,2),color=color.white) box(frame=f4,size=(1,1,1),color=color.blue) scene.visible=1 a=radians(1**2) b=radians(2**2) c=radians(3**2) d=radians(4**2) while 1: rate(10) f1.rotate(angle=a) f2.rotate(angle=b) f3.rotate(angle=c) f4.rotate(angle=d) if scene.mouse.events>0: m=scene.mouse.getevent() if m.release=='left': if m.pick: if m.pick.__class__ is box: scene.center=m.pick.pos m.pick.opacity=random() else: scene.center=m.pickpos m.pick.color=(random(),random(),random()) else: scene.center=scene.mouse.pos else: pass else: pass |
From: Bruce S. <Bru...@nc...> - 2009-01-10 22:30:15
|
Interesting points. Thanks for the insight. Bruce Sherwood Guy K. Kloss wrote: > On Fri, 09 Jan 2009 09:42:51 Bruce Sherwood wrote: >> I don't know why numpy made some seemingly trivial >> changes such as NewAxis -> newaxis. Annoying. > > I'd guess they did it as it's more PEP-8 compatible. NewAxis looks like a > class, whereas newaxis is an attribute, variable, or some other identifier. > numpy.newaxis is comparable to visual.color.magenta in a way. > > I'm glad that it's renamed, as it is not possible to create a NewAxis > instance, and therefore is much less confusing to the Python programmer. > > Guy > |
From: Guy K. K. <g....@ma...> - 2009-01-10 20:10:03
|
On Fri, 09 Jan 2009 09:42:51 Bruce Sherwood wrote: > I don't know why numpy made some seemingly trivial > changes such as NewAxis -> newaxis. Annoying. I'd guess they did it as it's more PEP-8 compatible. NewAxis looks like a class, whereas newaxis is an attribute, variable, or some other identifier. numpy.newaxis is comparable to visual.color.magenta in a way. I'm glad that it's renamed, as it is not possible to create a NewAxis instance, and therefore is much less confusing to the Python programmer. Guy -- Guy K. Kloss Institute of Information and Mathematical Sciences Te Kura Pūtaiao o Mōhiohio me Pāngarau Room 2.63, Quad Block A Building Massey University, Auckland, Albany Private Bag 102 904, North Shore Mail Centre voice: +64 9 414-0800 ext. 9585 fax: +64 9 441-8181 eMail: G....@ma... http://iims.massey.ac.nz |
From: symion <sy...@pr...> - 2009-01-09 17:06:52
|
Here is a small program that wraps a wire-frame around a cube with a single data set, that can be used by either points, curve or convex, each cube can be divided into a square grid. The demo displays 8 cubes that can act independently or as a group and has heaps of control, IDLE displays key control table. Color, Number of squares on a side, Thickness of wire-frame, Rotation, Visibility and Axis can all be randomly chosen. And it is Fast. From a single cube with 6 sides to a grid wrapped cube with 52 x 52 x 6 sides = 16244 squares maximum. A problem exists when the number of squares equals 9,12,21 or 46 through 49 or exceeds 52! I don't know what causes this! I have checked the data set but have not resolved it yet! Source code is here: gridwire.py <http://home.primusonline.com.au/knoware/python/gridwire.py> Symion |
From: Bruce S. <Bru...@nc...> - 2009-01-09 17:04:43
|
Thanks, but what is an "embedded" VPython window? Bruce Sherwood Stef Mientki wrote: > I just found out that this error is related to the previous problem, the > moving of the embedded VPython window. > If an embedded window is moved, > and during zoom the (unvisible) mouse position get's outside the (moved) > VPython window, > this error occurs. > > cheers, > Stef > > > Stef Mientki wrote: >> hello, >> >> I just got this error, while zooming an (embedded) VPython window: >> >> VPython ***CRITICAL ERROR***: ..\src\core\display_kernel.cpp:535: >> cvisual::display_kernel::world_to_view_transform: VPython degenerate >> projection: 0 0.0833827 0.57735 0.463799 >> >> cheers, >> Stef >> >> ------------------------------------------------------------------------------ >> Check out the new SourceForge.net Marketplace. >> It is the best place to buy or sell services for >> just about anything Open Source. >> http://p.sf.net/sfu/Xq1LFB >> _______________________________________________ >> Visualpython-users mailing list >> Vis...@li... >> https://lists.sourceforge.net/lists/listinfo/visualpython-users >> >> >> > > ------------------------------------------------------------------------------ > Check out the new SourceForge.net Marketplace. > It is the best place to buy or sell services for > just about anything Open Source. > http://p.sf.net/sfu/Xq1LFB > _______________________________________________ > Visualpython-users mailing list > Vis...@li... > https://lists.sourceforge.net/lists/listinfo/visualpython-users |
From: Stef M. <s.m...@ru...> - 2009-01-09 16:00:11
|
I just found out that this error is related to the previous problem, the moving of the embedded VPython window. If an embedded window is moved, and during zoom the (unvisible) mouse position get's outside the (moved) VPython window, this error occurs. cheers, Stef Stef Mientki wrote: > hello, > > I just got this error, while zooming an (embedded) VPython window: > > VPython ***CRITICAL ERROR***: ..\src\core\display_kernel.cpp:535: > cvisual::display_kernel::world_to_view_transform: VPython degenerate > projection: 0 0.0833827 0.57735 0.463799 > > cheers, > Stef > > ------------------------------------------------------------------------------ > Check out the new SourceForge.net Marketplace. > It is the best place to buy or sell services for > just about anything Open Source. > http://p.sf.net/sfu/Xq1LFB > _______________________________________________ > Visualpython-users mailing list > Vis...@li... > https://lists.sourceforge.net/lists/listinfo/visualpython-users > > > |
From: Stef M. <s.m...@ru...> - 2009-01-09 15:08:11
|
hello, I just got this error, while zooming an (embedded) VPython window: VPython ***CRITICAL ERROR***: ..\src\core\display_kernel.cpp:535: cvisual::display_kernel::world_to_view_transform: VPython degenerate projection: 0 0.0833827 0.57735 0.463799 cheers, Stef |
From: Stef M. <s.m...@ru...> - 2009-01-09 15:04:54
|
... when VPython window is docked and the parent window is moved. This worked well in VPython 3. cheers, Stef |
From: Joe H. <hea...@gm...> - 2009-01-09 03:53:57
|
> Date: Thu, 8 Jan 2009 17:45:11 -0500 > From: James Mueller <mu...@pi...> > Subject: Re: [Visualpython-users] Mac IDLE fix > To: James Mueller <mue...@pi... <mueller%2B...@pi...>> > Cc: Bruce Sherwood <Bru...@nc...>, vpusers > <vis...@li...> > Message-ID: <2AE...@pi...> > Content-Type: text/plain; charset="US-ASCII"; format=flowed; delsp=yes > > The patch works. > > In macosxSupport.py, if you change the line > > if tkversion >= '8.4.14': > > to > > if map(int, tkversion.split('.')) >= (8, 4, 14): > > then you get an IDLE->Preferences menu, which contains all the > configuration stuff. I too can confirm that this patch works. However, the configuration window that comes up can't be moved and it causes the main IDLE window to lose focus, which returns when the config window is dismissed. Joe |
From: Bruce S. <Bru...@nc...> - 2009-01-09 02:43:46
|
Thanks for the corrections, which I've checked into CVS. Bruce Sherwood Stef Mientki wrote: > thanks Bruce, > > Bruce Sherwood wrote: >> See the example programs stars.py or gas.py in the Visual 5 version, >> which have been rewritten to work either with Numeric (Visual 3) or >> numpy (Visual 5). I don't know why numpy made some seemingly trivial >> changes such as NewAxis -> newaxis. Annoying. > I didn't notice the demo stars (as I've under the name Nebula_20), > beautiful ! > If it was only the newaxis, it can also be set with > try: > NewAxis > except: > NewAxis = newaxis > (Because I use a pre-script, it's easier for me to put it there once) > But there is also a subtle change with "tolist", I see :-( > > Two minor remarks about the stars demo: > > print """ > Right button drag to rotate view. > Left button drag up or down to move in or out. > """ > shouldn't "left button" be "middle button" ? > > and you misses at the end where " t += dt" > Nsteps += 1 > > cheers, > Stef > > > ------------------------------------------------------------------------------ > Check out the new SourceForge.net Marketplace. > It is the best place to buy or sell services for > just about anything Open Source. > http://p.sf.net/sfu/Xq1LFB > _______________________________________________ > Visualpython-users mailing list > Vis...@li... > https://lists.sourceforge.net/lists/listinfo/visualpython-users |
From: Stef M. <s.m...@ru...> - 2009-01-08 22:50:58
|
hi Bruce, Bruce Sherwood wrote: > Your font is sans-serif, because that's the default when you don't > specify a font in a label statement. On my Windows Vista machine I > don't see extra pixels lit up (but I do if I specify serif). On winXP, the serif fonts shows the same effect, but on other characters. The monospace font doesn't show the effect (but it's so large). With all font types, the borderlines seems to change random between: 1 white line or 2 gray lines. btw. Instead of resizing the window, you can force the effect also with zooming in and out. cheers, Stef |
From: James M. <mu...@pi...> - 2009-01-08 22:45:19
|
The patch works. In macosxSupport.py, if you change the line if tkversion >= '8.4.14': to if map(int, tkversion.split('.')) >= (8, 4, 14): then you get an IDLE->Preferences menu, which contains all the configuration stuff. {I had a typo in my last mail, It should have said version of Tk < 8.4.10.} I haven't checked the 2.5.4 version of MacPython, but since this change only went into the repository on Friday. It might not be in the bundle. -Jim On Jan 8, 2009, at 4:25 PM, James Mueller wrote: > I just realized I responed to Scott and not the entire list, so I > paste that here. > > In the meantime. here are three issues listed the python tracker. > > 2754 6 days ago Mac version of IDLE doesn't scroll as > expected > open alextrob > http://bugs.python.org/issue2754 > > 3549 6 days ago Missing IDLE Preferences on Mac pending > pchew > http://bugs.python.org/issue3549 > > After reading the first one, I can verify that I see this effect too. > > The second one states that the Options->Configure menu has become > IDLE- >> Preferences on the mac, but there was a bug in how they checked the > Tk version. So it should bite you if you have a version of Tk >= > 8.4.10. It states that this was fixed on Friday and is in the trunk > and backported to the 2.6 and 3.1 versions of Python. (3.1?) > > Anyway below is my previous message, which is probably out of date > now. > >> I have tried out idle from both the current Enthought and the one >> that >> comes with MacPython. The only things I see are: >> >> 1) If I open a new window, or open a file, occasionally I get an >> error >> >> RCNE SendEventToEventTarget (suom Moved ) failed, -50 >> >> This does not happen every time, and maybe it could happen selecting >> other menu items. I haven't tried everything, and it is intermittent >> on those where I do see it. I can't give an impression of whether it >> occurs more frequently in one distribution than another, because >> after >> playing for 5 minutes on each, I only have a handful of instances >> total. Any comparison would no be statistically significant, but it >> does not seem to be a large problem. Of course that might just be my >> hardware. >> >> 2) If I click in one window and then back in source window, Focus is >> changed to the source window but the cursor position is still where >> it >> was when I was last in that window. Once focus has been shifted to >> that window, cursor move properly when I click on text. This is a >> "feature" that I see all the time on Macs. When I have two browser >> windows open I click on a button in one, it has no effect unless that >> window already has the focus. This is sometimes annoying for me in >> that I don't want to have to click twice to get something to happen. >> Other times I am happy that the button I just happen to click on >> while >> trying to bring a window to the front didn't actually register the >> click. >> >> 3) I haven't been able to get the scrollbar problem to occur, but >> again if it is an intermittent problem, perhaps I just haven't tried >> long enough. >> >> 4) The reason that the new Enthought distribution has a "Configure >> IDLE" menu option is that they threw out the IDLE.app. Instead they >> provide a simple shell script, ".command" which then runs "/ >> Library/ >> Frameworks/Python.framework/Versions/Current/bin/idle" in a console >> window. So the configure problem is in IDLE.app, not idle. > > > -Jim > > > On Jan 8, 2009, at 12:47 PM, Bruce Sherwood wrote: > >> I've verified that the Visual 5.01 works with the latest MacPython >> 2.5.4, and I've changed the Visual 5 download pages for Mac and >> Windows >> to reference the recent 2.5.4 release instead of 2.5.2. >> >> However, when I install MacPython 2.5.4, overwriting 2.5.2 but >> leaving >> the Visual 5.01 files in place, Visual hangs (like the problem >> sometimes >> seen with Visual 5.01 when running for the first time on a Mac). >> Reinstalling Visual 5.01 cures the problem. Strange. >> >> Bruce Sherwood >> >> Joe Heafner wrote: >>> Date: Wed, 07 Jan 2009 13:26:09 -0500 >>> From: Bruce Sherwood <Bru...@nc... >>> <mailto:Bru...@nc...>> >>> Subject: [Visualpython-users] Mac IDLE fix >>> To: vpusers <vis...@li... >>> <mailto:vis...@li...>> >>> Message-ID: <496...@nc... >>> <mailto:496...@nc...>> >>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed >>> >>> The version of IDLE that comes with Python on the Mac is >>> defective. In >>> particular, it does not offer a menu option to configure IDLE. >>> If you >>> would like to have a larger font size, to have your file >>> automatically >>> saved when you run (if you changed it), the ability to be able >>> to make a >>> change and re-run your program without being interrupted by >>> being asked >>> whether to save the file, and to have the Visual help available >>> on the >>> IDLE help menu, download the file idlerc.zip and unzip it in >>> your home >>> folder (e.g. /Users/tom). Depending on your Finder settings, you >>> may not >>> see the resulting folder ".idlerc", but it will be used by IDLE >>> (in a >>> Terminal you can see it if you execute "ls -a"). >>> >>> >>> Seems to work fine for me. I've installed the new Mac VPython on >>> all 12 >>> of my MacBooks at work and we'll start using it tomorrow. Will >>> applying >>> MacPython 2.5.x updates break Visual? For some time, I was under the >>> impression that my VPython installed via Fink was using Python 2.6 >>> but I >>> was mistaken. Now I've no idea what package caused Python 2.6 to be >>> installed under Fink, but I can't remove it because something else >>> depends on it. Funny... >>> >>> Joe >>> >>> >>> ------------------------------------------------------------------------ >>> >>> ------------------------------------------------------------------------------ >>> Check out the new SourceForge.net Marketplace. >>> It is the best place to buy or sell services for >>> just about anything Open Source. >>> http://p.sf.net/sfu/Xq1LFB >>> >>> >>> ------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> Visualpython-users mailing list >>> Vis...@li... >>> https://lists.sourceforge.net/lists/listinfo/visualpython-users >> >> ------------------------------------------------------------------------------ >> Check out the new SourceForge.net Marketplace. >> It is the best place to buy or sell services for >> just about anything Open Source. >> http://p.sf.net/sfu/Xq1LFB >> _______________________________________________ >> Visualpython-users mailing list >> Vis...@li... >> https://lists.sourceforge.net/lists/listinfo/visualpython-users > > > ------------------------------------------------------------------------------ > Check out the new SourceForge.net Marketplace. > It is the best place to buy or sell services for > just about anything Open Source. > http://p.sf.net/sfu/Xq1LFB > _______________________________________________ > Visualpython-users mailing list > Vis...@li... > https://lists.sourceforge.net/lists/listinfo/visualpython-users |
From: Stef M. <s.m...@ru...> - 2009-01-08 22:32:13
|
thanks Bruce, Bruce Sherwood wrote: > See the example programs stars.py or gas.py in the Visual 5 version, > which have been rewritten to work either with Numeric (Visual 3) or > numpy (Visual 5). I don't know why numpy made some seemingly trivial > changes such as NewAxis -> newaxis. Annoying. I didn't notice the demo stars (as I've under the name Nebula_20), beautiful ! If it was only the newaxis, it can also be set with try: NewAxis except: NewAxis = newaxis (Because I use a pre-script, it's easier for me to put it there once) But there is also a subtle change with "tolist", I see :-( Two minor remarks about the stars demo: print """ Right button drag to rotate view. Left button drag up or down to move in or out. """ shouldn't "left button" be "middle button" ? and you misses at the end where " t += dt" Nsteps += 1 cheers, Stef |
From: Bruce S. <Bru...@nc...> - 2009-01-08 22:15:15
|
Your font is sans-serif, because that's the default when you don't specify a font in a label statement. On my Windows Vista machine I don't see extra pixels lit up (but I do if I specify serif). Maybe the situation is different on XP. Thanks for the report. Bruce Stef Mientki wrote: > > Bruce Sherwood wrote: >> I've seen this label bug with font='serif' but not with the default >> sans-serif font that it looks like you've used. Could you please post >> the actual code you used to generate the picture? > AFAIK, I didn't set the font, > so where is the font coming from. > Code below. >> I stand however by my previous statement that the only "significant >> differences" are those listed. > I agree it's not really significant. > > cheers, > Stef >> Bruce Sherwood >> |