A combo-box input control was implemented in Mathcad Prime 7.0 and other web controls from Mathcad 15.0 convert to the combo-box type input control in Mathcad Prime. However, we are investigating the scope of scripted controls. Outside different control UI (like the slider, which is something we do want to get to), I'd be very interested in what extra functionality gets used with a scripted control that isn't yet something that can be done with the combo-box in Prime 7.0. Many of the customer worksheets we've seen utilize simple scripts for controls that essentially setup a control in much the same way you can do with the combo-box (scripted controls were added in Mathcad before web controls, and I think a lot of users moved to the easier to setup web controls when they were added simply because they covered all the setup the user needed). However, we have more complex examples where additional functionality is used (for example, having the contents of a control dependent on the setting of an earlier control). It would help us understand the scope of the project if we could get some input on that additional functionality.
The loss of Control Object functionality impedes any who would add cost-schedule-performance realism through selection of listed or conditionally linked product specs over analytic "vaporware". As a practicing system engineer /architect, I've resisted the Matlab movement. My extensive analytical toolset, ability to rapidly tailor, add, or expand its capabilities, and mentoring of others are a direct result of Mathcad's intuitive, equation-based utility and quick-to-master versatility. Now, as Mathcad 15-M050 sunsets, Prime 8.0 and beyond must preserve the best of Mathcad if I and colleagues are to argue successfully for the continued licensing of PTC products.
PLEASE support us as your advocates. Again, ease-of-use and realism are what sway corporate purchasing managers. Restoring object control "buttons" will provide a tangible, readily beneficial feature. Please do. Thanks.
Generally, controls can be used for structuring workflow tasks:
1. At the beginning of a calculation to control input variables e.g.; the combo -box. It needs an option to make the chosen input permanent though so it is easier to pick up work the next day. 2. Checking calculation progress and or results. Here controls are needed to classify and to accept or reject calculation results. It would be best if results are colour coded when exceeding a given threshold and have the option to be discarded. 2a. For conducting a calculation with non-standard values e.g.; setting safety factors to unity in order to check limits. Such a settings is best colour coded to mark this change so that no oversight might happen. 3. After calculation a control comes in handy when exporting results to a file. Choose a file from a combo-box like control and get a message whether, at which time and to which file it has been exported. Ideally, this control would have a counter for repeated calculations so that the file name is extended by that counter. This is valuable for parameter studies.
Raiko
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
