Launcher - Unclear state of buttons
-
The command line buttons in the Launcher don’t convey their state properly.
Upon a fresh install, a few are pressed and a few aren’t. It is difficult to figure out whether they are on or off. Does the grey represent that they’re toggled, i.e. on? Does the white, them being brighter, mean that they’re on?
Perhaps something like a check-mark with text above would be a saner choice from a user experience point of view.
-
@justonce01 agreed!
-
Like a light bulb, white = On, dark = off
-
RTFM (User Manual has all info, chapter 2.2.8)
@justonce01 said in Launcher - Unclear state of buttons:
The command line buttons in the Launcher don’t convey their state properly.
Upon a fresh install, a few are pressed and a few aren’t. It is difficult to figure out whether they are on or off. Does the grey represent that they’re toggled, i.e. on? Does the white, them being brighter, mean that they’re on?
Perhaps something like a check-mark with text above would be a saner choice from a user experience point of view.
-
@Badger
The general computer button UI convention seems to be that depressed is the “on” state. Depressed buttons are usually darker, to visually represent them being pushed in.
I mean, the fact that we are discussing this kinda speaks for the issue itself, doesn’t it.@Micro_440th
Thanks, that does indeed answer the question.I still stand by the point that one shouldn’t really need to consult a technical manual to figure out a UI button’s state.
-
-
@justonce01 maybe a little checkmark icon along with the text label… or a more prominent border for the ‘enabled’ state buttons?
I never had any cognitive dissonance re those 5 buttons … but I do empathize in general… a lot of apps have ambiguous UX for toggle-buttons, and it’s super annoying.
-
@airtex2019 for me, its not clear the state of those buttons.
-
@justonce01 okay understood.
@airtex2019 maybe green/red colors or Check box could be an idea?
-
@Micro_440th said in Launcher - Unclear state of buttons:
maybe green/red colors
ok now you’re just trolling… (I am mildy red/green colorblind
-
@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.