Usage without attaching to specific elements about ctxmenu HOT 3 CLOSED

Thanks for your feedback and your kind words 😊
I haven't had much time to look at your code, but I had a glance. If I understand you correctly, you want to add APIs to control the lifecycle of the menu instead of relying on events doing it for you, in other words, control the opening/closing programmatically, right?
I think there's no reason not to have this, in fact, I had some similar requests in the past, because of the open closeMenu function, which is private at the moment.

Feel free to prepare a PR, I'll be happy to review it.
Please consider the following things:

• naming should be consistent: either show and hide, or open and close. I wouldn't want to mix it. I prefer show and hide and maybe we should rename/delete the private open closeMenu function to avoid future confusion
• The github pages file (./docs/demo.js) doubles as a manual test file, as there are no automated tests (yet). Feel free to add some buttons to the page to showcase the feature, or some hidden global functions.
• I've seen you've added tsdoc comments to the interface. If you could also add the documentation to the README.md that would be absolutely fantastic 💯

Thank you!

from ctxmenu.

The private open closeMenu method might not be required at all after your change, so if you can replace it with the new show hide method, feel free to delete it...
In your current implementation there are similar functions both for show and hide, which calls for confusion... 🙂

from ctxmenu.

Great! I will give it go in the next couple of days.

from ctxmenu.