In my opinion, you should bind the UI things you want to change, to a tag. the radio button effects that tag. Thus the last thing selected will work as a default for that said property etc… onaction wont happen without action. so if it aint pressed it won’t work. or you could change the way it triggers.
I like the idea of using a tag but. Trying to visualize how this will work and . . . it seems I would need to have a separate tag for every PC? Otherwise, with a single tag, the moment two PCs access the same view the UI logic would break. The UI would reflect the radio button that was last clicked, even if it was clicked on another PC if that makes sense.
Perhaps the ‘tag suggestion’ is to actually have a separate tag for every PC? Does this sound right?
It’s all dynamic, the UI is updated based on a (radio button) selected by the user. The radio buttons allow the user to select which record (record from database) to populate the UI with