Skip to content
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

When setting max levels lowest child element will still be tempted to accept child elements #112

Open
northernbeacheswebsites opened this issue Jun 1, 2017 · 1 comment

Comments

@northernbeacheswebsites
Copy link

Although when you set the maxLevels to 2 for example the lowest child elements won't actually accept any more child elements which is great but when you drag something over the top of it, the child element still opens up as if it wants to accept an inside of it. From a user perspective it creates confusion because it appears as if you can put items inside of it, and it also means when you want to place an item in front or behind that lowest element this opening up gets in the way of dropping the item into place. Apart from that though this code is amazing. Thanks,

@papamurik
Copy link

I managed to come around a similar problem by adding an additional condition level < o.maxLevels to the code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants