georgealways

Hi there, no plans for such a method currently. For now, you can use a workaround like this: https://github.com/georgealways/lil-gui/issues/86#issuecomment-1426788541 Leaving this open in case others would like to express the...

Got it—so you're expecting setValue to convert that parameter to a true/false value before actually assigning the property? Curious which 3D library you're using. And after you do this, the...

Thanks—let me think on this a little. None of the other controllers do any validating/converting. Right now I like how `setValue` is "what you set is what you get", but...

Hi there, looks like there's two things going on: > It also remove useless updates caused by the click event and only call onChange if the value really changed. The...

- A fix for stepped number controllers generating extraneous onChange events is on the list for the next release. - I'd like some more input from others on how prevValue...

Hi there, thanks for this. I think it makes sense to do this for Controller.name, GUI.title, and the creation of options in OptionController. I'm not sure we need to change...

Hi @jynxio, this was implemented in the latest release. Thanks for bringing it to my attention.

Hi there, I'll consider it! For now I would suggest adding your own button elements to `controller.$widget` that call `controller.setValue`.