Changes between Initial Version and Version 1 of Ticket #863
- Timestamp:
- Feb 26, 2017 11:38:19 PM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #863 – Description
initial v1 1 Load Plugin is used to force an update of plugin models that may have changed but somehow not triggered an auto update. This works fine if the category at the time is **not** Plugin Model. However if it is "Plugin Model" and a plugin is selected on the fit page, load will clear the model dropdown box, but does not clear the rest of the model GUI stuff on the fit page. Strangely, if the model that had been chosen is a new style plugin and the user then tries to change a parameter and run the model everything behaves though the model dropdown remains blank (suggesting no model is currently "active" for that fit page. However, doing the same thing with an old style plugin causes an error that throws a rather unhelpful error message suggesting a thread problem along with a more useful error that the parameter being modified does not exist. 1 Load Plugin is used to force an update of plugin models that may have changed but somehow not triggered an auto update. This works fine if the category at the time is **not** Plugin Model. However if it is "Plugin Model" and a plugin is selected on the fit page, load will clear the model dropdown box, but does not clear the rest of the model GUI stuff on the fit page. If the user then tries to change a parameter and run the model (e.g. by hitting return) throws an error. If the user then goes to the model selection drop down and reselects the model all is well again. 2 2 3 3 4 {{{ … … 13 14 }}} 14 15 15 Not sure why this does not also throw an error with new style models but if it is going to work the drop down should not be blank. 16 Interesting factoid: there are 4 types of models: new style (e.g. copied from the built in), created using simple model editor (essentially new style), old style plugins, and the sum/multiply models which remain a mix of styles. This last type in fact seems to be quite happy even when the drop down is cleared - i.e. it does not throw the error and in fact continues to work fine when parameters are changed as if it is loaded at some deeper level? maybe deep copy issue? 16 17 17 18 Possible solutions:
