On Aug 31, 2:12 pm, Terry Brown <[email protected]> wrote:
> An odd bug, DnD only seems to worn on a file that's been saved. Create a new > file, enter a bunch of nodes, and DnD doesn't work. Save the file, and it > does. I think I understand what is going on. The problem is not with new/ unsaved files per se. The crucial distinction is whether the DnD happens between the same or distinct copies of Leo. When dragging between two *distinct* copies Leo to another, Qt generates just one enter event, when the drag starts in the *source* outline. Alas, when dragging from two Leo outlines, both opened with the *same* copy of Leo, Qt generates *two* enter events, one when the drag starts in the source outline, and a second when the cursor moves into the destination outline. This is unfortunate, imo. This second enter event causes problems. Indeed, Leo's present code thinks the source started from the *destination* outline, so the drop moves (or clones!) the entry position in the *destination* outline to the drop position. Not good. As I write this, I see that it may be possible to use an application- wide lockout, say g.app.dragging, to detect this case. No commander- specific lockout will work, because two different commanders are involved. I'll experiment with this lockout now. Edward -- 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.
