I have a runtime designer that has been working very well until my upgrade to the latest version of .NetHTML5 (Beta 3).  I could not figure out why I could no longer drop any of my controls on a child panel that is intended to contain children (such as a panel).  I then noticed the new property "AllowTargetsPropagateToChildControls"  and found this link to an "Issue"  http://support.visualwebgui.com/issue/ViewIssue.aspx?ID=10727 I have tried all combinations of true and false of this property for child and parent controls and can not get it to work the way it used to.  The best I can do is get the dragdrop event to raise on the parent even though I have the DragTargets property set to both parent and child.  I am hoping there is something I am not understanding and there is a way to fix this.    I can provide simple example if requested.

[Edit: sorry, original link was incorrect]

 Hi,

Firstly, the name of this property has changed in 6.4.0 Release e and it now is AllowDropTargetsPropagation with explanation "A flag indicating whether this component allows its drag target to propagate to its contained components". The meaning of this is the exact opposite of what you have understood (I think). It means that if your Button would be inside a Panel, you could set DragTargets for the Panel and set AllowDropTargetsPropagation = true and you could drag the button to the same controls as set for Panel.DragTargets.

As for your breaking behaviour, then you are correct. This is a breaking behaviour documented in the breaking changes article here.  Please let me know if this description is hard to understand. 

Hope this helps,

Palli

 Hi Dave,

When writing up a better description for you on the new and enhanced implementation of the Drag & Drop mechanism in 6.4.0 d and later, it was a bit confusing and not providing the results we intended. We finally tracked it down to a bug which caused the Source in the DragDropEventArgs not being consistent. This bug has now been fixed in the upcoming 6.4.0 Release f.

I added a new section in the breaking changes article on the new properties and how they work. They will give you huge optimizations in some scenarios. Please view the new section here.

Please note that until we will release this fix, your results are bound to be confusing, so I recommend that you hang on until the fix will be available and then again take it for a spin and report any problems you may find.

Palli