georgealways

Thanks! So I agree, that would be convenient. At one point I thought about making it so that `onChange` and `onFinishChange` would be fired on click (given they don't do...

Hey, do you mind describing the use-case, and how you would want onBeforeChange to work?

Got it, thanks for the details! In the example it seems like you're primarily using this onBeforeChange method to constrain values (clamping or limiting decimals), right? I'll have a think...

Makes sense. It feels like the constraining you're doing in `onBeforeChange` can be done with the library's built in functionality. I'm curious why you're not just using `step: .1` instead...

Got it—basically you want "dynamic" constraints. I'll have to think more on that. Thanks for the kind words.

Yes, that was an intentional API change, `gui.remove` is replaced by `controller.destroy()`. It didn't really make sense to me that you needed a reference to the parent GUI to do...

Sorry it broke things for you! I agree, some kind of "mostly" language could go in the "drop-in" sentence—I was just trying to keep it short. I think the migrating...

Sure, let's put it back as a synonym for `destroy()`, there's valid arguments for both and it helps with compatibility. I don't think `gui.add` should be overloaded to accommodate `gui.add(...

Hi there—yes, totally reasonable. Ideally we could make `disable()` behave how you describe, without having to introduce a new method. Right now, a controller is "disabled" by applying `pointer-events: none`...

I had imagined that this behavior would only apply to text inputs (string or number controllers), so that you could copy and paste out a value. What would be the...