did you read the previous reply to your post? There's a link in there
to a working setup.py for python2.6 + pygame.
cheers,
Bo Jangeborg wrote:
well, there is code after mouse_pos = event_pos.
I would add a assert type(event) is not long
after any function call in mouse_button_up to know when event is
changed,
then drill down the offending function.
--
claxo
I have only gotten one more trace, and that after
On Fri, 18 Sep 2009 08:10:06 +0100, René Dudfield ren...@gmail.com
wrote:
did you read the previous reply to your post? There's a link in there
to a working setup.py for python2.6 + pygame.
cheers,
Yes, thanks. The link to
http://blog.thadeusb.com/2009/04/15/pygame-font-and-py2exe/.
I
On Fri, Sep 18, 2009 at 03:36:35PM +, Kris Schnee wrote:
Could it be that I'm doing something wrong with the basic steps involved?
I can't tell you if this is causing your problems, but you definitely
don't want to be copying your .py file or anything else into C:\Python26
You should not
Lenard Lindstrom skrev:
Bo Jangeborg wrote:
well, there is code after mouse_pos = event_pos.
I would add a assert type(event) is not long
after any function call in mouse_button_up to know when event is
changed,
then drill down the offending function.
--
claxo
I have only gotten one more
I'm a little confused - you said you get a segmentation error, and you
mentioned running a debugger, but you are showing a python error. So do you
get a real segmentation fault? Like bad memory access that drops out of
python and all that? If so, you haven't captured that error in the right
kind
On Wed, Sep 16, 2009 at 1:45 AM, rygoody rygo...@gmail.com wrote:
But this right here
test = (y - y0)*(x1 - x0) - (x - x0)*(y1 - y0)
That's just the cross product of 2 vectors (which is the same as the dot
product of the 2 vectors where one is rotated 90 degrees)
the first vector is the path
Brian Fisher skrev:
I'm a little confused - you said you get a segmentation error, and
you mentioned running a debugger, but you are showing a python error.
So do you get a real segmentation fault? Like bad memory access that
drops out of python and all that? If so, you haven't captured that
Bo Jangeborg wrote:
Lenard Lindstrom skrev:
Bo Jangeborg wrote:
well, there is code after mouse_pos = event_pos.
I would add a assert type(event) is not long
after any function call in mouse_button_up to know when event is
changed,
then drill down the offending function.
--
claxo
I have