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
Problem
The annotator's right click / context menu can get crowded; especially if there are a lot of applets and states registered to the project. This makes the menu less accessible and potentially problematic in low viewport scenarios.
Request
Put the create states into its own submenu
Put the track functions into its own submenu
Put the applet functions into its own submenu
These submenus could appear/disappear on mouseover/mouseout and are likely another div that is adjacent to the current menu. Alternatively, these submenus could behave like the video settings and timeline settings menus and have a back button and require clicking.
Could also investigate using browser.menus.overrideContext instead
The text was updated successfully, but these errors were encountered:
I switched around the initializing of this a bit in moving it to tator-js. The code still lives in annotation.js; but it uses the custom menu's web component as an interface which isn't great. I think we want to have a signal defined coming off the canvas like: "right-click event" and have the higher-order code (annotation-****) make the menu and all that.
Category
Feature Request
Problem
The annotator's right click / context menu can get crowded; especially if there are a lot of applets and states registered to the project. This makes the menu less accessible and potentially problematic in low viewport scenarios.
Request
create
states into its own submenutrack
functions into its own submenuapplet
functions into its own submenuThese submenus could appear/disappear on
mouseover
/mouseout
and are likely another div that is adjacent to the current menu. Alternatively, these submenus could behave like thevideo settings
andtimeline settings
menus and have aback
button and require clicking.Could also investigate using
browser.menus.overrideContext
insteadThe text was updated successfully, but these errors were encountered: