Hello,
I'm trying Visual v4 beta14 with Python 2.5 on my computer.
It's nice to find v4 support texturing and transparency besides of the
improved display quality.
However, after replace my v3 with the v4 beta 14, the vpython program
doesn't response the keyboard input any more! I also tried beta 14 with
Python 2.4, it doesn't work neither.
I don't know if you guys have the same problem or it's cause by some
other reason. Simply try this
########################################################
from visual import *
while 1:
rate(10)
if scene.kb.keys: # is there an event waiting to be processed?
print "key is pressed!"
s = scene.kb.getkey() # obtain keyboard information
if s=='a':
print "a is pressed!"
if scene.mouse.clicked:
scene.mouse.getclick()
print "mouse is clicked."
#########################################################
On my computer (winxp home), the script does response the mouse
click but not the key press.
Should I go back to v3.1?
Thank you!
Ting

Hello,
I've just installed vpython on Fedora 6 and I got the same problem with
gtkglarea. The rpm of gtkglarea installs the package in /usr/local/lib
so you have to move it to /usr/lib/ and then it works fine.
hope it helps
Paco

Book Monday 9th July to Wednesday 11th July 2007 in your calendar!
EuroPython 2007, the European Python and Zope Conference, will be held in
Vilnius, Lithuania. Last year's conference was a great success, featuring
a variety of tracks, amazing lightning talks and inspiring keynotes. With
your participation, we want to make EuroPython 2007, the sixth EuroPython,
even more successful than the previous five.
Talks, Papers and Themes
------------------------
This year we have decided to borrow a few good ideas from PyCon, one of
which is to move away from the 'track' structure. Instead, speakers are
invited to submit presentations about anything they have done that they
think would be of interest to the Python community. We will then arrange
them into related groups and schedule them in the space available. In the
past, EuroPython participants have found the following themes to be of
interest:
* Science
* Python Language and Libraries
* Web Related Technologies
* Education
* Games
* Agile Methodologies and Testing
* Social Skills
In addition to talks, we will also accept full paper submissions about any
of the above themes. The Call for Refereed Papers will be posted shortly.
The deadline for talk proposals is Friday 18th May at midnight (24:00
CEST, Central European Summer Time, UTC+2).
Other ways to participate
-------------------------
Apart from giving talks, there are plenty of other ways to participate in
the conference. Just attending and talking to people you find here can be
satisfying enough, but there are three other kinds of activity you may wish
to plan for: Lightning Talks, Open Space and Sprints. Lightning Talks are
very short talks that give you just enough time to introduce a topic or
project, Open Space is an area reserved for informal discussions, and
Sprints are focused gatherings for developers interested in particular
projects. For more information please see the following pages:
* Lightning Talks: http://www.europython.org/sections/events/lightning_talks
* Open Space: http://www.europython.org/sections/events/open_space
* Sprints: http://www.europython.org/sections/sprints_and_wiki
Your Contribution
-----------------
To propose a talk or a paper, go to...
* http://www.europython.org/submit
For more general information on the conference, please visit...
* http://www.europython.org/
Looking forward to seeing what you fine folk have been up to,
The EuroPython Team

From the on-line help in the section on "Controlling Windows":
scene.objects is a list of all the visible objects in the display named
"scene"; invisible objects are not listed. For example, this makes all
(visible) boxes in the scene red:
for obj in scene2.objects:
if obj.__class__ == box # can say either box or 'box'
obj.color = color.red
You could use similar code to make all the visible objects invisible.
Not the same thing, but note too that you can make a window named
"scene" invisible by "scene.visible = False".
Concerning deleting objects, see the section in the on-line help on
"Deleting an Object", where you'll see that making an object invisible
doesn't delete the object from memory, because you might choose to make
it visible again later. But if you reuse the name of that invisible
object, it becomes eligible for Python to delete it from memory, because
there is now no way to access the object (to make it visible again).
Bruce Sherwood
John Salerno wrote:
> Hi everyone. I just started using the visual module and I think it's
> pretty neat so far. But one thing I couldn't find in the documentation
> was a way to clear the current "scene" completely. I know to delete
> something you can just set the visibility to 0 (although this seems
> not to work all the time), but if you have a lot on the screen and
> want to clear it all, is there a way to do this?
>
> Thanks,
> John Salerno

Hi everyone. I just started using the visual module and I think it's
pretty neat so far. But one thing I couldn't find in the documentation
was a way to clear the current "scene" completely. I know to delete
something you can just set the visibility to 0 (although this seems
not to work all the time), but if you have a lot on the screen and
want to clear it all, is there a way to do this?
Thanks,
John Salerno