Search
-
Re: Can anyone make this more elegant/professional
Possibly. Honestly I have no idea, I've mashed this code together by doing a lot of googling and checking the mxs reference. It all seems to work but I bet it could be better. especially when working in sub object mode. -
Re: Can anyone make this more elegant/professional
(<br> global callbackItem<br> global lastSelectedObject<br> <br> fn toggleToolMode arg = (<br> toolmode.commandmode = #SELECT<br> toolmode.commandmode = arg<br> )<br> <br> --ev returns the event that fired the callback<br> --nd returns the node<br> fn CallbackFnWacomFixSelection ev nd = (<br> <br> --stores the current… -
Re: Can anyone make this more elegant/professional
That's pretty cool. From what I can see, the code looks pretty good (without knowing the language). If this was in Python, then I'd probably be able to give you better feedback. -
Re: Can anyone make this more elegant/professional
That's simply to reduce the risk of another script overwriting the variable so we're clear. As far as the rest of the script goes - if it works you're good. There's not really enough code there to provoke any bugs. -
Re: Can anyone make this more elegant/professional
There's a bug i've found which ill try sort today, or if anyone else wants to have a crack at it :) If your in "attach" mode it bugs out and changes your selection type. -
Re: Can anyone make this more elegant/professional
Right, im being more ambitious with this now....can anyone find any issues with this? trying to get it working now properly with sub object mode. Also can anyone explain why this means? "ev nd" i have no idea, i just followed the maxscript reference. Ideally test this out with a wacom :) but woks fine with a mouse too.…
6 results