[opc@digitalnut .node-red]$ npm install bartbutenaers/node-red-contrib-ui-contextmenu
npm WARN Master_flow@0.0.1 No repository field.
npm WARN Master_flow@0.0.1 No license field.
+ node-red-contrib-ui-contextmenu@1.0.9
updated 1 package and audited 1250 packages in 13.621s
15 packages are looking for funding
run `npm fund` for details
found 0 vulnerabilities
@BartButenaers@Paul-Reed, coming back to the issue from this last weekend for a moment... Bart, does your node add things to the appcache of the dashboard, or is it compiled/minified to it? Paul, can you try resetting it again through chrome://... like you did before and see if it changes anything?
Thanks, I thought you found a way to determine the x and y coordinates for that button to feed into the context menu. That is what I`m desperately looking for:
A way to anchor a position on the dashboard (like a button, but could be a dummy too, which can deliver the coordinates. It would be perfect if the ui-button node issues the x,y, of the mouse and x1,y1,x2,y2 coordinates of the button area on every press somewhere hidden (msg.ui_control.x1) for example. Or a general upgrade to the ui-control node to emit x.y coordinates on every mouse press ("Output: mouse events") perhaps here:
Than would be "universal" solution and only there if needed.
To hum it may concern: "Is this an idea that could be realized? Sometimes?"
It would be great if a specific new node was created that combined the button and context menu, so instead of providing coordinates, the menu would always fall gracefully from the node itself.
Currently using coordinates, the menu appears at slightly different positions relative to the ui- button, depending upon the browser (laptop v phone v tablet).
Will try to implement it as soon a I am retired, which is in about 21 years. So please be a bit patient ....
But instead of creating combinations of nodes, "perhaps" a UI node could send:
The clicked coordinates (like we currently do)
The bounding box (minX, minY, maxX, maxY) of the element that has been clicked.
Then you can calculate in your flow where you want to show the contextmenu. E.g. when you want to have the contextmenu to appear in the center of a button, then you just calculate the center of the button yourself. (ButtonNode --> FunctionNode (calculate the location) --> ContextMenuNode).
Just a wild idea... Not sure whether this is possible, and no time at the moment to try something...
Oeps, completely overlooked your sentence in the flood of feedback I get from all over the place at the moment. But then at least we are the same wavelength
But never used the ui-control node myself, so hopefully someone else (reading this) has some time to experiment with it. Otherwise our proposal will die a slow dead here and now ...
No problem, happening myself from time to time.
Thank you for this node help to keep the dashboard clean from rarely used but sometimes useful options.
Still desperately seeking for an anchor on the dashboard to use it more often.