dojox.mdnd.AreaManager Can't handle multiple dragHandleClass

[Andrew Muraco]

Description: When working with two drag and drop areas (I was using 2 GridContainers?, but this should apply to anything that uses AreaManager?) Where each GridContainer? has a specific dragHandleClass, Items won't drag and drop correctly when added to the first Area since the AreaManager? doesn't attach to the dragHandle. This is even more problematic when the dnd areas are nested, since the wrong node will become the dragHandle.

GridContainer? overwrites the dragHandleClass during initialization, since areaManager is a global singleton of AreaManager?, it overwrites this property for any other Containers that are using areaManager.

Note: acceptTypes/dndType aren't enough to fix the problem, AreaManager? doesn't attach to the right elements!

Workaround: Use the same class for all GridContainer? dragHandleClass so that they don't change the areaManager and let acceptTypes/dndTypes sort out which dnd area it is allowed to drop on. Doesn't really help with styling though.

[Andrew Muraco]

Likely fix is to have AreaManager? contain an array of dragHandleClasses and append to it as needed.

[bill]

The mdnd code seems abandoned. Closing ticket unless a patch is supplied.