0

I'm using Dojo dnd version 1.7.2 and it's generally working really well. I'm happy.

My app maintains many arrays of items, and as the user drags and drops items around, I need to ensure that my arrays are updated to reflect the contents the user is seeing.

In order to accomplish this, I think I need to run some code around the time of Source.onDndDrop

If I use dojo.connect to set up a handler on my Source for onDndDrop or onDrop, my code seems to get called too late. That is, the source that's passed to the handler doesn't actually have the item in it any more.

This is a problem because I want to call source.getItem(nodes[0].id) to get at the actual data that's being dragged around so I can find it in my arrays and update those arrays to reflect the change the user is making.

Perhaps I'm going about this wrong; and there's a better way?

Harold
  • 1,584
  • 1
  • 12
  • 20

2 Answers2

1

Ok, I found a good way to do this. A hint was found in this answer to a different question: https://stackoverflow.com/a/1635554/573110

My successful sequence of calls is basically:

var source = new dojo.dnd.Source( element, creationParams );
var dropHandler = function(source,nodes,copy){
  var o = source.getItem(nodes[0].id); // 0 is cool here because singular:true.
  // party on o.data ...
  this.oldDrop(source,nodes,copy);
}
source.oldDrop = source.onDrop;
source.onDrop = dropHandler;

This ensures that the new implementation of onDrop (dropHandler) is called right before the previously installed one.

Community
  • 1
  • 1
Harold
  • 1,584
  • 1
  • 12
  • 20
-1

Kind'a shooting a blank i guess, there are a few different implementations of the dndSource. But there are a some things one needs to know about the events / checkfunctions that are called during the mouseover / dnddrop.

One approach would be to setup checkAcceptance(source, nodes) for any target you may have. Then keep a reference of the nodes currently dragged. Gets tricky though, with multiple containers that has dynamic contents.

Setup your Source, whilst overriding the checkAcceptance and use a known, (perhaps global) variable to keep track.

var lastReference = null;
var target = dojo.dnd.Source(node, {
    checkAcceptance(source, nodes) : function() {
        // this is called when 'nodes' are attempted dropped - on mouseover
        lastReference = source.getItem(nodes[0].id)
        // returning boolean here will either green-light or deny your drop
        // use fallback (default) behavior like so:
        return this.inhertied(arguments);
    }
});

Best approach might just be like this - you get both target and source plus nodes at hand, however you need to find out which is the right stack to look for the node in. I believe it is published at same time as the event (onDrop) youre allready using:

dojo.subscribe("/dnd/drop", function(source, nodes, copy, target) {
  // figure out your source container id and target dropzone id
  // do stuff with nodes
  var itemId = nodes[0].id
}

Available mechanics/topics through dojo.subscribe and events are listed here http://dojotoolkit.org/reference-guide/1.7/dojo/dnd.html#manager

mschr
  • 8,531
  • 3
  • 21
  • 35
  • Thanks for your reply. I appreciate the help. I don't know what you mean by "there are a few different implementations of the dndSource" ... Can you clarify? I'm using the one in Source.js. The .subscribe technique has the same problem I describe in my question. If my subscription gets called after the built in one, the item has already been removed from the source. I don't want my program to depend on the order of the callbacks. – Harold Jul 11 '12 at 18:06
  • there is a dnd api specific for dijit.Tree, theres some in dojox.. Is it dojo/dnd/Source? Either way, implement a dndSource.checkAcceptance(source, nodes) then - ill fill out blank – mschr Jul 12 '12 at 21:53
  • 1
    oh, didnt notice your answer below :p – mschr Jul 12 '12 at 22:02