@jypre I think I understand your desire to follow this approach, but I can’t but help think if rather than call javascript code, if you created an action widget to do the same and use the event catcher to trap your double clicks, you would also have an action widget that can be used from any trigger.
- My idea is to code into tiddlywiki; objects widgets and actions so it follows the standard code patterns, increases modularity and extends the features.
- Whilst I see value making a simpler, easy to apply, widget I can see using the genesis to define or enhance an existing widget also has its value, and may allow you to avoid Javascript and the need to save and reload to install (Although this depends on what you want to occur in the action)