Just minor comment - looks like all the enhanced syntax/execute/format options for calc engine use the shift key which is great - the notes just refer to the execute button using the option key.
Thanks, I'm finding this so useful for debugging larger calculations without having to deconstruct components and split them out into separate data viewer calcs - being able to check all conditions of a Case statement in-line is a huge time saver
Would be interesting to know what enhancements under the hood are implied by the newer SDK?
Trying to find any updated specs like script parameter length and calculation statement length, sql statement length etc ...
???
I have an idea/request for the next release if possible.
99% of the time when developing in anchor-buoy solutions (or any type for that matter) when accessing the graph you want to jump to the current layouts table occurrence (the anchor) because you're usually working on that layout and thus any graph changes you're making are occurring on that anchor-buoy.
SO wouldn't it be nice to have a setting to always jump to the layout contexts TO by default when accessing the graph? The MBS search is already there, so I'm sure it could be utilised for this, where you could just grab the current layouts TO name and do a pre-search ?
This would save always having to locate the Anchor-buoy every time you go to the graph