I spent some time messing about with the gauges app… learned a lot about how webCoRE works in the process and found some limitations to what I was trying to do. To configure this, just fill out the first six variables and the piston will (sometimes slowly) take care of the rest.
- Any tile clicked on will toggle its light on and off
- Rather than redrawing all gauges on an event, I just drew the affected gauge and updated the specific line item in the Piston State. This may improve performance a small amount, but makes the whole thing vulnerable to only catching one out of a group of lights turning on or off at the same time. I ran the IF statement as asynchronous to see if that would allow concurrent instances, but the result was the same.
- Created a “hide state” and “hide gauges” button that can be enabled/disabled with boolean variables
After some work I figured out the whole “clearing tiles” thing… gets especially messy when you decrease the number of tiles you have displayed by your piston.
Here’s the big, ugly mess if someone wants to take the time to figure out how to get around the groups of lights turning on, or see how the individual gauges and variables were updated. I’ll post a cleaner one in a bit that gets back to updating all gauges at each event, but includes the ‘hide’ options and light toggle for tiles when clicked.