You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes the window/container got resized, or the element's size changes, and its height is larger than its bounds.
If I drag it at this moment, it will got shrink. But if I don't drag it, it will stay unresized, which is bad.
I want to have an exposed function that I can call to manually invoke the recalculation of the element's position on the screen, no need to drag it.
Or, if this is not elegant, I think it's possible to listen to resize events of the element's container, and watch the element's size?
Or, we can do this outside neodrag, and emit a custom event when we need this. Can there be an option to listen to a custom event?
I think all these 3 approach looks good to me. I really need this and believe this is a common use case. Thank you for all your work!
The text was updated successfully, but these errors were encountered:
CNSeniorious000
changed the title
Feature requests for exposing an API for manually invoke recalculation of the position
Feature requests for invoking position recalculation manually
Jun 18, 2024
Sometimes the window/container got resized, or the element's size changes, and its height is larger than its
bounds
.If I drag it at this moment, it will got shrink. But if I don't drag it, it will stay unresized, which is bad.
I want to have an exposed function that I can call to manually invoke the recalculation of the element's position on the screen, no need to drag it.
Or, if this is not elegant, I think it's possible to listen to
resize
events of the element's container, and watch the element's size?Or, we can do this outside neodrag, and emit a custom event when we need this. Can there be an option to listen to a custom event?
I think all these 3 approach looks good to me. I really need this and believe this is a common use case. Thank you for all your work!
The text was updated successfully, but these errors were encountered: