What's new:
Fixed / Addressed issues:
- A more efficient code interpreter stack. Please test your frameworks if you can now work on a lesser stack value. YMMV, but we do know that it is significant enough to warrant a check. For those who don't know, you can relaunch Mote using the rocket icon on the toolbar, and set the value for stack size to a lower value, with a minimum of 1, though we'll add handling for values less than 1M in 1.0.4. We tested a 5M stack framework at 512kb, w/ few notable side-effects.
- Wrote a more mature solution to the 2-level code block level limit in MapToolScript. Nesting tested as far as 5 levels. Possible to go up to 50, maybe more. Please test if the solution is comprehensive.
- Improved the Token Properties Editor (formerly Viewer) behavior. Newly added tokens have their properties set if there is on property type set to default for the campaign. If so, the Editor will populate with views right away, when visible.
- Corrected macroLinkText behavior (SE ticket #56). This is important because people apparently used the 3-argument version, expecting it to still trigger when there is no impersonation. The source in Mote and even in MapTool, for macroLinkText does not explicitly allow this behavior, meaning that a hack was done somewhere during the event processing, allowing for such. That this stopped in Mote, means we corrected this long standing bug in MapTool, though it may mean some scripts out there that were built under this premise, will not work anymore. We advise to review the wiki entry, and pass an empty string (i.e. "") for the 3rd argument, which will make the macro link function properly, in all respects.
Fixed / Addressed issues:
- Fixed HTML initial refresh issue
- Fixed minor issue toggling Token Bar visibility.
- Seems the code folding in the editor got turned off. It's back on now.
- SE tickets #54-62