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
Not a problem with the design but an improvement... I can't seem to find how to do this.**
Where you add buttons, there should be a way to group them so that when one is turned on the other goes off... but only within that group.
The way it is now, if I have heat buttons, 1-2-3-4-5 and fan buttons 1-2-3-4-5.... I turn on heat 3 (heat 3 is now highlighted), then I turn on Fan 4 (Fan 4 is now highlighted and Heat 3 goes off). I would like to make a Fan group and a Heat group so if I turn on Heat 3 - it only changes if I hit another Heat button... So both Heat 3 stays ON and Fan 4 stays on. This way you can tell at a glance your last heat and fan setting.
In this image there are 5 groups
The text was updated successfully, but these errors were encountered:
Currently, Artisan only highlights the last button pressed (if the corresponding feature is activated). Your suggestion is well-understood and makes sense. Implementation of your suggestion is non-trivial and might thus never get realized. Not even sure how a simple UI could look like to define such groups. We keep this as feature request.
Not a problem with the design but an improvement... I can't seem to find how to do this.**
Where you add buttons, there should be a way to group them so that when one is turned on the other goes off... but only within that group.
The way it is now, if I have heat buttons, 1-2-3-4-5 and fan buttons 1-2-3-4-5.... I turn on heat 3 (heat 3 is now highlighted), then I turn on Fan 4 (Fan 4 is now highlighted and Heat 3 goes off). I would like to make a Fan group and a Heat group so if I turn on Heat 3 - it only changes if I hit another Heat button... So both Heat 3 stays ON and Fan 4 stays on. This way you can tell at a glance your last heat and fan setting.
In this image there are 5 groups
The text was updated successfully, but these errors were encountered: