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: James M. <mu...@pi...> - 2009-01-08 21:25:45
|
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 |
From: Stef M. <s.m...@ru...> - 2009-01-08 21:04:21
|
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 > #----------------------------------------------------- # Demo of a symmetric (I1=I2) gyroscope. It uses # numerical integration with a primitive mid point # solver of Euler's equations using the Euler angles # [phi,theta,psi] as variables. # # Left mouse toggles the display of the trail of the # orbit of the tip of the gyroscope. # # Right mouse toggles the display of the vectors L and # omega (angular momentum and velocity). # # Center mouse button (or left+right) zooms the view. # # ** To exit press ESC ** # # by E. Velasco. December 2004 #----------------------------------------------------- from visual import * # Initial conditions for the Euler angles phi = 0. phidot = -2.6 theta = pi/4 # Must satisfy 0<theta<pi thetadot = 1. psi = 0. psidot = 50. # Fast for the gyro to work # Constant definitions Ulenght = 1.0 # Unit of lenght in m Lshaft = 0.8 # length of gyroscope shaft Rshaft = 0.03 # radius of gyroscope shaft Hshaft = Lshaft/15. # height of cone tip of shaft Cshaft = (0,0.6,0.9) # Color of shaft Rrotor = 0.38 # radius of gyroscope rotor Drotor = 0.12 # thickness of gyroscope rotor Lcm = Lshaft/1.8+Hshaft # Distance of cm to fixed point Crotor = (0,0.5,0.8) # Color of rotor Cbraces = (1,0.1,0) # Color of braces of rotor hpedestal = Lshaft # height of pedestal wpedestal = 0.17 # Width of pedestal Cpedestal = (0.4,0.4,0.5) # Color of pedestal and base tbase = 0.05 # thickness of base wbase = 4.*wpedestal # width of base Lvector = 1.05*Lshaft +2*Hshaft CL = (1,0.4,1) # Color of angular momentum COmega = color.green # Color of angular velocity Ctrail = color.yellow # Color of the trail of the tip of gyro ShowVectors = 0 ShowTrail = False # Moments of inertia divided by mass (only from rotor) I1 = 0.25*(Rrotor**2+Drotor**2) + Lcm**2 I3 = 0.5*Rrotor**2 # Components of the angular velocity in the MOVING frame omega1 = phidot*sin(theta)*sin(psi)+thetadot*cos(psi) omega2 = phidot*sin(theta)*cos(psi)-thetadot*sin(psi) omega3 = phidot*cos(theta)+psidot # A constant of motion gL_I = 9.8*Lcm/(I1*Ulenght) Delta = (I3-I1)/I1*omega3 # Window properties. Define them before creating visual objects. #scene.width=700 #scene.height=600 #scene.fullscreen = 1 # Change it to 0 to get a floating window #scene.title='Gyroscope' scene.userspin = 0 # No rotation with mouse scene.forward = (-1,0,0) # View from the +x axis slightly down scene.up = (0,0,1) scene.range=(1.9*Lshaft,1.9*Lshaft,1.9*Lshaft) scene.ambient=0.3 scene.lights = [0.3*norm((1,-0.5,-0.2)),0.5*norm((1,0.5,0.2))] scene.autoscale = 0 label ( pos = ( 0, 0, 1.2 ), text = 'Left-Click: Toggle orbit of tip' ) label ( pos = ( 0, 0, 1.0 ), text = 'Right-Click: Toggle L and w' ) # A function that returns the three moving unit vectors def MovingFrame(phi,theta,psi): CosPhi = cos(phi); SinPhi = sin(phi) CosTheta = cos(theta); SinTheta = sin(theta) CosPsi = cos(psi); SinPsi = sin(psi) V1 = vector(CosPhi*CosPsi-CosTheta*SinPhi*SinPsi, SinPhi*CosPsi+CosTheta*CosPhi*SinPsi, SinTheta*SinPsi) V3 = vector(SinTheta*SinPhi,-SinTheta*CosPhi, CosTheta) V2 = cross(V3,V1) return (V1,V2,V3) # A function that returns an L in the y-z plane displaced by V def Char_L(V): sz = 0.017 # size of letter return [V+vector(0,-sz,3*sz),V+vector(0,-sz,0), V+vector(0,sz,0)] # Build a leter omega in the y-z plane sz_omega = 0.015 # size of letter Npts = 10 alpha0=2*pi/3 Dalpha = (2*pi-alpha0)/(Npts-1) l_omega = [] for k in range(Npts): alpha = alpha0+k*Dalpha l_omega.append(sz_omega*vector(0,cos(alpha)-1,1+sin(alpha))) for k in range(Npts): alpha = pi+k*Dalpha l_omega.append(sz_omega*vector(0,1+cos(alpha),1+sin(alpha))) letter_omega = array(l_omega) # Use a numeric array for efficiency # A function that returns a omega in the y-z plane displaced by V def Char_omega(V): char=array([V])+letter_omega # Fast numeric array addition return char # Get the vectors angular velocity and angular momentum in fixed frame (V1,V2,V3) = MovingFrame(phi,theta,psi) Omega = omega1*V1+omega2*V2+omega3*V3 L = I1*omega1*V1+I1*omega2*V2+I3*omega3*V3 OmegaScale = Lvector/mag(Omega) LScale = Lvector/mag(L) Omega_body = curve(pos=[(0,0,0),0.95*OmegaScale*Omega], color=COmega, radius=0.01, visible=ShowVectors) Omega_tip = cone(pos=0.95*OmegaScale*Omega, axis=0.05*OmegaScale*Omega, radius=0.02, color=COmega, visible=ShowVectors) Omega_label = curve(pos=Char_omega(1.05*OmegaScale*Omega), color=COmega, radius=0.005, visible=ShowVectors) L_body = curve(pos=[(0,0,0),0.95*LScale*L], color=CL, radius=0.01, visible=ShowVectors) L_tip = cone(pos=0.95*LScale*L, axis=0.05*LScale*L, radius=0.02, color=CL, visible=ShowVectors) L_label = curve(pos=Char_L(1.05*LScale*L), color=CL, radius=0.006, visible=ShowVectors) # Define the fixed support of the gyro support=frame() pedestal = pyramid(pos=(0,0,-hpedestal), axis = (0,0,hpedestal), size=(hpedestal,wpedestal,wpedestal), color=Cpedestal, frame=support) base = box(pos=(0,0,-hpedestal-tbase/2.), height=wbase, length=tbase, width=wbase, axis=(0,0,1), color=Cpedestal,frame=support) sphere(pos=(0,0,0), radius=0.01, color=Cshaft) # Articulation at the pivot # Bolts B1 = sphere(pos=(wbase/2.3,wbase/2.3,-hpedestal),radius=wbase*0.04, color=Cpedestal, frame=support) B2 = sphere(pos=(wbase/2.3,-wbase/2.3,-hpedestal),radius=wbase*0.04, color=Cpedestal, frame=support) B3 = sphere(pos=(-wbase/2.3,wbase/2.3,-hpedestal),radius=wbase*0.04, color=Cpedestal, frame=support) B4 = sphere(pos=(-wbase/2.3,-wbase/2.3,-hpedestal),radius=wbase*0.04, color=Cpedestal, frame=support) support.rotate(angle=pi/7, axis=(0,0,1)) # Define the gyro gyro=frame(visible=0) pivot = cone(pos=(0,0,Hshaft), axis=(0,0,-Hshaft), color=Cshaft, frame=gyro, radius=Rshaft) shaft = cylinder(axis=(0,0,Lshaft), pos=pivot.pos, radius=Rshaft, color=Cshaft, frame=gyro) tip = cone(pos= pivot.pos+shaft.axis, axis=(0,0,Hshaft), color=Cshaft, radius=Rshaft, frame=gyro) rotor = cylinder(pos=(0,0,Lcm - Drotor/2), radius=Rrotor, axis=(0,0,Drotor), color=Crotor, frame=gyro) # Braces of rotor cylinder(pos =(-Rrotor,0,Lcm - Drotor/3.), radius=Drotor/2, axis=(2*Rrotor,0,0), color=Cbraces, frame=gyro) cylinder(pos =(0,-Rrotor,Lcm - Drotor/3.), radius=Drotor/2, axis=(0,2*Rrotor,0), color=Cbraces, frame=gyro) cylinder(pos =(-Rrotor,0,Lcm + Drotor/3.), radius=Drotor/2, axis=(2*Rrotor,0,0), color=Cbraces, frame=gyro) cylinder(pos =(0,-Rrotor,Lcm + Drotor/3.), radius=Drotor/2, axis=(0,2*Rrotor,0), color=Cbraces, frame=gyro) ring(pos=(0,0,Lcm), radius=Rrotor, thickness=Drotor/2, axis=(0,0,1), color=Cbraces, frame=gyro) # Rotate gyro to its starting position # First rotate by phi around the z axis gyro.rotate(angle=phi, axis=(0,0,1)) # Use the new x axis (Vx) and rotate by theta Vx=(cos(phi),sin(phi),0) gyro.rotate(angle=theta, axis=Vx) # Use the final z axis (V3) and rotate by psi gyro.rotate(angle=psi, axis=V3) gyro.visible=1 # Make the gyro visible # Curve described by tip of gyro trail = curve(radius=0, color=Ctrail) dt = 0.0002 # Time step dt = 0.004 dt2 = dt/2 # Half time step # First rotate the gyro around current Omega by mag(Omega)*dt2 gyro.rotate(angle=mag(Omega)*dt2, axis=Omega) while 1: #rate(800) rate (50) # Find midtime variables CosPsi = cos(psi); SinPsi=sin(psi); SinTheta=sin(theta) phidot = (SinPsi*omega1+CosPsi*omega2)/SinTheta phi_m = phi + phidot*dt2 theta_m = theta + (CosPsi*omega1 - SinPsi*omega2)*dt2 psi_m = psi + (omega3-phidot*cos(theta))*dt2 omega1_m = omega1 +(gL_I*SinTheta*CosPsi-Delta*omega2)*dt2 omega2_m = omega2 -(gL_I*SinTheta*SinPsi-Delta*omega1)*dt2 # Get the full step variables CosPsi_m = cos(psi_m); SinPsi_m=sin(psi_m); SinTheta_m=sin(theta_m) phidot_m = (SinPsi_m*omega1_m+CosPsi_m*omega2_m)/SinTheta_m phi += phidot_m*dt theta += (CosPsi_m*omega1_m - SinPsi_m*omega2_m)*dt psi += (omega3 - phidot_m*cos(theta_m))*dt omega1 += (gL_I*SinTheta_m*CosPsi_m - Delta*omega2_m)*dt omega2 -= (gL_I*SinTheta_m*SinPsi_m - Delta*omega1_m)*dt # Get the vectors angular velocity and momentum in the fixed frame (V1,V2,V3) = MovingFrame(phi,theta,psi) Omega = omega1*V1+omega2*V2+omega3*V3 L = I1*omega1*V1+I1*omega2*V2+I3*omega3*V3 # Toggle Painting the trail and the L w vectors if scene.mouse.events: mouseObj = scene.mouse.getevent() scene.mouse.events = 0 if mouseObj.click == "left": # Toggle orbit of tip if ShowTrail == True: ShowTrail = False trail.pos=[] else: ShowTrail = True if mouseObj.click == "right": # Togle display of L and w ShowVectors = 1 - ShowVectors L_body.visible = L_tip.visible = ShowVectors L_label.visible = ShowVectors Omega_body.visible = Omega_tip.visible = ShowVectors Omega_label.visible = ShowVectors # Update the trail and the L w vectors L_body.pos = [(0,0,0),0.95*LScale*L] L_tip.pos=0.95*LScale*L; L_tip.axis=0.05*LScale*L L_label.pos=Char_L(1.05*LScale*L) Omega_body.pos = [(0,0,0),0.95*OmegaScale*Omega] Omega_tip.pos=0.95*OmegaScale*Omega; Omega_tip.axis=0.05*OmegaScale*Omega Omega_label.pos=Char_omega(1.05*OmegaScale*Omega) if ShowTrail == True: trail.append(pos=V3*(Lshaft+2*Hshaft)) # Rotate the gyro around new Omega by mag(Omega)*dt gyro.rotate(angle=mag(Omega)*dt, axis=Omega) |
From: Bruce S. <Bru...@nc...> - 2009-01-08 20:51:49
|
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? I stand however by my previous statement that the only "significant differences" are those listed. Bruce Sherwood Stef Mientki wrote: > hi Bruce, > > Bruce Sherwood wrote: >> The only significant differences that I know of between Visual 3 and >> Visual 5 are that the following have not (yet) been implemented in >> Visual 5: scene.cursor.visible, and right-button and middle-button >> mouse events. These are listed as known bugs in the statement of new >> features in the documentation for Visual 5. > you don't know yet, how good I am in finding bugs ;-) > here is subtle one, (VP5, winXP-sp2) > look very carefully at the picture, it contains 2 bugs. > The bug appears depending on the ratio of hor/ver size of the frame, > and moving either the height or width slightly, you can get to see other > variations. > > 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 20:44:10
|
hi Bruce, Bruce Sherwood wrote: > The only significant differences that I know of between Visual 3 and > Visual 5 are that the following have not (yet) been implemented in > Visual 5: scene.cursor.visible, and right-button and middle-button > mouse events. These are listed as known bugs in the statement of new > features in the documentation for Visual 5. you don't know yet, how good I am in finding bugs ;-) here is subtle one, (VP5, winXP-sp2) look very carefully at the picture, it contains 2 bugs. The bug appears depending on the ratio of hor/ver size of the frame, and moving either the height or width slightly, you can get to see other variations. cheers, Stef |
From: Bruce S. <Bru...@nc...> - 2009-01-08 20:43:09
|
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. But it was essential to invoke numpy rather than Numeric in Visual 5 because Numeric is no longer supported. In the Visual 5 documentation (accessible from the IDLE help menu), choose "Numpy module (arrays)" for documentation on numpy. Bruce Sherwood Stef Mientki wrote: > hello, > > A number of VP3-scripts uses, like this > > r = pos-pos[:,NewAxis] # all pairs of atom-to-atom vectors > > > NewAxis isn't defined in VP5, > and I can't find any information about NewAxis. > > Anyone has a clue ? > > thanks, > 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 20:30:55
|
hello, A number of VP3-scripts uses, like this r = pos-pos[:,NewAxis] # all pairs of atom-to-atom vectors NewAxis isn't defined in VP5, and I can't find any information about NewAxis. Anyone has a clue ? thanks, Stef |
From: Bruce S. <Bru...@nc...> - 2009-01-08 20:24:29
|
The only significant differences that I know of between Visual 3 and Visual 5 are that the following have not (yet) been implemented in Visual 5: scene.cursor.visible, and right-button and middle-button mouse events. These are listed as known bugs in the statement of new features in the documentation for Visual 5. Bruce Sherwood Stef Mientki wrote: > thanks Bruce, > > I didn't know that, > and indeed it works like a charm. > So now I can really test the differences between VP3 and VP5 ;-) > I'll report my findings. > > cheers, > Stef > > Bruce Sherwood wrote: >> But "hide" IS supported. It's unfortunate that there was a >> scene.hide() that was undocumented (and not implemented in Visual 5), >> but it has always been the case that scene.visible = False has worked >> in all versions of Visual. >> >> Nor am I sure that I understand what is meant by "resize not allowed >> during visible". Do you mean setting scene.width and scene.height? >> That didn't work in Visual 3, either. The following resizing works in >> both Visual 3 and Visual 5: >> >> from visual import * >> box() >> scene.mouse.getclick() >> scene.visible = False >> scene.width = 800 >> scene.visible = True >> >> Bruce Sherwood >> >> Stef Mientki wrote: >>> Bruce Sherwood wrote: >>>> That's a very strange bug in VP3; I have no idea what is the cause. >>>> I note that creating a new label after making the window visible >>>> fails to show any text, though the box surrounding the (nonvisible) >>>> text is the appropriate width. If on the other hand no label is >>>> created before the window manipulations are carried out, a new label >>>> does show text. Very strange. >>>> >>>> The only workaround that I can see is to use VP5. >>>> >>> I was afraid to get that answer ;-) >>> And yes, probably it's the best way to go, >>> but then embedding of VPython isn't possible anymore ( hide not >>> supported, resize not allowed during visible) >>> :-( >>> >>> thanks anyway, >>> cheers, >>> Stef >>>> Bruce Sherwood >>>> >>>> Stef Mientki wrote: >>>>> hello, >>>>> >>>>> the simple program below, hiding the scene for a moment, >>>>> lets the text disappear in VP3 (VP5 works ok). (winXP-sp2) >>>>> Is there a workaround ? >>>>> >>>>> thanks, >>>>> Stef >>>>> >>>>> >>>>> from visual import * >>>>> >>>>> label ( text = 'Click to show problem' ) >>>>> >>>>> while True : >>>>> rate ( 50 ) >>>>> if scene.mouse.clicked > 0 : >>>>> while scene.mouse.clicked > 0 : >>>>> scene.mouse.getclick() >>>>> scene.visible = False >>>>> scene.visible = True >>>>> >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> >>>>> 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 19:02:31
|
thanks Bruce, I didn't know that, and indeed it works like a charm. So now I can really test the differences between VP3 and VP5 ;-) I'll report my findings. cheers, Stef Bruce Sherwood wrote: > But "hide" IS supported. It's unfortunate that there was a > scene.hide() that was undocumented (and not implemented in Visual 5), > but it has always been the case that scene.visible = False has worked > in all versions of Visual. > > Nor am I sure that I understand what is meant by "resize not allowed > during visible". Do you mean setting scene.width and scene.height? > That didn't work in Visual 3, either. The following resizing works in > both Visual 3 and Visual 5: > > from visual import * > box() > scene.mouse.getclick() > scene.visible = False > scene.width = 800 > scene.visible = True > > Bruce Sherwood > > Stef Mientki wrote: >> >> Bruce Sherwood wrote: >>> That's a very strange bug in VP3; I have no idea what is the cause. >>> I note that creating a new label after making the window visible >>> fails to show any text, though the box surrounding the (nonvisible) >>> text is the appropriate width. If on the other hand no label is >>> created before the window manipulations are carried out, a new label >>> does show text. Very strange. >>> >>> The only workaround that I can see is to use VP5. >>> >> I was afraid to get that answer ;-) >> And yes, probably it's the best way to go, >> but then embedding of VPython isn't possible anymore ( hide not >> supported, resize not allowed during visible) >> :-( >> >> thanks anyway, >> cheers, >> Stef >>> Bruce Sherwood >>> >>> Stef Mientki wrote: >>>> hello, >>>> >>>> the simple program below, hiding the scene for a moment, >>>> lets the text disappear in VP3 (VP5 works ok). (winXP-sp2) >>>> Is there a workaround ? >>>> >>>> thanks, >>>> Stef >>>> >>>> >>>> from visual import * >>>> >>>> label ( text = 'Click to show problem' ) >>>> >>>> while True : >>>> rate ( 50 ) >>>> if scene.mouse.clicked > 0 : >>>> while scene.mouse.clicked > 0 : >>>> scene.mouse.getclick() >>>> scene.visible = False >>>> scene.visible = True >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> >>>> 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: Bruce S. <Bru...@nc...> - 2009-01-08 17:48:02
|
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 |
From: Bruce S. <Bru...@nc...> - 2009-01-08 17:44:14
|
But "hide" IS supported. It's unfortunate that there was a scene.hide() that was undocumented (and not implemented in Visual 5), but it has always been the case that scene.visible = False has worked in all versions of Visual. Nor am I sure that I understand what is meant by "resize not allowed during visible". Do you mean setting scene.width and scene.height? That didn't work in Visual 3, either. The following resizing works in both Visual 3 and Visual 5: from visual import * box() scene.mouse.getclick() scene.visible = False scene.width = 800 scene.visible = True Bruce Sherwood Stef Mientki wrote: > > Bruce Sherwood wrote: >> That's a very strange bug in VP3; I have no idea what is the cause. I >> note that creating a new label after making the window visible fails >> to show any text, though the box surrounding the (nonvisible) text is >> the appropriate width. If on the other hand no label is created before >> the window manipulations are carried out, a new label does show text. >> Very strange. >> >> The only workaround that I can see is to use VP5. >> > I was afraid to get that answer ;-) > And yes, probably it's the best way to go, > but then embedding of VPython isn't possible anymore ( hide not > supported, resize not allowed during visible) > :-( > > thanks anyway, > cheers, > Stef >> Bruce Sherwood >> >> Stef Mientki wrote: >>> hello, >>> >>> the simple program below, hiding the scene for a moment, >>> lets the text disappear in VP3 (VP5 works ok). (winXP-sp2) >>> Is there a workaround ? >>> >>> thanks, >>> Stef >>> >>> >>> from visual import * >>> >>> label ( text = 'Click to show problem' ) >>> >>> while True : >>> rate ( 50 ) >>> if scene.mouse.clicked > 0 : >>> while scene.mouse.clicked > 0 : >>> scene.mouse.getclick() >>> scene.visible = False >>> scene.visible = True >>> >>> >>> ------------------------------------------------------------------------------ >>> >>> 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 17:20:25
|
Bruce Sherwood wrote: > That's a very strange bug in VP3; I have no idea what is the cause. I > note that creating a new label after making the window visible fails > to show any text, though the box surrounding the (nonvisible) text is > the appropriate width. If on the other hand no label is created before > the window manipulations are carried out, a new label does show text. > Very strange. > > The only workaround that I can see is to use VP5. > I was afraid to get that answer ;-) And yes, probably it's the best way to go, but then embedding of VPython isn't possible anymore ( hide not supported, resize not allowed during visible) :-( thanks anyway, cheers, Stef > Bruce Sherwood > > Stef Mientki wrote: >> hello, >> >> the simple program below, hiding the scene for a moment, >> lets the text disappear in VP3 (VP5 works ok). (winXP-sp2) >> Is there a workaround ? >> >> thanks, >> Stef >> >> >> from visual import * >> >> label ( text = 'Click to show problem' ) >> >> while True : >> rate ( 50 ) >> if scene.mouse.clicked > 0 : >> while scene.mouse.clicked > 0 : >> scene.mouse.getclick() >> scene.visible = False >> scene.visible = True >> >> >> ------------------------------------------------------------------------------ >> >> 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: Scott D. D. <Sco...@Ac...> - 2009-01-08 05:24:38
|
Bruce Sherwood wrote: > Mouse problems I've seen on the Mac include the scrollbar "sticking" > (failing to slide), and clicking into text only to have the insertion > point be somewhere else than where you clicked. David Scherer found that > he could (temporarily?) fix such problems by clicking in the title bar > of the IDLE window. To get evidence of this -- start idle from a terminal window with a "python25 -m idlelib.idle" where python25 is the path to your python executable. You get output on stderr each time the mouse drops a line of mouse positioning. --Scott David Daniels Sco...@Ac... |
From: Joe H. <hea...@gm...> - 2009-01-08 05:24:23
|
> > Date: Wed, 07 Jan 2009 13:26:09 -0500 > From: Bruce Sherwood <Bru...@nc...> > Subject: [Visualpython-users] Mac IDLE fix > To: vpusers <vis...@li...> > Message-ID: <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 |
From: Bruce S. <Bru...@nc...> - 2009-01-08 04:40:38
|
Mouse problems I've seen on the Mac include the scrollbar "sticking" (failing to slide), and clicking into text only to have the insertion point be somewhere else than where you clicked. David Scherer found that he could (temporarily?) fix such problems by clicking in the title bar of the IDLE window. I see that there is now a Python 2.5.4 for the Mac, but its IDLE is still broken. For instance, there still is no menu option to configure IDLE. Bruce Sherwood James Mueller wrote: > Bruce, > I have both the MacPython and Enthought versions of 2.5.2 on my > macbook pro. While the IDLE in MacPython is broken as you say, the one > shipped with the Enthought distribution appears to be fine. Now they > both claim to be IDLE 1.2.2, and this seemed confusing, so I looked into > the Enthought distribution a little more. I had previous versions of it > so I checked IDLE in each of them > > EPD 2.5.2001 released July 2008 - IDLE missing configure menu > EPD with Py2.5 4.0.30002 released Oct 2008 - IDLE missing configure menu > EPD Py2.5 4.1.30101 released Dec 2008 - IDLE has configure menu > > I see that you were complaining about idle on the idle-dev mailing list > back in November, but I don't see any note to indicate a fix going in, > so I am still confused as to why the Enthought IDLE seems to work, but > the MacPython one is still broken. > > I also haven't seen any mouse problems, but that is probably because I > am just not trying the right thing to trigger them. > > -Jim > > > On Jan 7, 2009, at 1:26 PM, Bruce Sherwood wrote: > >> This has been added to the Visual 5 Mac download page: >> >> 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"). >> >> ------------------------------------------------------------------------------ >> >> 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: James M. <mu...@pi...> - 2009-01-08 04:19:38
|
Bruce, I have both the MacPython and Enthought versions of 2.5.2 on my macbook pro. While the IDLE in MacPython is broken as you say, the one shipped with the Enthought distribution appears to be fine. Now they both claim to be IDLE 1.2.2, and this seemed confusing, so I looked into the Enthought distribution a little more. I had previous versions of it so I checked IDLE in each of them EPD 2.5.2001 released July 2008 - IDLE missing configure menu EPD with Py2.5 4.0.30002 released Oct 2008 - IDLE missing configure menu EPD Py2.5 4.1.30101 released Dec 2008 - IDLE has configure menu I see that you were complaining about idle on the idle-dev mailing list back in November, but I don't see any note to indicate a fix going in, so I am still confused as to why the Enthought IDLE seems to work, but the MacPython one is still broken. I also haven't seen any mouse problems, but that is probably because I am just not trying the right thing to trigger them. -Jim On Jan 7, 2009, at 1:26 PM, Bruce Sherwood wrote: > This has been added to the Visual 5 Mac download page: > > 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"). > > ------------------------------------------------------------------------------ > 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: Bruce S. <Bru...@nc...> - 2009-01-08 03:47:22
|
That's a very strange bug in VP3; I have no idea what is the cause. I note that creating a new label after making the window visible fails to show any text, though the box surrounding the (nonvisible) text is the appropriate width. If on the other hand no label is created before the window manipulations are carried out, a new label does show text. Very strange. The only workaround that I can see is to use VP5. Bruce Sherwood Stef Mientki wrote: > hello, > > the simple program below, hiding the scene for a moment, > lets the text disappear in VP3 (VP5 works ok). (winXP-sp2) > Is there a workaround ? > > thanks, > Stef > > > from visual import * > > label ( text = 'Click to show problem' ) > > while True : > rate ( 50 ) > if scene.mouse.clicked > 0 : > while scene.mouse.clicked > 0 : > scene.mouse.getclick() > scene.visible = False > scene.visible = True > > > ------------------------------------------------------------------------------ > 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: Bruce S. <Bru...@nc...> - 2009-01-07 23:33:24
|
The message about shader program is normal. From the documentation: "Materials will work with graphics cards that support Pixel Shader 3.0 ("PS 3.0"). For details, see http://en.wikipedia.org/wiki/Pixel_shader#Hardware. Some materials may work with graphics cards that support PS 2.0, but other materials may need to be manually disabled; see instructions in the site-settings.py module in the Visual package in your site-packages folder. If the graphics hardware does not support pixel shaders, the material property is ignored. If you think you should be able to use materials but have trouble with their display or performance, we highly recommend upgrading your video card drivers to the latest version." In other words, you can suppress the shader program message by changing site-settings.py. Mouse problems in IDLE is in principle not within the province of the VPython project, nor have I seen problems with IDLE on Ubuntu Linux. However, there are serious problems with IDLE on the Mac, including mouse problems, and David Scherer is working on an alternative version of IDLE to address those issues. Conceivably this would address problems you're seeing on Fedora; I don't know. Due to personal committments, it's not clear when Scherer might be able to release an alternative to the current IDLE. (Historical note: In 2000, while building VPython, Scherer made major revisions to the relatively primitive IDLE that then existed. Later others continued his work. This year, while again working on VPython, Scherer found that various aspects of IDLE now needed attention.) Bruce Sherwood Vineyard, Michael F. wrote: > Hi Folks, > > I have built Visual 5.01 on Fedora 10. The examples and some of my earlier programs seem > to run ok, but I see some funny behavior. I get the following warning in the python shell > when I run a module: > > Vpython WARNING: error in shader program: > linking with uncompiled shader > > Also, the mouse buttons don't function properly in the idle windows. > > Does anyone have an idea of how to fix these? > > Thanks, > > Mike Vineyard > > ------------------------------------------------------------------------------ > 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: Vineyard, M. F. <vin...@un...> - 2009-01-07 22:46:49
|
Hi Folks, I have built Visual 5.01 on Fedora 10. The examples and some of my earlier programs seem to run ok, but I see some funny behavior. I get the following warning in the python shell when I run a module: Vpython WARNING: error in shader program: linking with uncompiled shader Also, the mouse buttons don't function properly in the idle windows. Does anyone have an idea of how to fix these? Thanks, Mike Vineyard |
From: Bruce S. <Bru...@nc...> - 2009-01-07 18:26:16
|
This has been added to the Visual 5 Mac download page: 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"). |
From: Stef M. <s.m...@ru...> - 2009-01-06 22:12:56
|
hello, the simple program below, hiding the scene for a moment, lets the text disappear in VP3 (VP5 works ok). (winXP-sp2) Is there a workaround ? thanks, Stef from visual import * label ( text = 'Click to show problem' ) while True : rate ( 50 ) if scene.mouse.clicked > 0 : while scene.mouse.clicked > 0 : scene.mouse.getclick() scene.visible = False scene.visible = True |
From: Bruce S. <Bru...@nc...> - 2009-01-06 04:19:09
|
<!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"> Indications in the build.log file are that no Boost libraries have been installed on your machine. See detailed discussion in the file INSTALL.txt.<br> <br> Bruce Sherwood<br> <br> German Andres Gaviria Martinez wrote: <blockquote cite="mid:fcc...@ma..." type="cite">Hello I have the following error during installation<br> <br> <br> <br> <a class="moz-txt-link-abbreviated" href="mailto:erman@german-laptop:~/Escritorio/visual-5.01_candidate$">erman@german-laptop:~/Escritorio/visual-5.01_candidate$</a> sudo make<br> Making all in site-packages/visual<br> make[1]: se ingresa al directorio `/home/german/Escritorio/visual-5.01_candidate/site-packages/visual'<br> make[1]: No se hace nada para `all'.<br> make[1]: se sale del directorio `/home/german/Escritorio/visual-5.01_candidate/site-packages/visual'<br> Making all in src<br> make[1]: se ingresa al directorio `/home/german/Escritorio/visual-5.01_candidate/src'<br> Compiling ./core/util/atomic_queue.cpp ...<br> make[1]: *** [atomic_queue.lo] Error 1<br> make[1]: se sale del directorio `/home/german/Escritorio/visual-5.01_candidate/src'<br> make: *** [all-recursive] Error 1<br> <br> <pre wrap=""><pre wrap=""><pre wrap=""> <hr size="4" width="90%"> ------------------------------------------------------------------------------ </pre><pre wrap=""> <hr size="4" width="90%"> _______________________________________________ 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></pre></pre> </blockquote> </body> </html> |
From: German A. G. M. <ger...@gm...> - 2009-01-06 01:17:34
|
Hello I have the following error during installation erman@german-laptop:~/Escritorio/visual-5.01_candidate$ sudo make Making all in site-packages/visual make[1]: se ingresa al directorio `/home/german/Escritorio/visual-5.01_candidate/site-packages/visual' make[1]: No se hace nada para `all'. make[1]: se sale del directorio `/home/german/Escritorio/visual-5.01_candidate/site-packages/visual' Making all in src make[1]: se ingresa al directorio `/home/german/Escritorio/visual-5.01_candidate/src' Compiling ./core/util/atomic_queue.cpp ... make[1]: *** [atomic_queue.lo] Error 1 make[1]: se sale del directorio `/home/german/Escritorio/visual-5.01_candidate/src' make: *** [all-recursive] Error 1 |
From: Mr G. K. <s40...@st...> - 2009-01-05 12:16:47
|
Does Vpython work with Jython? |
From: Bruce S. <Bru...@nc...> - 2009-01-02 00:39:08
|
Several people have privately expressed concern that the native-mode Visual 5 implementation on the Mac is based on Carbon rather than Cocoa. We developers are concerned, too. The problem is that Apple has begun the process of dropping support for Carbon, a decision that has caused a lot of anguish among many developers. Unfortunately, it seems to be extremely difficult (impossible?) to base Visual on Cocoa, for highly technical reasons having to do with who is the primary thread. Some months ago I posted a question about this to the cocoa-dev mailing list. The first response flamed at me for being an idiot for wanting to continue to use Carbon. The second response said roughly, "No, the poor guy has a serious problem. Years ago we faced a similar, daunting problem trying to get Java working in the Mac environment." At the moment we seem to have no option for responding to the strong need for a native-mode Mac version but to base it on Carbon. Maybe someone deeply knowledgeable in the Mac will step forward eventually with a Cocoa solution, which would be great. There is a somewhat related problem with Visual 5 on the Mac in that it is no longer possible to call Tcl functions, even in the Carbon environment. Bruce Sherwood |
From: Bruce S. <Bru...@nc...> - 2009-01-01 21:29:11
|
In Visual 5 you can read the window width and height (but to change them you first have to make the scene invisible): box() scene.mouse.getclick() print scene.width, scene.height It is true that you can't read these data in Visual 3. More generally, it's fair to say that currently VPython doesn't provide good mechanisms for creating graphical user interfaces. It's good for navigable 3D animations, but not for a variety of other uses. Bruce Sherwood Stef Mientki wrote: > hello, > > The label item has nice properties to position the text absolute in a frame, > through xoffset / yoffset, > so it's not affected by zooming. > > But it's still moves when the window is resized. > > Now the windows parameters width and height are not available, when the > window is shown. > Therefor it doesn't seem possible to position the text in the upper left > corner and keep it there, > unless you place the center in the upper left corner. > > How are others position fixed texts ? > (btw most scripts I've seen now, doesn't use xoffset / yoffset, why ? ) > > thanks, > Stef > > > ------------------------------------------------------------------------------ > _______________________________________________ > Visualpython-users mailing list > Vis...@li... > https://lists.sourceforge.net/lists/listinfo/visualpython-users > |