This is because a pressed control key typically means a different behavior. There is no action on right click while a control key is pressed, because there is no binding for this. Not even a selection update, because there are no default bindings for the right clicks on the body. The design of the actions registered is not stacking. That means if you register multiple actions for the same binding, only the first one found will be executed.
At least IIRC. The DataModificationExample [1] shows how to attach a body menu on right click by performing a row selection first. By adapting that to your use case you should be able to get your stuff working. Thanks for the quick reply! It appears I have misunderstood the usage of the statemask. How to show the Eclipse Move context menu in project explorer Ask Question. Asked 7 years, 4 months ago.
Active 5 years, 4 months ago. Viewed 2k times. Regards, Pavitra. Improve this question. P 11 5 5 bronze badges. Move shows for me with a ordinary folder and file, it does not show when a Java package folder is selected. This is presumably because different processing is required. The code of the mouse listener doesn't necessarily have to live in Sprotty, though. Are you suggesting that we rather put the entire code into the sprotty-theia integration or keep it in the applications only?
In the end, I think it also depends on how relevant the cross-platform use case for Sprotty diagrams is that is, if we want to be able to define a Sprotty diagram once, and use it with minimal effort also in different platforms, such as Theia, Eclipse RCP, VSCode. Because if this use case is very relevant, then it imho makes sense to have a common way of defining context menus inside Sprotty and have integration code such as sprotty-theia that is translates those menus into the native way of rendering menu items in different platforms.
If this use case is not relevant, then I guess it should be fine to have the context menu as part of the integration code to provide a framework for defining those.
Leaving context menu support entirely to the application as opposed to the platform might lead to code duplication though, as the code for defining menu items, rendering them on a platform, and sending actions back to the action dispatcher on-click would probably always be the same for each platform Theia, etc.
I think I would tend to having "Sprotty-native support" for menu items to be able to specify them as part of the Sprotty diagram; but I do get your point to avoid having to cope with menu items, registries and the like in Sprotty. So I'd understand, if you prefer to keep it out and keep menu item support outside of Sprotty in sprotty-theia or even GLSP only. Ok, let's include native support for context menus. We should have proper documentation of all first-class features at some point Skip to content.
Star New issue. Jump to bottom. Labels enhancement. Milestone v0. Linked pull requests. Add support for context menus The solution you suggested works!
Thank you! Well, actually this simple operation should work in QTP - and not such a hack be necessary to achieve it We are also using QTP 10 java addin Eclipse. The issue is that we are not able to recognize the objects properly. Are you using the same objects. If yes, could you please tell me which properties you are using to identify these objects. Thanks in advance.
Kind regards, Vimal. Problem solved, thanks for your help.
0コメント