Hmm, I think there's already a command that displays the context menu (emailing on my phone or I'd check).
I think act-on-node was originally supposed to be a tree context specific plugin hook type thing. Cheers -Terry On March 27, 2015 4:51:27 PM CDT, "Edward K. Ream" <[email protected]> wrote: > >On Fri, Mar 27, 2015 at 8:52 AM, 'Terry Brown' via leo-editor < >[email protected]> wrote: > >> >> I feel I'm missing bits of this thread, but let's proceed cautiously, >a >> rodent hater such as yourself, Edward, might not be the best at mouse >> use analysis :-) >> >> Right clicking on a node brings up the context menu (an on by default >> plugin). This is too much of an expected behavior to change. >> > >I agree completely. act-on-node should bring up a context menu. And >to >change my mind a bit, it will bring up a context menu even if it is >empty >or only has one item in it. > > >> Currently double clicking enables editing the node headline, this >> > would >> > > mean that editing a headline would only be available via >keyboard. I >> > > don't have a problem with it, but it's worth noting. >> > > >> > >> > I agree. Double clicking *anywhere* in a headline should start >> > headline editing. >> >> Where you click in the headline has made no difference since the Tk >> interface went away, the iconbox / elsewhere distinction existed only >> there. >> > >Right. So what I was saying is there will be no real change. > >> >> > Assigning these meanings to right clicks and double clicks will >> > minimize changes to Leo's code base and will preserve all required >> > functionality for mouse users. >> >> I'm not sure, but it seems you're proposing hard-wiring double click >to >> edit headline and right click to act-on-node. >> > >No. I was proposing to let things remain as they are, as much as >possible. > > >> >> I don't think we should do this. There are at least two plugins >which >> use double-click for their own ends. There's also a setting which >> allows editing of a node headline with a single click *if* the node >was >> already selected. This sounds inconvenient, but I use it all the >time >> without noticing it. >> > >Thanks for mentioning these fine points. I'm sure we can > >accommodate them somehow. > >My present thinking is that act-on-node will be synonymous with >right-clicking a node. For now, the simplest thing that could possibly >work >would be to leave double-clicking strictly alone. > >There was a discussion about making mouse clicks into bindable things >> like keys, which is how X windows at least treats them. > > >I'd like to avoid all this for now. Really, all I want is for >act-on-node >(a real command that can be bound to any key) to work like a right >click in >a headline. That's a big step forward. Everything else can wait, imo. > >Even just extending act-on-node will require some real >behind-the-scenes >work, presumably a collaboration with contextmenu.py. That's another >reason why I want to limit this project. > >Edward > >-- >You received this message because you are subscribed to the Google >Groups "leo-editor" group. >To unsubscribe from this group and stop receiving emails from it, send >an email to [email protected]. >To post to this group, send email to [email protected]. >Visit this group at http://groups.google.com/group/leo-editor. >For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
