Oh so use to that…i keep putting maxscript into C, java into maxscript and god knows what I’m puting into C and I want kill the developers of lua…but it’s all fun…
Just wondering, why couldn’t this be achieved by making multiple toolbars? E.g. Make one toolbar for “Studio tools”, and users can make their own custom ones as they see fit. I believe max allows one to export their set of toolbars, so you easily pass around the .cui file and load it up on each machine, and that would save you the hassle of handling all this stuff manually (making the toolbox UI, remembering what each toolbar has (serializing/deserializing its contents), making it as robust and bugfree as the existing solution). All these things cost time and effort, as you know, so no point reinventing what is already there.
But I can only guess you have some really custom needs that the current toolbar mechanism can’t accomplish.
But then again, max is pretty flexible in its UI configuration.
Just my thoughts.
Don’t tell em that! I’m getting paid to do this stuff!!
I think the general idea is to keep the toolbox together in one place/window and allow the addition of standalone scripts, without the need to convert them to macros.
We’re having problems with macro’s having to be copied locally when the machines start as it is.
But you are right, that would work.
Cheers
Shane