Re: [Visualpython-users] Backwards-compatibility problems in Visual 5

[Roberto A. M. <rha...@ho...>]

> I wasn't aware of a change from list to tuple for scene.objects, but
> clearly it ought to be a tuple, not a list, as this should not be a
> modifiable sequence. In what context did it matter that it was a list
> rather than a tuple?
>

Like in the following example, when you need to recover the index of a  
previously picked object:


varCurrentObject = m.pick

(...)

#The following line gets an error on Visual 5, yet it works on Visual 3:
varCurrentObjectIndex=scene.objects.index(varCurrentObject)


-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/