search

code-google-com / blur-dev

Automatically exported from code.google.com/p/blur-dev
1 stars 0 forks source link

Is there any "upgrade" information to update tools that were done with the old toolset? #36

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
We had a bunch of tools we did with the first version of Py3dsmax.
There have been quite some big changes. Is there and guideline/info/hints on 
what to change, pitfalls etc?

Original issue reported on code.google.com by instinctvfx@gmail.com on 5 Aug 2011 at 10:31

GoogleCodeExporter commented 9 years ago 
Depending on the version you had, we had been trying to mimic the original 
Maxscript syntax as much as possible, but have found it to be quite buggy.  
Something like:

>>> obj = mxs.objects[0]
>>> obj.position.controller

May have worked with your old code (depending on the version) but would not 
work now.  The whole "nested attribute" problem for maxscript is a pretty nasty 
one, where controller is not a property of a position, but in this case 
"position.controller" is a property of obj.  Those kinds of cases would be the 
biggest ones, where there is no clear documentation from max on what is nested 
vs. what is an actual property.

Do you have specific examples?  What are some of the changes you are noticing - 
sorry, its been a while for me since the early iterations.

Original comment by eric.hul...@gmail.com on 8 Aug 2011 at 1:57

GoogleCodeExporter commented 9 years ago 
Sorry that was put very misunderstandable.

I was mainly referring to PyQt changes. We have a bunch of rather complex PyQt 
tools that work the old way with some custom hacks. So i was wondering if there 
are any major hickups to expect.

Regards,
Thorsten

Original comment by instinctvfx@gmail.com on 9 Aug 2011 at 7:57