You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently if you load load Elastic from a file you are able to display and view values directly out of network tables. However this is not possible to do programmatically via the Shuffleboard api. Where it is required to publish a second duplicate record of the data to network tables to be viewable within the dashboard. This is specifically a problem when wanting to view vision data or values from a co-processor publishing to network tables directly. Where the only way to programmatically publish these would be to read the data from network tables and republish it to shuffleboard on the robot adding unneeded latency.
It would be nice to be able to just tell elastic to look at a particular network table entry/path by only publishing the string of the path itself vs needing to send a copy of the value.
The text was updated successfully, but these errors were encountered:
This can already be done, but It's not really documented anywhere. Elastic stores the NT topic as a property, so it can be manually set with the Shuffleboard API via the widget's properties. To do this when adding a widget, you would use the withProperties() method.
Here's an example:
Shuffleboard.getTab("Example Tab").add("Example Widget", 0.0) // 0.0 will never be displayed, so it doesn't really matter what you put for it
.withProperties(Map.of("topic", "Whatever/Topic/You/Want/To/Display"));
Currently if you load load Elastic from a file you are able to display and view values directly out of network tables. However this is not possible to do programmatically via the Shuffleboard api. Where it is required to publish a second duplicate record of the data to network tables to be viewable within the dashboard. This is specifically a problem when wanting to view vision data or values from a co-processor publishing to network tables directly. Where the only way to programmatically publish these would be to read the data from network tables and republish it to shuffleboard on the robot adding unneeded latency.
It would be nice to be able to just tell elastic to look at a particular network table entry/path by only publishing the string of the path itself vs needing to send a copy of the value.
The text was updated successfully, but these errors were encountered: