DSP Robotics Support

I can't be the only one tired of having to deal with ruby code blocks getting into bad states even when the code itself is correct. The persistence of values within the Ruby component causes all sorts of mucky stuff mid-development. There needs to be some easy way of resetting the state of the Ruby component and starting it up fresh. Is there a way to do this I don't know about or is this perhaps something we can petition the devs for? I know sometimes just clicking on the input nodes and then turning it off and on again is enough, but when your schematic just randomly stops working sometimes it can be hard to dig up some random Ruby block that blew a fuse on you.

In general I find managing the persistent values in Ruby to be a pain in the butt. Maybe I should get into the habit of switching it off as I'm editing the code, if that helps. But that can't help external forces causing errors on the inputs.

It also probably wouldn't hurt if there was some top-level Ruby error reporting put into the Flowstone interface, so if you have a block somewhere throwing an error it will actually show you there's an error without you having to go and dig up that specific code block and look at it to see it.

What do you mean by persistance values? Instance variables?

If Ruby code gets into bad state, there is an issue for sure. Even if you think your code is correct. You should share that code, when there's issues. 4 eyes or 6 or 8 or... see more than 2.

Also, you are free to set up a method that sets all your "persistent values" to nil or their start values. That is the equivalent of resetting. You just call that method whenever you need it. Normally though, this would never be needed.