On Fri, 27 Mar 2015 06:57:41 -0500 "Edward K. Ream" <[email protected]> wrote:
> On Thu, Mar 26, 2015 at 6:55 PM, john lunzer <[email protected]> wrote: > > > > > if I have the mouse in my hand anyway I tend to use it for bringing > > up a node menu. > > > > Good point. Right clicking should be the same as act-on-node. 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. > 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. > 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. 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. There was a discussion about making mouse clicks into bindable things like keys, which is how X windows at least treats them. They could be seen as three keys in two flavors: LeftClick, LeftDblClick, MiddleClick, MiddleDblClick, RightClick, RightDblClick (if we ignore for now mice with more than three buttons. And triple clicks :-) So you could have bindings like: contextmenu-show ! tree = RightClick active-path-expand ! tree = Ctrl-LeftClick * or * active-path-expand ! tree = LeftDblClick I'm not saying we need to do this whole clicks as keys thing, although it would be nice, but be aware that active_path.py and bookmarks.py both, with the right settings, act on double clicks. Act-on-node is an interesting idea, but in practice I'm not sure it's used that much, e.g. active_path.py and bookmarks.py both have multiple actions they can take on a node, so a single "do your thing now" event isn't really helpful. Also there's the issue I mentioned the other day of whether it's ok for the single-click callbacks to always fire, even for double-clicks. Currently I think they do, they could be suppressed using the timer system I mentioned, but first we should think of at least one case where it matters... ha, found one... with "single click to edit already selected node" enabled, pretty much essential if you're using double click for something else, double-click on an already selected node doesn't fire the double click action. But I don't think we should focus on that directly, rather review what we want big picture wise. Cheers -Terry > 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.
