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
This is probably a low-priority issue but worth keeping in mind, especially for new feedbacks:
For boolean-valued feedbacks (which is perhaps all of them?) there's no need to provide options for on/off since Companion has a built-in "invert" logic button. So the corresponding on/off dropdown menus could be eliminated.
The text was updated successfully, but these errors were encountered:
agreed. What should the feebacks be called. "Change style of button depending on state of ...." , Thinking its easy to miss in feedback list if its called "Change style of button when ... is true" then probably many will look for the "false" feedback not realizing they should invert to "true" action
@fa1k3n , I think for the most part the names can be the same, or with words like "on" or "selected" appended.
Then the description just explains what it does: "Change button style when feature is on" or some such.
Partly related: many (?) of the feedbacks have descriptions copied from the action. These should be cleaned up as well.
This is probably a low-priority issue but worth keeping in mind, especially for new feedbacks:
For boolean-valued feedbacks (which is perhaps all of them?) there's no need to provide options for on/off since Companion has a built-in "invert" logic button. So the corresponding on/off dropdown menus could be eliminated.
The text was updated successfully, but these errors were encountered: