-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Drop inside other layouts does misplace drop at end of components #58
Comments
I'm having the same problem. I've grouped a few components in a CssLayout which I want to drag and drop as a single item. But dragging over other components composed the same way shows that the drop can be shown within that component. Tried getting around the problem using the AcceptCriterion.accept() but am not able to distinguish between a correct placement and one within subcomponent. |
The fix mentioned above is specific for the DDCssLayout, but I think most other DD layouts would need a similar fix too... |
Is there any chance this will still be fixed? I am having the described problem. |
The Issue is open since almost 6 years now. |
When the components which are placed inside a DDxxxLayout are themself containers, the drop can be done inside such a layout.
The result is then, that the droped component is placed at the end of the layout and not in the place of the drop.
Here a example screenshot where the DDCssLayout is used, and the components to drag&drop are VerticalLayouts with two button on them.
As long as we drag it over the VerticalLayouts it works fine, but when the drop indicator shuffles inside the VerticalLayouts things get messy.
Sample code with the default DefaultCssLayoutDropHandler drop handler active
The text was updated successfully, but these errors were encountered: