Our main route to triggering tools is through right-clicking on the feature, or on the Run context menu.
This route provides the feature(s) for the tool, but many tools have additional parameter requirements.
Let's consider how we do this.
Some parameters have parameters that may be enumerated. So, for a frequency parameter, we could provide a further level of menu, where the analyst chooses from, e.g. 1 sec, 5 secs, 10 secs, 30 secs, 1 minute, 5 minutes,.... and so on up to 1 day, and then a Custom option that reverts to showing a dynamically collated dialog that allows provision of the missing parameters.
Where a tool requires start and stop time, this could be taken from the Time Controller's current filter period (which is actually stored in session state), So, for commands that require this time period, offer a submenu of From Time Controller or Custom....
Our main route to triggering tools is through right-clicking on the feature, or on the
Runcontext menu.This route provides the feature(s) for the tool, but many tools have additional parameter requirements.
Let's consider how we do this.
Some parameters have parameters that may be enumerated. So, for a frequency parameter, we could provide a further level of menu, where the analyst chooses from, e.g. 1 sec, 5 secs, 10 secs, 30 secs, 1 minute, 5 minutes,.... and so on up to 1 day, and then a
Customoption that reverts to showing a dynamically collated dialog that allows provision of the missing parameters.Where a tool requires start and stop time, this could be taken from the Time Controller's current filter period (which is actually stored in session state), So, for commands that require this time period, offer a submenu of
From Time ControllerorCustom....