I'm gonna go ahead and as a relevant question as well - is there a way to get the joystick values to the dashboard without travelling to the robot and back? Reasons being the obvious delay introduced, as well as the waste of resources (however tiny). We could have used it last year, and this year I'm also thinking of a control system utilizing it. In both cases, the delay of going through the robot makes it useless.
DominickC - if you've found the correct property node input to control the active tab, and want to use a joystick button to control it, then what you need to do is, first, make sure you have the joystick value in the cluster you're sending to the dashboard from the cRIO. Then, you can simply use this value in the dashboard project and connect it to the property node to switch the tab.
