You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rule priorities can be changed in two ways: by changing the rule properties in the properties panel (SetPriorityAction), or by shifting the priorities in the rule tree (ShiftPriorityAction). The second method does not work for selected recipes, though, mainly because the selected recipes are not reflected in the SimulatorModel.
Recipe priorities can only be changed by manually changing the control program.
CtrlLoader.changePriority (untested!) does the work of changing the control programs so that new priorities are reflected, but to invoke it, SimulatorModel should be adapted to include the selected recipes.
Reported by: rensink
The text was updated successfully, but these errors were encountered:
Having an explicit set of selected actions (rules + recipes) would also allow getting rid of some strange (erroneous) selection behaviour: if you select a recipe, a rule also gets selected because currently the assumption is that every resource must be selected.
Rule priorities can be changed in two ways: by changing the rule properties in the properties panel (SetPriorityAction), or by shifting the priorities in the rule tree (ShiftPriorityAction). The second method does not work for selected recipes, though, mainly because the selected recipes are not reflected in the SimulatorModel.
Recipe priorities can only be changed by manually changing the control program.
CtrlLoader.changePriority (untested!) does the work of changing the control programs so that new priorities are reflected, but to invoke it, SimulatorModel should be adapted to include the selected recipes.
Reported by: rensink
The text was updated successfully, but these errors were encountered: