Hi Isomorphic,
please see this modified online testcase (v11.1p_2018-07-14):
Changed:
Now, dragging right Bin3/Blue part onto left Bin 1/Blue Cube does not result in an entry under Blue Cube and that one being a folder, which I would expect.
I did read your docs
but I like the isFolder:false for leaf nodes, so that they don't have a plus icon if empty.
From how I understand the docs, this should work as I expect, because otherwise having the API canDropOnLeaves does not make sense at all.
In my application I use a DS with a field for isFolder and a folderDrop-handler (in Java/SmartGWT) and it is behaving like the sample.
Best regards
Blama
please see this modified online testcase (v11.1p_2018-07-14):
Changed:
Code:
isc.PartsTreeGrid.create({ ID:"myTree1", data: partsTree1, canReorderRecords: true, canAcceptDroppedRecords: true, [B]canDropOnLeaves: true,[/B] canDragRecordsOut: true, dragDataAction: "move" }),
I did read your docs
Whether drops are allowed on leaf nodes.
Dropping is ordinarily not allowed on leaf nodes unless canReorderRecords is set.
The default action for a drop on a leaf node is to place the node in that leaf's parent folder. This can be customized by overriding folderDrop().
Note that enabling canDropOnLeaves is usually only appropriate where you intend to add a custom folderDrop() implementation that does not add a child node under the leaf. If you want to add a child nodes to a leaf, instead of enabling canDropOnLeaves, use empty folders instead - see Tree.isFolder() for how to control whether a node is considered a folder.
Dropping is ordinarily not allowed on leaf nodes unless canReorderRecords is set.
The default action for a drop on a leaf node is to place the node in that leaf's parent folder. This can be customized by overriding folderDrop().
Note that enabling canDropOnLeaves is usually only appropriate where you intend to add a custom folderDrop() implementation that does not add a child node under the leaf. If you want to add a child nodes to a leaf, instead of enabling canDropOnLeaves, use empty folders instead - see Tree.isFolder() for how to control whether a node is considered a folder.
From how I understand the docs, this should work as I expect, because otherwise having the API canDropOnLeaves does not make sense at all.
In my application I use a DS with a field for isFolder and a folderDrop-handler (in Java/SmartGWT) and it is behaving like the sample.
Best regards
Blama
Comment