Closed jamesb93 closed 4 years ago
Thanks. fl.getparam~ may not exist for much longer, as it is very hard to support in all possible scenarios correctly, but useful to know it isn't functioning as expected in case it stays.
OK - this was a simple error fixed by e3b9ff10e779faa4f7291a6b10cbe35071f931ce.
However, I'm now going to remove the object, as it doesn't solve any real problem (you can always derive values from elsewhere, and the work required to maintain correct functionality under all conditions is too high). Something like this may return at a later stage, but for now it is gone.
As far as I can tell, "only the first trigger input" should make fl.getparam~ extract the parameter information from the connected object. In this small patch, it seems fl.getparam~ constantly filres when it is allegedly triggered by fl.once~ but is connected to fl.interval~