Notifications
Clear all

[Closed] Visual MAXScript: Does it actually save time?

I believe Autodesk has big plans for maxScript, which may(or may not) include a new VMSE.

From Max 8 Help File
“The MAXScript debugger implements the first half of a script development and debugging environment.”

I always use MaxScript, and for semi complex interface it would be very time consuming not to imho.

There are a few problems with the visual maxscript you have to know though, if you know how to avoid these problems it will definetly be able to save alot of time. I can put up a pic of the new PolySpeed interface if you like, to put those buttons by hand would be quite dreadful.

Problems:

  1. You can have no variables to the the controlers. For example you cannot write checkbutton chb_pressMe caption:“Press” checked:checked_variable

To solve this, all changes to the controller should be done in the Open event:
on rol_Rollout open do
(
chb_PressMe.checked=checked_variable
)

  1. As you know, the visual interface can easily eat the last line below the rollout. Just add a few lines with comments below it.

  2. Be careful with copying buttons that have events in the visual editor. The events will be copied too.

It really depends on what kind of interface you have if the visual maxScript editor should be used. I only use it to place my buttons, and sometimes copy them etc, but I don’t use it for anything else.

/Andreas

I’d actually like a VMS that places controls and generates codes as you would using the relative method. (across, offset, etc)

Page 3 / 3