Launcher - Unclear state of buttons
-
@airtex2019 Ah damn. I forgot
-
@Micro_440th probably it has never come up ā¦ doesnāt usually affect me with display screens or traffic lights etc.
but as a UI developer Iāve been told I sometimes pick ugly or mismatching color combinationsā¦ I use this as my excuse.
I have a friend who is fully, truly R/G colorblind ā¦ difficulty sometimes with red vs green arrows on traffic lights. I always think of him, whenever I see UI using red-vs-green to convey information (banking and stock apps seem bad, in this regard)
-
@airtex2019 said in Launcher - Unclear state of buttons:
@Micro_440th probably it has never come up ā¦ doesnāt usually affect me with display screens or traffic lights etc.
but as a UI developer Iāve been told I sometimes pick ugly or mismatching color combinationsā¦ I use this as my excuse.
I have a friend who is fully, truly R/G colorblind ā¦ difficulty sometimes with red vs green arrows on traffic lights. I always think of him, whenever I see UI using red-vs-green to convey information (banking and stock apps seem bad, in this regard)
So if you have time, maybe a checkbox could solve the color question. But of course, Chihiro and you are AL bosses
-
Also, the Virtual Reality labelling is completely unclear. It should read āDisabledā not āDisableā, and āEnabledā not āEnableā.
āDisabledā and āEnabledā are the correct spellings to indicate a CURRENT STATE.
āDisableā and āEnableā are the correct spellings to indicate a DESIRED STATE that needs to be clicked or checked.
But it is set up backwards in this user interface.
Iāve posted this months ago, but I see itās not been addressed with U3. But I notice that yāall DID make the upper right windows controls more visible as I posted about, and I appreciate it.
-
-
@Micro_440th - Also, since weāre on this āCommand Lineā buttons topic
In the User Manual, Page 13, in the middle of the page, you state
Command Line let you enable or disable certain Launcher.exe functions (all command line parameters are explained on the page 22, chapter 2.2.9).
However, there is no chapter 2.2.9, and there is no explanation for them on page 22. On Page 15, there is 2.2.8, and there are command line options listed, but you donāt explain what the āACMIā, āDebugā, āEyeFlyā, āWindowā, or āNoMovieā buttons mean as you promised in the quote on Page 13.
-
This seems the logical solution for binary switches
-
Come to mention it, I donāt think the BMS cmd line parameters are documented anywhere at allā¦
-
They are
-
@SoBad please post your findings in the docs bugtracker thread.
-
@Micro_440th ok now I do see User Manual sec. 2.2.8 ā¦ I was ctrl+F searching for āmonoā and didnāt find it.
Iāll submit some additional content for reviewā¦ after double-checking relevant bits of the source.
-
@airtex2019 said in Launcher - Unclear state of buttons:
@Micro_440th ok now I do see User Manual sec. 2.2.8 ā¦ I was ctrl+F searching for āmonoā and didnāt find it.
Iāll submit some additional content for reviewā¦ after double-checking relevant bits of the source.
Fuck you are right. Somehow I deleted mono. Will fix it in U4.
-
@CriticalMass even more confusing if greyscale without any reference which position is on/off. Even labeling these things confuses people a lot.
Speaking of conventions mentioned here: they heavily depend on what OS you are used to. And, as time goes by, they change. In addition to that, buttons have more states than pressed/depressedā¦.focused, hovered, enabled, disabled, dragged (no issue here)ā¦this makes it very hard to get a color scheme readable and understood by everyone. Flat and mimic 3d design decisions made by OS vendors adds a lot of extra confusion to UI elements.
Thatās why I would - UI/UX wise - vote for a viper panel mimic with chicken head knobs and / or toggle switches and proper labeling. Will try to make a mock-up later on. Would not only be eye-candy but crystal clear
-
Just a mockup on top of the Alternative Launcher 4.35 on github. You get the idea.
-
@r00t Iām with you except ā¦ the ccw direction to go from āoffā to āonā ā¦ weāre back where we started
-
@airtex2019
rgrā¦my fault
-
Iām not really a fan of skeuomorph design. It can get very old very quickly.
-
I had no problem understanding white is on, grey off. Pretty simple to me. Donāt understand how this is such a big deal.
-
@CriticalMass said in Launcher - Unclear state of buttons:
Iām not really a fan of skeuomorph design. It can get very old very quickly.
Not ashamed to say I had to look that one up.
-
@Icarus I just wanted to point out that a slider without a reference isnāt much more intuitive to me than a button without a reference.
On/Off references could be applied in flat designs also, by labeling the slider besides coloring them or having a sub/sup/hover hint text on a button. But as you said, one gets used to it and doesnāt think about it after the third launch. Admitted, my first thoughts at the first launch a few weeks ago where like OP wrote: āwhat is the state of these buttons?ā. My second thought was: āwhat do they do? Why donāt they have a hover text with a summary of their intentionsā.
@CriticalMass Not a fan of designs like that either. Just tossing around ideas.