On Tuesday, December 20, 2011 10:37:12 AM UTC+7, btheado wrote:
I wasn't aware of the multi-select functionality.
Nor was I, I guess the fact that cloning requires marking nodes first
caused me to assume same for deletes.
Actually now that I think about it, I haven't had a need for bulk deletes
yet, I guess because I'm still so tentative about my data. . .
> While poking around I notice another workaround option is to use
@settings to add another entry to the context menu:
Very cool, works a treat thanks!
> I didn't see a way for "@data contextmenu_commands" to override other
context menu entries (i.e. to replace the existing "Delete" menu entry)
Too bad, would be nice.
Now that I think about it (I can hear the groans), that would also be a
straightforward way (maybe?) to handle all the mouse-driven events, in
learning about
- active_path.py
- act-on-node
- @url vs @mime, bookmarks etc
it seems there needs to be an easy standardized way to control what happens
when the user left-clicks (single vs double, "new" vs when already
selected) as well as the right-click context menu.
With the same facility and clarity that keybindings do now.
There could be a global default for a given event, then more specific
actions defined for specific @types, maybe even user-defined new ones, tied
into commands and scripts.
Right now, if you select multiple nodes and right-click, some of the
options offered operate on all nodes selected, but others only on one at a
time.
Others only appear in the first place if you have a single node selected.
I'm not complaining about this, just pointing out that there does seem to
be a need to rationalize this area of the UI.
To simplify things, perhaps have the user-added context options only show
when single nodes are selected, as for example happens with "open
containing folder" - such a facility might also provide the basis for
overriding Terry's multiple-delete code with the regular command in that
context.
Did a little further digging and found these enlightening
https://groups.google.com/forum/#!topic/leo-editor/em3Jn8GguYw/discussion
https://groups.google.com/d/msg/leo-editor/-xheznGVc9c/ZTJdwtyLZa4J
I think I tend to agree with Edward about prefering to just not deal with
multiple selected nodes, the ability to mark nodes and their specifically
targeted commands seems much safer.
Not to mention the value of setting things up so you can just keep your
hands on the keyboard. . .
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/leo-editor/-/BnTH-B_mAsoJ.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/leo-editor?hl=en.
