drag and drop solution

[lesouef]

easy to isolate for the browser suite, remove it temp.
fyi, even if it does not fix it, I made my tests using the smart client, also started from the developer, and ondrop gets triggered on records.
my current env was xp + 5.0.1.
I am now using 5.1rc2 where ondrop does not work at all.
should be fixed for 5.1 final, Servoy said...
Soyons patients...

[rgansevles]

I am now using 5.1rc2 where ondrop does not work at all.

lesouef,

Can you try this with 5.1 rc3?

Rob

[lesouef]

I am using rc3 now, still the same, smart client drops nothing, not even on records like the original release.
web client mode: all ok.

[ROCLASI]

I am using 5.1rc3 and drag & drop works fine for me in the smart client.
I am using it to populate table views.

Are you using return DRAGNDROP.COPY or return DRAGNDROP.MOVE in your onDrag method ?

[rgansevles]

I am using rc3 now, still the same, smart client drops nothing, not even on records like the original release.
web client mode: all ok.

Can you create a small sample and attach this to a case in our support system?

Rob

[lesouef]

Robert,
answer is no. I don't even know what it does. I am still looking for the doc, and even a working example, and I am not the only one obviously, viewtopic.php?f=22&t=13507
the weird thing is that it works in web mode, but this maybe a lucky side effect.
there maybe an explanation in the wiki, but no way to access that for me (account created and confirmed but never worked...) and no way to re-create one.

Rob,
I could, I am sure you'll locate the error instantly if you confirm that it works, but I'd rather understand the beast myself.

[ROCLASI]

Robert,
answer is no. I don't even know what it does.

Then there is your issue.
The onDrag needs to allow the drag to happen. You accomplish this by returning either one of those constants.
When you return nothing or return DRAGNDROP.NONE then the drag won't happen and therefor the onDragOver will never trigger.
In the onDragOver you have to allow the Drop by returning true or false, true means you will allow the drop and onDrop will trigger.
So it's sort of a cascading approach. If you disallow it somewhere in the chain the rest will simply not trigger.

the weird thing is that it works in web mode, but this maybe a lucky side effect.

I think so too.

there maybe an explanation in the wiki, but no way to access that for me (account created and confirmed but never worked...) and no way to re-create one.

Just send an email to Servoy, they will fix/reset it for you.

[lesouef]

DRAGNDROP is true after startDrag, selectex indexes are correct (output to console).
then I drag over the destination table, the dragOver is not triggered... what can block this event?

[ROCLASI]

DRAGNDROP is true after startDrag

Not sure what you mean by that. DRAGNDROP holds 3 possible constants that you can use.

Code: Select all

DRAGNDROP.NONE
DRAGNDROP.COPY
DRAGNDROP.MOVE

See the Application > Constants > DRAGNDROP node in the Solution Explorer

You use this constant as a return value in the startDrag event.

Code: Select all

return DRAGNDROP.MOVE

If you don't the dragOver will never trigger.

[lesouef]

A bit better using DRAGNDROP.MOVE (what the hell is the difference, copy returns 1, move returns 2...)
I now get the "forbidden drag" sign instead of nothing and the onDragOver is triggered, but that's all, no way to drop. I am obviously missing a step...
Just checked the wiki (I was mislead by some wrong links you can find in some places...), there is no real explanation, 3 times the same startDrag example...
Probably why I already gave up on Servoy 2 years ago... How did you find your way?

[lesouef]

our posts got crossed, but actually, my answer is the same...
off for dinner, getting kind of fed up...

[ROCLASI]

Hi Lesouf,

Can you show me the code of your startDrag and onDragOver methods ?

[lesouef]

// attached to source table
function startDrag(event)
{ var data = [];
var selection = foundset.getSelectedIndexes();
for(i in selection)
{ application.output("id selected="+selection[i]); // to check
data.push(foundset.getRecord(selection[i]));
}
event.data = data ;
return DRAGNDROP.MOVE;
}

//attached to dest table
function onDragOver(event)
{ var source = event.getSource();
if(source && event.data)
{ return DRAGNDROP.COPY;
}
}

function onDrop(event)
{ application.output("drop seen");
var $order_id = forms.main.orderid ;
// Check the event object for multiple product records
for(i in event.data)
{ var record = event.data[i]; //application.output("search_r="+record.productname);
if (foundset.getSize()>0) // Check if product already in order
{ var fs = foundset.duplicateFoundSet();
if(fs.find())
{ fs.productid = record.productid;
if(fs.search()) // product exists in order, increment qty
{ fs.getRecord(fs.getSelectedIndex()).quantity += 1;
}
else if(foundset.newRecord()) // product did NOT exist, add a new record
{ orderid = $order_id ;
unitprice = 99 ;
productid = record.productid;
unitprice = record.unitprice;
quantity = 1;
discount = 0.0;
}
}
}
else //add new record not really smart but did nto spend time to clean this
{ foundset.newRecord();
orderid = $order_id ;
unitprice = 99 ;
productid = record.productid;
unitprice = record.unitprice;
quantity = 1;
discount = 0.0;
}
}
}

thx for help, but I am a bit fed up to bother you (other dev people) for the lack of proper ref for this new feature...

[ROCLASI]

Doing a quick scan over your code I believe the problem lies in this method:

Code: Select all

function onDragOver(event) {
    var source = event.getSource();
    if(source && event.data) {
        return DRAGNDROP.COPY;
    }
}

You should use return true if you want to accept a drop on this element. False if you don't.
Also I believe the getSource will give the source object from the draggedover object. Not from the dragged object.
Anyway, the following code should work.

Code: Select all

function onDragOver(event) {
    var source = event.getSource();
    if(source && event.data) {
        return true;
    } else {
        return false;
    }
}

thx for help, but I am a bit fed up to bother you (other dev people) for the lack of proper ref for this new feature...

I understand Paul Bakker is working hard on this (on the wiki). It seems they like to put it out when it's all done, instead of releasing smaller parts of it.

[pbakker]

I understand Paul Bakker is working hard on this (on the wiki)

Indeed, we are working hard on this and we will release the separate bits when done, just like we have done so far.

Paul