Ed -- your code is surely better than mine since it handles undo-ing
I do want to be sure I understand the new code
-- moves forward in tree
-- relies on 2 new functions
p.positionAfterDeletedTree()
u.afterDeleteMarkedNodes()
Right? There was a error with my version of Leo when I simply turned
your code into a button because I would need to use a bzr version (I
am not a regular Launchpad + bzr user).
But I think I see a flaw in using Marked nodes for deletion (at least
for what I wanted)
I anticipated only deleting a group of selected nodes locally. But If
I mark a cloned node, the other cloned nodes are also marked and hence
deleted. This contrasts with Leo behavior for what happens if you
simply delete a node that happens to be cloned (not using a marked
set). The local node disappears and the other cloned nodes are
unaffected, which is what I think users would expect to happen if they
select and delete a group of nodes.
Maybe a concept of local marking or selection is needed.
Also completely separate issue: I think delete in context_menu has
unexpected undo / redo effects. Redo after Undo often fails, but you
can Undo again. Must be related to different undoable code when
deleting nodes through context_menu verses Outline menu
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
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.
