Hi folks, Currently the node-red-ui-contextmenu node can be displayed at a location that is specified: In the input message. For example when you click on an SVG shape, the node-red-contrib-ui-svg node sends the mouse-click coordinates in the output message, which can be used by the contextmenu …

Hey @dceejay , @Paul-Reed , Nice work! Thank you both for the assistance! I really should add a simple example to the contextmenu node's readme page, to show the cooperation with the button widget (once the feature is on NPM).

Just tweaking the position a little makes the menu appear in a more natural position relative to the button icon; [pos] [flow] [json] PS - As I use a common menu across all pages, I load the 'message based' menu from context - so I only have to edit it once to make global menu changes.

I may be reading this incorrectly, but the 'touchstart' event does not return msg.position or msg.coordinates. cheers

[image] greenembrace: the 'touchstart' event does not return Hi Daniel, I see here that @dceejay has added it to the buttonClick event. But don't see any other button related event (e.g. touchstart) there. So expected the same behaviour... Bart

Hi Bart, Specifically I was interested in your SVG nodes output and should have said such in the message, but as it related to the 'contextmenu' I put it here. I don't know where to place the menu. I could just put it in the top corner but on a 7in screen that annoying.

@greenembrace for now, is there any reason you are using touchstart over click? Click should work on a touch screen & does contain coordintated. @BartButenaers we need to handle this differently. the touch events present their pageX and pageY coordinates in a different property to click. e.g... /…

[image] Steve-Mcl: Click should work on a touch screen & does contain coordintated. Steve, tried that this morning but (if I'm not mistaken) it didn't work on my Android phone. The touchstart worked fine. [image] Steve-Mcl: So we can fix touch events like this... Thanks for having a …

Don't need to support anything legacy as far as I can see Bart. It just didn't work for a touchscreen when using touchstart. TBH, most users would instinctively choose click. And even if they did choose touch events, the odds are even smaller they would be using the context menu and odds reduce eve…

[image] Steve-Mcl: Don't need to support anything legacy as far as I can see Bart Seems I had posted an incorrect link. This is the issue . For the "click" event we currently (npm version) send this output: [image] But the dashboard button: [image] Sends this when clicked: [image] Don'…

Contextmenu location

Developing Nodes

BartButenaers 1 May 2020 06:33 51

Nice catch! I have created a new issue for the SVG node. Will need to refactor the coordinate related fields in the output message anyway in the 2.0.0 release, to use the same fields as the other UI nodes (as described above in this discussion). Will keep you updated!

Topic		Replies	Views
[Announce] node-red-contrib-ui-contextmenu Share Your Nodes	55	5522	8 December 2021
[ANNOUNCE] node-red-contrib-ui-contextmenu - typedinputs Share Your Nodes	6	1189	25 July 2020
Announce node-red-contrib-ui-svg : feedback request Share Your Nodes	42	5920	2 October 2019
Node-RED Worldmap Popup's requiring right click for button to function Dashboard	11	1604	2 August 2021
Context Menu position General	21	1880	5 May 2020

Contextmenu location

Related topics