-
-
Notifications
You must be signed in to change notification settings - Fork 142
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
A way to derive dragging active state #94
Comments
What’s your motivation for switching away from the library you’re currently using? |
To be clear, what I referred to as a 'library' is a set of class-based, non-typescript components that were originally ripped from an actual library and commited (after making some unspecified adjustments to meet the requirements) into the codebase I'm currently contributing to. I'm looking to replace it as it's a general mess and a nightmare to maintain - but so far, out of all the libraries I've tried only this one seems to tick all the boxes - except just this one thing |
I think Note that I don't think it makes senes to try to fire that event for Window Splitter events (resizing by keyboard) because there's no explicit stop for those, nor for imperative resize methods (by React refs) because those are generally discrete– only for resizes done by pointer. |
Available in v0.0.37 |
My specific use case requires me to disable certain app features and hide a few elements while the user is dragging a panel handle to save up on performance, so I need to be able to somehow derive this dragging active state using the library API.
In the library I was going to migrate from I could just pass callbacks that were called whenever the user started or stopped dragging the handles (something like
onResizeStart
/onResizeEnd
).The text was updated successfully, but these errors were encountered: