-
Notifications
You must be signed in to change notification settings - Fork 75
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
Gridster inside gridster #123
Comments
When using Drag, the function is called twice "addWidgetFromDrag(field, $event)", would have solution? |
Hi, I've tried it and it seams that most of things works. I only found an issue with resize handler and maybe with drag handler if it's the same for both - parent and nested gridster. |
I do not know if it is now easier to understand? |
Yes, problem is clear now. Sorry for late response. |
It's possible to insert a
|
Good morning, could you help me with this doubt? |
I will try to provide solution for this problem this month. |
thank you! |
What is the status of this? I am interested in this too. If possible to make sure that like non-nested grids that gridster nested grids can be rendered dynamically/programatically using object, that would significantly increase utility and futureproof. |
I'm currently working on that. Since this is not trivial problem it takes time to implement. |
I have the same problem that @rodrianderson reported |
@swiety85 can I help you from something?
For fire this event, just resize a component in the demo. |
@richardlnnr Sorry, but I can't reproduce this bug. Can you provide more details how to reproduce it? |
Yes, sure. Current master branch does not support dragging with nested gridsters. |
Exactly, this is one of the issue I have to fix. 😊 |
Can I help you to fix this things? :-) |
Problem seams to be hard to fix but fill free to give it a try. I will try to focus on this problem this week. I will let you know as soon as I will have any progress. |
The problem you found is already fixed. It's pushed. There is still some problem with dragging the item prototype after couple time moving out and over gridster area - especially when you drag to the very bottom of the window. After the drop, collision detection is not working with some items, similar to your example above. |
It seems that it works now. Can you pull changes on 123-Gridster-inside-gridster branch and check if it's working fine for you now? Thanx! |
I fixed these issues. Please give it the next try. I also fixed some issues with resizing - have a look at it as well. |
Good morning. |
Thx for the compliments. :) |
I have two questions :-) It's possible to prevent an child gridster to interact with an specific gridsterItemPrototype? It's possible to drag an element into main gridster to child gridster? And the opposite also. |
I have no clue why your gridster area is not visible. I didn't change anything in CSS. I can't reproduce it in any browser. Did you change anything in styles or ViewEncapsulation? |
When I launch the demo in Google Chrome and Edge, and the gridster area is on the right (No CSS change) About two questions, I'll create issues to make this features :-) Could I open the two issues? |
I have seen a bug, but I don't know exactly how to reproduce it. |
Please also create two issues for these two question you have. Thanx! |
65.0.3325.181 (Oficial Version) 64 bits. |
Thanks @swiety85 |
How do you actually use the gridster inside of another? I did what seemed intuitive but when dragging a prototype it adds a new item to both parent and child and throws a bunch of errors. Is there somewhere I can look to see an example of some sort of documentation of this? |
It's possible to insert a
<gridster>
inside a<gridster-item>
element?Something like:
<gridster> <!-- outter -->
<gridster-item> <!-- item from outter -->
<gridster> <!-- inner -->
<gridster-item> <!-- item from inner gridster -->
</gridster-item>
</gridster>
</gridster-item>
</gridster>
sry for the confusion :x
The text was updated successfully, but these errors were encountered: