visualpython-users

[Visualpython-users] Buttons and sliders

[Bruce S. <ba...@an...>]

Attached is a zip file of which the following is the final, test portion. 
To run the complete program you need the latest version of VPython (which 
implements full mouse control).

The test routine is shown below. Establish a normal VPython graphics window 
with a red cube in it. Then create a "controls" window named "c" and create 
two buttons and two sliders in it. The "actions" defined for the buttons 
and sliders are functions (def's) to be executed when a button comes up or 
when a slider is dragged. In the while loop, c.interact() checks for mouse 
interactions on buttons or sliders, updates their appearances, and performs 
the actions specified. The slider "value" attribute gives the 
floating-point location along the slider, whose default min and max are 
0-100. The effect is that you can control the speed and direction of the 
cube's rotation. Just for fun, the sliders are coupled together: changing 
one changes the other. The coordinate system for setting up the buttons and 
sliders has the origin in the lower left corner, and the upper right corner 
is (100,100).

The point of the exercise is to seek your comments on this proposed module 
for a VPython-based set of controls. The actual appearances of the buttons 
and sliders can obviously be improved. The key issues are whether this 
"interact" scheme looks good, useful, and easy to teach and use.

Bruce Sherwood

--------------------------------------------------

from visual import *
display(x=300, y=0, range=3, forward=-vector(0,1,1), newzoom=1)
cube = box(color=color.red)

c = controls()
bl = button(y=60, text='Left', action='setdir(1.)')
br = button(x=50, y=60, text='Right', action='setdir(-1.)')
hs = hslider(x=40, y=20, width=10, length=60, action='hsetrate()')
vs = vslider(x=20, y=0, width=10, length=50, action='vsetrate()')

def setdir(direction): # called on button up events
    cube.dir = direction

def setrate(value):
    cube.dtheta = 2.*value*pi/1e4

def hsetrate(): # called on hslider drag events
    setrate(hs.value) # hs.value is 0-100 slider position
    vs.value = hs.value # demonstrate making both sliders read alike

def vsetrate(): # called on vslider drag events
    setrate(vs.value) # vs.value is 0-100 slider position
    hs.value = vs.value # demonstrate making both sliders read alike

hs.value = 70. # mimic dragging the slider
hsetrate()
setdir(-1.)

while 1:
    rate(100)
    c.interact() # check for events, drive actions
    cube.rotate(axis=(0,1,0), angle=cube.dir*cube.dtheta)

[Visualpython-users] [Q] from demo in the web page

[Young-Jin L. <yl...@ui...>]

Hi, all.
I have a question on the demo example in the VPython home page, =
http://cil.andrew.cmu.edu/projects/visual/vpythonprog.htm.

When I ran this example, the size of the ball and rectangle are =
changing.
It seems to me that the camera position is changing during simulation.
Can I set the camera in a fixed position?=20

Thanks in advance.

YJ

[Visualpython-users] update

[Bruce S. <ba...@an...>]

Minor update to downloads on the VPython web site. New versions of the demo 
programs stonehenge.py and toroid_drag.py to use the new mouse machinery 
and implement dragging with mouse button down.

To my surprise, stonehenge worked fine after merely inserting scene.newzoom 
= 1. On the other hand, toroid_drag needed some modest restructuring.

Bruce Sherwood

Re: [Visualpython-users] [Q] VPython and IDLE

[Bruce S. <ba...@an...>]

IDLE is just a convenient environment for editing and running Python 
programs, including VPython programs. One need not invoke IDLE at all to 
edit or run a VPython program; you can use any text editor of your choice, 
and you can invoke the Python interpreter to run the program.

I don't understand your comment about "VPython has only command line 
interface." There is a command line interface available for Python, or one 
can use IDLE, etc. There is no command line interface associated with the 
Visual module which goes with Python to make the package we refer to as 
VPython.

Bruce Sherwood

--On Wednesday, October 31, 2001 15:38 -0600 Young-Jin Lee 
<yl...@ui...> wrote:

> I would like to know if VPython application can be executed outside IDLE.
> I mean, I want to create a Python application with VPython because
> VPython has only command line interface. Can it be possible?

Re: [Visualpython-users] [Q] VPython and IDLE

[Kevin C. <kj...@gr...>]

Yes.  I don't use IDLE.  I type my program using the emacs editor.  I
run it by typing "python name.py" and it works fine.  (This is on a 
Linux system, but it should work the same on a Windows system.)

On Wed, 31 Oct 2001, Young-Jin Lee wrote:

> Hi, all.
>
> I would like to know if VPython application can be executed outside
> IDLE. I mean, I want to create a Python application with VPython
> because VPython has only command line interface. Can it be possible?
> 
> Thanks in advance.
> 
> YJ
> 

-- 
 Kevin Cole, RHCE, Linux Admin  |  E-mail:  kj...@gr...
 Gallaudet Research Institute   |  WWW:     http://gri.gallaudet.edu/~kjcole/
 Hall Memorial Bldg  S-419      |  Voice:   (202) 651-5135
 Washington, D.C.  20002-3695   |  FAX:     (202) 651-5746

[Visualpython-users] New mouse machinery

[Bruce S. <ba...@an...>]

At http://cil.andrew.cmu.edu/projects/visual there is new mouse machinery, 
currently available for Windows.

As you may know, there is a problem with the current VPython mouse scheme, 
because left button down means "zoom". For that reason, dragging an object 
with the mouse is done with the mouse buttons up, which is inconsistent 
with dragging in other computer applications. As we announced some time 
ago, in late December we will change VPython so that the default will be 
that zooming is done with the "middle" button (left and right buttons or 
wheel down on a 3-button mouse, CTRL key pressed on a 1-button mouse). This 
will make it possible for the left button to be down during the dragging of 
an object.

In order to try out the new scheme right now, with the new VPython you can 
execute

	scene.newzoom = 1

and get the new behavior. In last December this statement will become 
unnecessary.

Here are extracts from the new documentation:

scene.mouse.button
Can be "none" (no buttons pressed), "left", "right", "middle" (left and 
right buttons pressed on a 2-button mouse, or CTRL key pressed with a 
1-button mouse), or "wheel" (scroll wheel pressed on some Windows mouses). 
Example: scene.mouse.button == "left" is true if the left button is down.

Here is a complete routine for dragging a sphere with the left button down. 
Note the statements for making the cursor invisible during the drag.

from visual import *
scene.newzoom = 1 # invoke new zooming with "middle" button
scene.range = 10 # fixed size, no autoscaling
ball = sphere(pos=(-5,0,0), radius=1., color=color.cyan)
while 1:
    if scene.mouse.clicked:
        m1 = scene.mouse.getclick() # wait for left button down
        if m1.button == "left" and m1.pick == ball:
            offset = ball.pos - m1.pos
            scene.cursor.visible = 0 # make cursor invisible
            while 1:
                m2 = scene.mouse
                ball.pos = m2.pos + offset
                if m2.button == "none" and m2.clicked: # up event
                    scene.cursor.visible = 1 # cursor visible
                    scene.mouse.getclick() # discard up event
                    break

If during a drag the user performs a zoom or rotate operation, at the end 
of the operation an up event is generated, followed by a down event (if any 
mouse buttons are still down).

In the new release of VPython, a few of the demo programs have had 
scene.newzoom = 1 added to them to permit dragging with the left button 
down: colorsliders, hanoi, planar, and tictac.

An unusual aspect of the new mouse machinery is that just adding the 
newzoom statement was sufficient to make the dragging work with the left 
button down. The reason is that in the past the drag was started with a 
mouse up event and terminated with another mouse up event. Now a mouse down 
event initiates the drag, and a mouse up event terminates the drag.

The new cvisual source code has been checked into SourceForge (sf.net, 
visualpython) and is also provided in the form of a zip file on the VPython 
site (in the "developers" section). If you able to do so, you could 
recompile for Linux or Unix.

We welcome your comments and suggestions about the new machinery.

Bruce Sherwood

P.S. This release also fixes a bug. The documentation claimed that you 
could discard a queue of unprocessed mouse events by executing 
scene.mouse.clicked = 0. This didn't actually work, but now it does.

[Visualpython-users] [Q] VPython and IDLE

[Young-Jin L. <yl...@ui...>]

Hi, all.
I would like to know if VPython application can be executed outside =
IDLE. I mean, I want to create a Python application with VPython because =
VPython has only command line interface. Can it be possible?

Thanks in advance.

YJ

Re: [Visualpython-users] more physics examples?

[Bruce S. <ba...@an...>]

Nice!

Very minor suggestion: You can print entire paragraphs with a single print 
statement, using triple quotes:

print """
This is a
paragraph.
"""

For additional physics programs beyond those provided in the demos that 
come with VPython, follow the links on the front page of the VPython site:

Use by students in the physics course Matter & Interactions
A module by Markus Gritsch for quickly building ball-and-spring models

Bruce Sherwood

--On Wednesday, October 24, 2001 1:04 AM -0500 Rob Salgado 
<sa...@ph...> wrote:

> I recently downloaded and installed the Windows version of VPython.
> It looks quite nice.
>
> For my first Python program, I coded something that seemed difficult
> [for me] to do using VRML with EAI/Java scripting.
>
> http://www.physics.syr.edu/~salgado/software/vpython/EFieldBuilder.py
>
> It allows the user to assemble electric charges in space
> and see the resulting electric field vectors.
>
> It's version 0.99 because it seems to crash once in a while.
> When I have more time, I'll try to reproduce the problem.
>
> I would appreciate any suggestions for improvement.
> Thanks.
>
> rob
> sa...@ph...
> http://physics.syr.edu/~salgado/
>
> P.S.
> Where can one find other physics-oriented vpython programs?

[Visualpython-users] more physics examples?

[Rob S. <sa...@ph...>]

Hello.
I recently downloaded and installed the Windows version of VPython.
It looks quite nice.

For my first Python program, I coded something that seemed difficult 
[for me] to do using VRML with EAI/Java scripting.



http://www.physics.syr.edu/~salgado/software/vpython/EFieldBuilder.py

It allows the user to assemble electric charges in space
and see the resulting electric field vectors.  

It's version 0.99 because it seems to crash once in a while.
When I have more time, I'll try to reproduce the problem.

I would appreciate any suggestions for improvement.
Thanks.


rob
sa...@ph...
http://physics.syr.edu/~salgado/



P.S.
Where can one find other physics-oriented vpython programs?

Re: [Visualpython-users] compile / rebuild-problems under Linux.

[Terje K. <te...@ma...>]

Roger Fearick <fe...@bi...> writes:

> I think I have seen this before. As I recall, it indicates that the
> source file has some character *after* that '\' (possibly as a
> result of having MS line endings (\x0a0d) rather than unix (\x0a)).

  that makes sense. in a sick way, but still. 

> A global search and replace should cure the problem.

  I got the binary to install nicely, I'll look at this if there is
  interest for it though. 

-- 
Terje

Re: [Visualpython-users] compile / rebuild-problems under Linux.

[Terje K. <te...@ma...>]

David Andersen <dm...@an...> writes:

> What happens if you install the binary rpm?

  gaah. pardon me for being difficult and looking for the source. the
  binary went in flawlessly. I'll have to work a bit to test it
  (actually, my girlfriend will have to test it, I'm just the
  installation-guy :)

  thanks.

-- 
Terje

Re: [Visualpython-users] compile / rebuild-problems under Linux.

[Roger F. <fe...@bi...>]

On 23 Oct 2001, Terje Kvernes wrote:

>   first of all, this installation is being done under Suse 7.1, with
>   all dependencies met. I've googled, search the archives and read the
>   faq, but the installation still breaks. 'rpm -v --rebuild
>   visual-2001.10.15-3.src.rpm' ends up with the following error:
> 
> g++ -g -I. -I./CXX/Include -I/usr/include/python2.1 -I/usr/include/python2.1/Numeric `gtk-config --cflags gtk gthread` -w   -c -o cvisual.o cvisual.cpp
> cvisual.cpp:26: parse error before `return'
> cvisual.cpp:26: stray '\' in program
> cvisual.cpp:75: stray '\' in program
[etc]
> 
>   I looked at the define on line 26, which is:
> 
> #define CALLF(what) Object what(const Tuple& args, const Dict& kwargs) {  \
>       return ::what(args,kwargs); \
>     }
> 

I think I have seen this before.
As I recall, it indicates that the source file has some character
*after* that '\' (possibly as a result of having MS line endings
(\x0a0d) rather than unix (\x0a)).
A global search and replace should cure the problem.

Roger.


-- 
Roger Fearick
Dept. of Physics
University of Cape Town

Re: [Visualpython-users] compile / rebuild-problems under Linux.

[David A. <dm...@an...>]

What happens if you install the binary rpm?

[Visualpython-users] compile / rebuild-problems under Linux.

[Terje K. <te...@ma...>]

  hi all.

  first of all, this installation is being done under Suse 7.1, with
  all dependencies met. I've googled, search the archives and read the
  faq, but the installation still breaks. 'rpm -v --rebuild
  visual-2001.10.15-3.src.rpm' ends up with the following error:

g++ -g -I. -I./CXX/Include -I/usr/include/python2.1 -I/usr/include/python2.1/Numeric `gtk-config --cflags gtk gthread` -w   -c -o cvisual.o cvisual.cpp
cvisual.cpp:26: parse error before `return'
cvisual.cpp:26: stray '\' in program
cvisual.cpp:75: stray '\' in program
cvisual.cpp:76: stray '\' in program
cvisual.cpp:77: stray '\' in program
cvisual.cpp:78: stray '\' in program
cvisual.cpp:79: stray '\' in program
cvisual.cpp:80: stray '\' in program
cvisual.cpp:81: stray '\' in program
cvisual.cpp:82: stray '\' in program
cvisual.cpp:83: stray '\' in program
cvisual.cpp:84: stray '\' in program
cvisual.cpp:85: stray '\' in program
cvisual.cpp:86: stray '\' in program
cvisual.cpp:87: stray '\' in program
cvisual.cpp:88: stray '\' in program
cvisual.cpp:89: stray '\' in program
cvisual.cpp:90: stray '\' in program
cvisual.cpp:91: stray '\' in program
cvisual.cpp:92: stray '\' in program
cvisual.cpp:75: end of file read inside definition
cvisual.cpp:147: parse error at end of input
make: *** [cvisual.o] Error 1

  I looked at the define on line 26, which is:

#define CALLF(what) Object what(const Tuple& args, const Dict& kwargs) {  \
      return ::what(args,kwargs); \
    }

  now, my C++ skills aren't what they might have been, but it looks
  okay to me. well, ugly, but okay. 'g++ --version' gives me 2.95.2,
  which I take to be a stable gcc release. 

  if anyone have any good idea on how to make this work I'd be
  thrilled. and please CC me answers, I'm not on the list. :)

-- 
Terje

RE: [Visualpython-users] Color / Intensity Question

[David S. <dsc...@vy...>]

> > Background on the first question.  I am looking into doing some 
> > experiments with VPython using digital video output which 
> could have 
> > some applicability to driving a scene projector. I am trying to 
> > understand what data is being generated, how many bits 
> etc., so I can 
> > decide how to encode and grab off from digital video the scene 
> > intensity data.
> 
> Surely this has much more to do with the color depth of your 
> video card 
> than with Visual.

Yes.  Visual uses OpenGL for low-level rendering, and exactly how
rasterization takes place is determined by the OpenGL drivers for your
video card.

Usually, the framebuffer will store 5-8 bits for each of red, green, and
blue.  I have never heard of a framebuffer with a separate intensity
channel.

> > On another related question. How does VPython handle 
> rendering object 
> > data which is sub-pixel?  If I for example have a 
> scene.range of say 
> > 1000 meters, and say 200x200 scene.x and scene.y, then a 
> screen pixel 
> > is on the order of 5 meters. (Math kept simple, in 
> deference to me).  
> > If I have an object that is, say a 1 meter sphere, will it 
> not appear, 
> > or only appear is it happens to be hit by some sampling process?

Again, this might conceivably depend on your OpenGL implementation.
Visual itself makes no attempt to do antialiasing (though it certainly
preserves coordinate information to subpixel accuracy).  However, some
OpenGL implementations can do screen-space antialiasing by
supersampling.

If you want to create very high-quality video from Visual, the best
approach would be to render individual frames at very high resolution
and scale them down (this is essentially a very slow supersampling
implementation).  You will need to extend Visual somehow to try to get
access to the image in the framebuffer.

Alternatively, you might explore using the POVray export to generate a
POV scene for each frame, raytrace it (with as much antialiasing as you
like) and then composite the raytraced images to form a video.

Dave

Re: [Visualpython-users] Color / Intensity Question

[Bruce S. <ba...@an...>]

Ah. Now I see what you're referring to. When you explicitly set the range, 
that turns off autoscaling, and the camera stays in a fixed location. 
Otherwise, with autoscaling in effect, you're seeing the camera move in and 
out to try to make sure that the entire scene is visible at all times. The 
autoscaling machinery isn't perfect and sometimes makes mistakes about 
whether the camera needs to move back or not.

A useful scheme is to establish the scene with its objects, then execute 
"scene.autoscale = 0" to turn off further autoscaling.

Bruce Sherwood

--On Monday, October 22, 2001 10:11 +0000 Do...@ao... wrote:

> Pentium 2 PC, 400 MHz, sort of an old machine, ATI video card...
>
> When I run things with the scene.fov, the complex appears to move back
> and forth in space, when I use the scene.range, the motion is not present.
>
> Wayne

Re: [Visualpython-users] Color / Intensity Question

[Bruce S. <ba...@an...>]

--On Sunday, October 21, 2001 21:29 +0000 Do...@ao... wrote:

> Background on the first question.  I am looking into doing some
> experiments with VPython using digital video output which could have some
> applicability to driving a scene projector. I am trying to understand
> what data is being generated, how many bits etc., so I can decide how to
> encode and grab off from digital video the scene intensity data.

Surely this has much more to do with the color depth of your video card 
than with Visual.

> On another related question. How does VPython handle rendering object
> data which is sub-pixel?  If I for example have a scene.range of say 1000
> meters, and say 200x200 scene.x and scene.y, then a screen pixel is on
> the order of 5 meters. (Math kept simple, in deference to me).  If I have
> an object that is, say a 1 meter sphere, will it not appear, or only
> appear is it happens to be hit by some sampling process?

Try it! You'll see that very small (or equivalently, very distant) objects 
don't display. There might be some question as to whether they should 
display one hardward pixel, but currently they don't. (I'm assuming you 
mean "scene.width" and "scene.height", not "scene.x" and "scene.y".)

> Oh, before I forget.  I have a simple program that looks at a
> number of objects that are rotating.  When I use scene.range
> to specify the effective field of view, it behaves nicely.  If I use
> scene.fov, there is a weird motion of the scene.  I will include a copy
> for  your amusement, probably at my stupidity...

I don't understand the issue. When I run your program using either range or 
fov, the behavior looks the same to me. Say more? What platform?

Bruce Sherwood

Re: [Visualpython-users] Color / Intensity Question

[<Do...@ao...>]

from visual import *

scene.width =3D 320
scene.height =3D 320
#scene.ambient =3D 0.05
#scene.range =3D (15,15,15)
my_fov =3D 3.1415926/4.0
scene.fov =3D my_fov
scene.x =3D 0
scene.y =3D 0
scene.lights =3D [vector(0,0,1.0)]
#scene.ambient =3D 0

art =3D frame()
topball=3Dsphere(pos=3D(0,6,0), radius=3D2, color=3D(1,0.7,0.2))
botball=3Dsphere(pos=3D(0,-2,0), radius=3D2, color=3D(1,0.7,0.2))
triangle1 =3D convex(frame =3D art,pos =3D [(2,2,2),(0,0,0),(-2,2,2)],color=20=
=3D color.red)
triangle2 =3D convex(frame =3D art,pos =3D [(2,2,2),(0,4,0),(-2,2,2)],color=20=
=3D color.blue)
triangle3 =3D convex(frame =3D art,pos =3D [(2,2,-2),(0,0,0),(-2,2,-2)],colo=
r =3D color.blue)
triangle4 =3D convex(frame =3D art,pos =3D [(2,2,-2),(0,4,0),(-2,2,-2)],colo=
r =3D color.red)
center=3Dsphere(frame =3D art,pos=3D(0,2,0), radius=3D0.5, color=3Dcolor.yel=
low)
box1=3Dbox(frame =3D art,pos=3D(5,2,0),axis=3D(0,1,0),Length=3D2,Width=3D2,H=
eight=3D6,color=3Dcolor.yellow)
box2=3Dbox(frame =3D art,pos=3D(-5,2,0),axis=3D(0,1,0),Length=3D2,Width=3D2,=
Height=3D6,color=3Dcolor.yellow)
box3=3Dbox(pos=3D(7,2,0),axis=3D(0,1,0),Length=3D2,Width=3D2,Height=3D9,colo=
r=3D(1,0,1))
box4=3Dbox(pos=3D(-7,2,0),axis=3D(0,1,0),Length=3D2,Width=3D2,Height=3D6,col=
or=3D(0,1,1))
box5=3Dbox(pos=3D(9,2,0),axis=3D(0,1,0),Length=3D2,Width=3D2,Height=3D6,colo=
r=3Dcolor.red)
box6=3Dbox(pos=3D(-9,2,0),axis=3D(0,1,0),Length=3D2,Width=3D2,Height=3D6,col=
or=3Dcolor.red)
for i in xrange(1,2000):
    art.rotate(angle =3D 0.1,axis =3D (0,1,0),origin =3D (0,0,0))
    topball.rotate(angle =3D -0.1,axis =3D (0,1,0),origin =3D (0,0,0))
    botball.rotate(angle =3D -0.1,axis =3D (0,1,0),origin =3D (0,0,0))
    box3.rotate(angle =3D -0.1,axis =3D (0,1,0),origin =3D (0,0,0))
    box3.rotate(angle =3D -0.3,axis =3D box3.axis,origin =3D box3.pos)
    box4.rotate(angle =3D -0.1,axis =3D (0,1,0),origin =3D (0,0,0))
    box5.rotate(angle =3D -0.1,axis =3D (0,0,1),origin =3D (0,0,0))
    box6.rotate(angle =3D -0.1,axis =3D (0,0,1),origin =3D (0,0,0))
    rate(30)

Re: [Visualpython-users] Color / Intensity Question

[Bruce S. <ba...@an...>]

I don't know the answer to your question about the effect of ambient light 
on the RGB values, but I can say that there isn't currently a mechanism in 
Visual to remove the border of a window. Tests show that the height and 
width include the borders, and that for very small windows (around 100 
pixels in height or width) there seems to be some minimum imposed, so that 
a window with small width and height may be more than one-half the size of 
a window whose width and height are specified to be twice that.

Bruce Sherwood

--On Saturday, October 20, 2001 23:56 +0000 Do...@ao... wrote:

> Related question.  If I specify the graphics height and width
> to be a certain size, does that include the border around the
> scene?  Can that border be turned off?

[Visualpython-users] Color / Intensity Question

[<Do...@ao...>]

If I specify the color of an object in the RGB format.  Now
suppose further that I have a specified ambient light in the
scene.  If I raise the ambient light in the scene, the object
gets brighter.  Is the signal in the RG and B channels the same
for the brighter object.  Does the additonal brightness end
up as some scaling factor on another channel?

Related question.  If I specify the graphics height and width
to be a certain size, does that include the border around the
scene?  Can that border be turned off?

Thanks in advance,
Wayne (notso) Keen

[Visualpython-users] users group join.

[Roger R. <ru...@he...>]

My name is Roger Rusack. I am a Physics prof at the University of Minnesota.
Please add my name to the name list of the Users Group.

My e-mail is Ru...@he..., ph 612-624-2322.

	Roger Rusack

[Visualpython-users] Re: Controlling the Scene

[Bruce S. <ba...@an...>]

scene.show() and scene.hide() don't seem to be documented but apparently 
are equivalent to setting scene.visible to 1 or 0. However, as Glen Rivard 
points out, making the window visible doesn't bring it to the front. For 
flexibility, we probably should separate the two issues; there should be a 
way to bring the window to the front, and there doesn't seem to be one at 
the moment.

Bruce Sherwood

--On Thursday, October 18, 2001 7:45 PM -0400 Glen Rivard 
<g_r...@je...> wrote:

> The project I'm working on requires that I control the display window. I
> need to be able to bring the display window to the top of all other
> windows. If I use scene.show() the display window does not necessarily
> appear on top of all other windows. Can you suggest a way that I can
> bring the display window to the top?

Re: [Visualpython-users] Visual 2001-10-15

[David A. <dm...@an...>]

I don't get it.   I can't reproduce this problem.   I've even re-installed 
Linux to get a completely clean system, then installed python2.1 and visual 
from our Web site - works just fine.

The first error message you are getting indicates that somehow you've got 
the wrong version of /usr/lib/python2.1/site-packages/cvisualmodule.so - is 
is possible you copied this in from someplace else?

Did you install python2.1 from our Web site or did you get it from 
somewhere else?

Re: [Visualpython-users] Visual 2001-10-15

[Ari H. <ahe...@an...>]

On Tue, Oct 16, 2001 at 04:36:17PM -0400, Michael Katz-Hyman wrote:
> I get the following error upon running python2 and then doing an
> from visual import *...
> 
> Python 2.1.1 (#1, Aug 28 2001, 19:51:39)
> [GCC 2.96 20000731 (Red Hat Linux 7.1 2.96-85)] on linux2
> Type "copyright", "credits" or "license" for more information.
> >>> from visual import *
> Visual-2001-10-15
> WARNING: Python C API version mismatch for module cvisual:
>   This Python has API version 1010, module cvisual has version 1007.

This is not the problem. It can be ignored.

> Traceback (most recent call last):
>   File "<stdin>", line 1, in ?
>   File "/usr/lib/python2.1/site-packages/visual/__init__.py", line 18, in
> ?
>     from cvisual import vector, mag, norm, cross, rotate, faces
> ImportError: cannot import name faces

This is the real problem.

> 
> I thought this was fixed?
> 
Apparantly it rebroke itself :)

DMA can fix it tho. Dave, can you also verify that the correct Makefile made
it into (and remained in) CVS?

Ari

Re: [Visualpython-users] Visual 2001-10-15

[Michael Katz-H. <mi...@go...>]

I get the following error upon running python2 and then doing an
from visual import *...

Python 2.1.1 (#1, Aug 28 2001, 19:51:39)
[GCC 2.96 20000731 (Red Hat Linux 7.1 2.96-85)] on linux2
Type "copyright", "credits" or "license" for more information.
>>> from visual import *
Visual-2001-10-15
WARNING: Python C API version mismatch for module cvisual:
  This Python has API version 1010, module cvisual has version 1007.
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
  File "/usr/lib/python2.1/site-packages/visual/__init__.py", line 18, in
?
    from cvisual import vector, mag, norm, cross, rotate, faces
ImportError: cannot import name faces


I thought this was fixed?

-Michael


On Tue, 16 Oct 2001, David Andersen wrote:

> I've built visual for Redhat Linux 7.1, Python 2.1.1 and updated our Web
> page accordingly.
>
> Included are all the pieces required to install Python 2.1.1, Numeric,
> libgtkglarea and visual.
>
> Also included is the source RPM for visual, plus the python and
> libgtkglarea pieces required to build visual.
>
>
> _______________________________________________
> Visualpython-users mailing list
> Vis...@li...
> https://lists.sourceforge.net/lists/listinfo/visualpython-users
>

-- 
/-------------------------------------------------------------\
| Michael Katz-Hyman	                  mz...@an... |
| Pittsburgh, PA USA 	       http://www.andrew.cmu.edu/~mzk |
\-------------------------------------------------------------/