Start Building Professional
Web Apps Today

Hello,

The issue is not reproduced locally. The grid row is removed after the response is received from the server. 

Please, try to use the latest dataprocessor libraries (attached). The dhtmlxdataprocessor_debug.js gives you the information about data that is sent and received from the server 

If the problem persists, please provide the direct link to problematic page

I have altered your sample file included with DHTML Suite.

I have altered the dhtmlGrid\samples\drag_n_drop\drag_grid.html file.

I simply included the dhtmlxdataprocessor.js and then associated a dataprocessor to mygrid3 on lines 85-88.  As you can see, eventhough the dataprocessor is not being called, by simply creating one for the grid it stops the grid row from being removed when the drag and drop occurs.  It simply strikes out the row.

This is the problem I do not quite understand. 

As explained above, I initially did not have a dataprocessor associated with my grid and everything worked fine.  Now I want to be able to delete rows from the grid (as well as drag and drop) so I needed to associate a dataprocessor with the grid as shown in the example.

Thanks

Dear Michael,

We use Data Processor when we want to send data to the server.

In your example oDP.setUpdateMode("off"). So, Data Processor doesn't send data automatically and it is necessary to use oDP.sendData().

And another issue is that you didn't set any server-side script which will process the received changes:

oDP = new dataProcessor(some_script);

The row will be deleted only after the necessary response will be received from the server:

Please, take a look at the sample in the documentation: dhtmlxGrid/samples/dataprocessor/savedata_grid.html

The article is dhtmlxGrid/doc/articles/Dataprocesor_usage.html

Yes, I completely understand how to use the dataprocessor, I have used it many, many times.  I think we are having a mis-understanding as to my question.

Let me try to explain again.

Initially I had no dataprocessor for my scenario.  I simply had a tree on the left pane of layout and a grid on the right.  I would click through tree and grid would change on the right hand side according to data associated with each folder.

I was able to drag and drop a row from grid (which represented a file) onto another folder.  For the tree_onDrop event, I send an dhtmlxAjax.post request to update the database which would move files in database from one folder to another.  Everything worked fine.

Now I wanted to enhance this for user to also be able to delete rows from the grid...which would NEED a dataprocessor.  The dataprocessor properly works in my real application.  I can highlight rows and delete using .sendData to a server-side script.

My issue is wandering why this screws up the drag and drop feature??  When I had no dataprocessor associated to grid, the drag and drop would remove row automatically from grid as shown in my previous attached example.

So, you don't want to call dataprocessor processing for row which dragged from grid to tree...

In this case you can try to use the following approach:

1) you should set flag which means that row is dropped to tree:

tree.attachEvent("onDrag",function(sid,tid,bid,sObj,tObj){
  if(sObj!=tree)  sObj._skipDeleteProcess = 1;  /*if item is dropped from another object*/
  return true
})

2) then you need to make a small modification in the dhtmlxdataprocessor.js:

please, locate this.obj.attachEvent("onBeforeRowDeleted",function(rowId){

...

and replace it with:

this.obj.attachEvent("onBeforeRowDeleted",function(rowId){

if (this._skipDeleteProcess){this._skipDeleteProcess=0; return true;}

...

I'm certainly not opposed to using the dataprocessor for both situations. 

I am using the dhtmlxAjax.post for the tree_onDrop event because I need to not only send information from the grid but also for target folder.  How would I send my target folder id along with the dataprocessor information when performing drag and drop, since dataprocessor information only passes grid information?

If there is a way to send this information as well, I would certainly rather use the dataprocessor for both situations rather than having to modify the .js file for any reason.

Any suggestions?

Thanks again. 

In the previous posts you wrote that a row becomes crossed out after drag-n-drop. The provided approach is the only way to avoid this behaviour.

The parent item from the tree can be added into the dataprocessor request using userdata (userdata of changed row is also sent to the server). 

In case of moving several rows at once, onDrop event handler gets the list on moved rows:

tree.attachEvent("onDrop",function(sid,tid,...){

var arr = sid.split(",");

for(var i = 0; i < arr.length;i++){

/*your code here*/

}

}) 

It is possible to send all changed data with one request:

dp.setUpdateMode("POST",true)
  or
dp.setUpdateMode("GET",true)

Please, see details about the parameters which is passed to the server: dhtmlxGrid/doc/articles/Dataprocesor_usage.html

Sorry, for the misleading information. Actually only grid onDrop contains the list of ids in the first parameter. 

geSelectedId() method of the grid returns the list of selected items. So, there is another approach you can try to use:

var dragged_ids = "";

grid.attachEvent("onBeforeDrag",function(){

dragged_ids = grid.getSelectedId();

return true
})

tree.attachEvent("onDrag",function(sid,tid,bid,sObj){

if((sObj==grid)&&(dragged_ids == grid.getSelectedId())){

var arr = dragged_ids.split(",");

for(var i = 0; i < arr.length;i++){

/*your code here*/

}

}

return true
})