callback script can be saved with file. see persistent parameter for addscript method.
So, with these parameters I can have a file on the network, and anyone who opens up the file automatically load the callback script, and once the user closes the file, the access to callback script is gone. Is that how it works?
I build a new cameraselector (shortcut “C”) that supports frameranges given in the cameraname.
This solution works very well.
Can you elaborate on that a little bit more please! This might be really helpful in my case. One issue I see with this is (if I understand it correctly), that, every user should have the same shortcut on their local machine, may be a bit of an issue to deal with?
Personally, to do this sort of thing I would have just made a new camera that moves around to each camera getting it’s transform and lens data from the other cameras. Would save having all the callback stuff to deal with. But that’s just me and I haven’t read all the posts as to why you want to do it the way that you mention.
I would have just made a new camera that moves around to each camera getting it’s transform and lens data from the other cameras. Would save having all the callback stuff to deal with.
I assumed this might be more complicated to handle in max, than just doing some kind of runtime script which works whenever I change my camera. In case I am creating a new camera which gets transforms and lens data from all cameras, I will have to run the script to create such camera everytime any of my camera changes. Not an issue, just thought if the runtime was easier, that makes the overall process more smoother, or more like realtime.
Since I am not very experienced with maxscript, I am also not sure if the runtime/callback scripts can cause a major issue when dealing with these scripts on the network? Like you said “to save all the callback stuff to deal with”?