I can't seem to reproduce this (I get consistent results between both
methods), but I definitely agree it sounds like a bug. I wonder if there's
some kind of accuracy issue associated with one of them, being that the
values are so high (or low, in this case). What version/platform are you on?
-Nathan
-----Original Message-----
From: Frank Rueter
Sent: Saturday, April 16, 2011 3:12 PM
To: Nuke Python discussion
Subject: Re: [Nuke-python] ypos values
I dare say that's a bug
On Apr 17, 2011, at 2:39 AM, John RA Benson wrote:
hello -
just curious - would anyone know why these values are different? xpos
seems to be the same. Besides float and int...
nuke.selectedNode()['ypos'].value()
# Result: -13028.0
nuke.selectedNode().ypos()
# Result: -13033
thanks
JRAB_______________________________________________
Nuke-python mailing list
[email protected]
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
_______________________________________________
Nuke-python mailing list
[email protected]
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
_______________________________________________
Nuke-python mailing list
[email protected]
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
