I have some questions regarding with RapidSetupX that would require some clarification:
I would like to know whether the IO labels displayed in RapidSetupX correspond to the labels defined in labels.networkio , similar to RapidSetup:
In RapidSetup, the IO labels show up as defined in labels.networkio and are displayed in the Network IO view
However, the same labels do not appear in the IO tab of RapidSetupX or the IOs section for the Node (they are using the default labels of Input 0, Input 1 etc.)
If RapidSetupX does not use labels.networkio , what is the recommended way to rename or customize the IO labels in RapidSetupX?
Does RapidSetupX provide a refresh function similar to RapidSetup (View → Refresh) for updating the UI to check for any changes, or is the UI automatically refreshed?
Your help and clarification is much appreciated. Thank you!
Hello Gregory, and thanks for the RapidSetupX questions.
Unfortunately, RapidSetupX does not currently have the same kind of IO label customization as the original RapidSetup. However, we have plans to support custom IO labels within RapidSetupX in a future release, with additional resilience to changes in topology.
In general, the UI should be refreshed automatically via polling. If you are noticing stale values, disconnecting and reconnecting to your rapidserver (or restarting RapidSetupX entirely) may refresh some of the controller state. These are, however, not a perfect analogue to the RapidSetup refresh function, and can disrupt some client-side constructs (e.g., Recorders will lose traces and may behave unexpectedly).
Could you let us know what specifically appears to require a refresh? The solution may depend on what values it involves.