MAXSCRIPT any new features since 2015 ?

[Anonymous]

Hi,

I'm using maxscript in max 2015 for 2 years now and found that debugging feature is far from what we can expect in year 2017

I looked at "what’s new in Maxscript" for 2016, 2017, 2018... 

I found interesting feature in Dictionary Value class and DataPair Value but did not see anything related to debugging.

For example very frustrating:

- Max is completely frozen while in break(), user cannot even copy variable name from the source code and past it in the watch.

- User don’t know which break() in encounter if source code contain more than one break() >> Add a break param !

- Max is not completely frozen while a messagebox is on screen (ex: need an OK to disappear) You can go to source code, select text area & copy but you discover as soon as you past the content that the clipboard content is the messagebox text 😞

And by the way, 2017 users should be able to add & remove breakpoint without modifying the source code. Trace feature should be also available.

Any good news on that part ?

Regards,

FRED

[istan]

yep. i agree. maxscript is simple, easy but dead.

debugging was always a joke..

c++ sdk has breakpoints, watches and "Debug+Continue" which allows DLL code changes while runtime..

[kevinvandecar]

Yes, it is true that MAXScript is a purely a scripting language, and as such traditionally does not have a strong effort to build a true debugger for it. Even on the Python side, there is no strong support for debugging. In versions prior to the PyMxs module, you could use something like the JetBrains PyCharm, but even that is not working since PyMxs came along.

As istan said, debugging is considered a "professional" feature, and is a given for C++ and C# areas. Both of those environment support debugging with robust features coming from the Visual Studio environment.

Sorry for not so good news, but hope it helps.

kevin