[Bf-python] Did .setEuler change between 2.32 and 2.33?

[Joseph Gilbert]

Yep. Originally this function took a f,f,f or a [f,f,f]. The mathutils lib
now has support for real eulers so this function now takes either [f,f,f],
or PyEuler type. I didn't continue the support for f,f,f, because it is
looking for 1 object not three. However, I think that this could be
reimplemented as f,f,f, [f,f,f] or PyEuler if the ParseTuple var is "O|ff"
(now that I think about it. I'll see if I can change it :)

-----Original Message-----
From: bf-python-admin at blender.org [mailto:bf-python-admin at blender.org]On
Behalf Of Lone Wolf
Sent: Tuesday, May 04, 2004 11:24 PM
To: bf-python at blender.org
Subject: [Bf-python] Did .setEuler change between 2.32 and 2.33?


I was about post my disco ball tutorial (done in Blender 2.32)
when I noticed that you released 2.33. Congrats :)

Anyway, I went ahead and upgraded blender (and also changed to
windows because my linux box died) since I didn't want to post
an outdated tut. When I tried to run the same python script
using 2.33 it got hung up on the following:

mySphere.setEuler(0,rotation,0)

I believe that it said that the parameters were of an unknown
type or something like that. I tried replacing the 'rotation'
variable with a number and still got the same error. Perhaps
there is a better way to rotate an object to a specific point?
Any suggestions would be greatly appreciated!

Thanks

________________________________________________
Get your own "800" number
Voicemail, fax, email, and a lot more
http://www.ureach.com/reg/tag
_______________________________________________
Bf-python mailing list
Bf-python at blender.org
http://www.blender.org/mailman/listinfo/bf-python