Hi all!
I have a scripted simpleobject(or whatever) plugin, where is add from time to time new features and new parameters.
Whenever i load a scene which includes an object which was build with an older version of the scripted plugin, the object can’t be loaded correctly.
I always searched for some better explanation for the “on update” code then in the help, but found not really answers. So i will try to find some answers here …i hope it’s ok.
…soo … how does “on update” work?
I have a scripted plugin where i first declare the parameters, then the rollouts with the UI, then the “on buildmesh do” and then the “tool create” mouse code.
As told above, when i’m adding another parameter the objects from older scriptversions doesn’t load correct. It seems so that the parameters are reset to the defaultparameter or completly deleted.
If i understand it correct, the “on update” event can take the parameters from the old scriptversion and put it to the correct parameters from the new scriptversion. …but how??
Another question is how the “remap:” thing works.
I also would be happy if i can see a real world example somewhere :-/
This was a problem in Max 4, when updating plugins it could kill the existing parameters. If I remember you had to add any new parameters to the end of the list. if you added them in the middle some where they it would kill all those below it. Been a long time since Max 4 but I remember things like this happening.
The update handler is only called as far as I know if you have an instance of the plugin loaded in the scene and you change and eval the script. It is not called when a file is loaded and the plugin has been changed. Use on load or on postLoad for this.
nah!
It’s not a max4 problem, but i tried your suggestion and put the new parameters to the end of the parma block, but it doesn’t change anything in max4 and max2008.
The Object (instance?) will be loaded together with all other objects with the scene and when max needs to know what to do with this Object, then the scripted plugin with the correct classId will be used/evaluated …right?
When this Object loads into max, it should have all parameters and controller stored in it’s paramblock – the params have (unique?) names!
What i can understand from the help is that the “on update” event offers you some strategies (keymap?) for backing up values of params which maybe have an new paramname.
What i don’t understand is why it can’t use params which names doesn’t have changed and that’s why i thought the “on update” event can fix this behave.
if you want, i can upload an example with the old and new script.
Very odd as I’m writting scritped plugins all the time and I don’t see those problems. I would have to see what you are doing to be able to help you more. It could have been custom attributes that had the issues in Max 4 that I was talking about.
ok …i found out what happens:
I use some rollouts in the userinterface and whenever i added a new param in one of the blocks, not only the complete paramblock becomes “leveled”, but also all blocks before this block.
Is there any way to have different paramblocks AND more then one Rollout in the UI?
parameters main rollout:params_one
(
param1 type:#worldunits ui:ui_param1 default:3.0
)
parameters main rollout:params_two
(
param2 type:#worldunits ui:ui_param2 default:3.0
--this would be the new param
param3 type:#worldunits ui:ui_param3 default:3.0
)
..
rollout params_one "ONE"
(
spinner ui_param1 "Something:" type:#worldunits range:[0,99999,param1]
)
rollout params_two "TWO"
(
spinner ui_param2 "Something:" type:#worldunits range:[0,99999,param2]
-- the new UI element
spinner ui_param2 "Something:" type:#worldunits range:[0,99999,param2]
)