toywylie
commented
2 years ago Basically the decision needs to be: Treat the Relay as a separate entity, or treat it as part of the collar proper. All other decisions will follow from that.
Open SilkieSabra opened 2 years ago
toywylie
commented
2 years ago Basically the decision needs to be: Treat the Relay as a separate entity, or treat it as part of the collar proper. All other decisions will follow from that.
mistressohm
commented
2 years ago What are the benefits of either of the two approaches?
What are the issues/pitfalls with either approach?
On Sun, Mar 27, 2022 at 11:32 AM Toy Wylie @.***> wrote:
Basically the decision needs to be: Treat the Relay as a separate entity, or treat it as part of the collar proper. All other decisions will follow from that.
— Reply to this email directly, view it on GitHub https://github.com/OpenCollarTeam/OpenCollar/issues/760#issuecomment-1079965777, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALSHY5EAMXKKQ6IDJQODJL3VCCLUDANCNFSM5RZAAYVA . You are receiving this because you are subscribed to this thread.Message ID: @.***>
There are some inconsistencies to how the collar menus access the relay.
The collar safeword will release restrictions applied through the relay.
But, turning off RLV in the collar does not also turn off the relay.
Yet the relay is in the RLV menu, and when RLV is turned off in the collar, the relay button is no longer accessible to menu access, even though the relay may be still on. This leads to confusion and unnecessary user errors.
Suggestions? Option 1) Automatically turn off the relay when collar RLV is turned off. This option is closest to a "bug fix." I can't think of many instances when someone who turns off collar RLV would not want the relay off also.
Option 2) Move the relay to the apps menu? This would force a lot of users to relearn how to find the relay. Also the apps menu is getting crowded.
Option 3) Rewrite the RLV menu so when RLV is turned off the Relay button is still available there.
Other ideas?