Changes between Initial Version and Version 1 of Ticket #7651


Ignore:
Timestamp:
Sep 13, 2008, 1:07:45 PM (12 years ago)
Author:
bill
Comment:

Hi youngho,

Hmm, well I'm sure there are cases when the designer will want to copy, and other cases where the designer will want to paste (ie move) the item.

The thing that concerns me is that if the two trees share the same store, even with your patch, dragging an item from Tree 1 to Tree 2 typically won't make the item disappear from Tree 1.

So I'm not sure that this patch helps much but I'll consider changing it for 1.3. Can you explain how this patch improves your application? After this change, dropping onto Tree 2 doesn't remove the item from Tree 1, right?

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #7651

    • Property Milestone changed from tbd to 1.3
    • Property Type changed from defect to enhancement
    • Property Summary changed from Patch for tree dndSource to Tree: if two trees have same store then drag should move item, not copy it
  • Ticket #7651 – Description

    initial v1  
    11Hello,
    22
    3 Working dnd item on a tree, if sources are the same than model didn't create new item and just pasteItem.
     3When dragging/dropping within the same tree, drop calls model.pasteItem() to be called instead of model.newItem(), effectively moving the item.
    44
    5 I think this kind of work criteria is
    6 
    7 Not source is the same
    8 But the sources share with a same store or not.
    9 
     5I think the criteria for calling pasteItem() should be whether or not the two trees share the same store.