Monitor Program Variables about dat.gui HOT 5 CLOSED

Thanks a million for the feedback doob!

I think that'd be a good solution. But perhaps instead of having each controller responsible for instantiating its own interval that checks the value, we have a method like GUI.listen() that you call in your own loop that goes through and monitors for variable changes on EVERY controller?

Curious to hear your thoughts on this approach. It may be that your sketch doesn't have a loop, or that you don't want to waste resources checking every variable you've added to the GUI (but I'm not exactly sure how taxing that really is).

from dat.gui.

Well, the idea was that GUI would have an internal interval. By calling .listen() the controller then would be added to the list of controllers to be checked in that loop. I don't think listening to all the controllers would be a good approach.

Maybe .startListening() and .stopListening()?

from dat.gui.

Right. I'm for the idea of individual controllers getting "listened" and I think there's something really elegant about putting .listen() at the end of the add call -- my only concern is: how do we give developers control over how frequently those values they choose to listen to are monitored? That's the only reason I was sort of into the idea of a GUI.listen() function that belongs in a user's own interval.

from dat.gui.

Here you have a patch :)
https://github.com/mrdoob/gui-dat/commit/d770dbb0c20e41a3ab38605d46ceff5e69696461

from dat.gui.

merged: https://github.com/jonobr1/gui-dat/commit/f736507fd460001e7b160324f9bc33b00515d2b2

from dat.gui.