On Thu, Jun 26, 2008 at 4:59 PM, Terry Brown [EMAIL PROTECTED]
wrote:
But Move would be trickier of course, given the rules about not being
your own ancestor. So I guess the polite way would be to attempt to
move all the nodes selected to the target position, and if it fails,
abort and do
On Thu, Jun 26, 2008 at 11:30 AM, Terry Brown [EMAIL PROTECTED]
wrote:
To be as versatile a tool as possible it seems to me that Leo needs to
be able to select and operate on groups of nodes. I've seen the
groupOperations.py plugin, and it's ok, but I don't really think it
addresses the
On Thu, 26 Jun 2008 11:37:32 -0500
Edward K. Ream [EMAIL PROTECTED] wrote:
The simplest thing that could possibly work is to mark nodes
(possibly in a way distinct from standard marks) and then support
commands to operate on such marked nodes. Say commands such as:
clone-marked-nodes,
What limitations would you put on the node's that could be
simultaneously selected? Would they all have to have a common parent
node? If not, what would Leo do with a paste of nodes from different
parents?
TL
--~--~-~--~~~---~--~~
You received this message
On Thu, 26 Jun 2008 14:42:30 -0700 (PDT)
TL [EMAIL PROTECTED] wrote:
What limitations would you put on the node's that could be
simultaneously selected?
None... which is already the case with nodes that can be simultaneously
marked, of course.
Would they all have to have a common parent
