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
Presently, the plugin APIs allow a plugin to create, act on and remove additional menu items to the canvas contextual menu.
This works well and is really useful. For example, in JavaScript you can use this to create a boundaried area.
Please can we have the ability to do these for other contexts such as waypoint, route, track and AIS target? This would open up great possibilities for custom actions on these objected. As an example, it would be possible to have a custom action on an AIS target such as making a DSC call, collision avoidance calculations, logging details etc.
The text was updated successfully, but these errors were encountered:
In my recently published PointUtility script the user needs to select a waypoint. This is impossible at the moment. The script has to search through all waypoints working out which is the nearest. This is just one example of why this enhancement is needed.
I do not use the set viz and set grey options. I just remove the menu item when not applicable.
The above would be great.
This is how the canvas context menu looks when the PointUtility script is running Copy mark would be moved to the waypoint context menu where it belongs.
Some of the ideas I am toying with might need a lot of menu items.
I have been reflecting on how it would be great if we could create sub-menus. This may be too much at this time, but while you are in there, perhaps you could think about this.
Presently, the plugin APIs allow a plugin to create, act on and remove additional menu items to the canvas contextual menu.
This works well and is really useful. For example, in JavaScript you can use this to create a boundaried area.
Please can we have the ability to do these for other contexts such as waypoint, route, track and AIS target? This would open up great possibilities for custom actions on these objected. As an example, it would be possible to have a custom action on an AIS target such as making a DSC call, collision avoidance calculations, logging details etc.
The text was updated successfully, but these errors were encountered: