Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: Colour blind mode #1

Open
pjf opened this issue May 19, 2014 · 5 comments
Open

Feature request: Colour blind mode #1

pjf opened this issue May 19, 2014 · 5 comments

Comments

@pjf
Copy link
Contributor

pjf commented May 19, 2014

SCANsat rocks so freakin' hard, thank you.

However, I happen to have colour blindness. All those times when indicator are blinking orange and green? Absolutely impossible for me to see.

Luckily, colour-blind friendly interfaces are pretty easy to design. Have a little "ideal altitude" light next to each scanner indicator, and light that up when we'd otherwise be seeing a "solid green". Bonus points if it flashes when we'd be in a "flashing orange" state

Alternatively, if we're talking about HSV colour spaces, then anything which varies the value (brightness) is colour-blind friendly. With the existing green/orange indicators, if the green was made brighter, and the orange made darker, then that would also work.

Many thanks again for a brilliant mod! I love your work!

~ pjf

@DMagic1
Copy link
Contributor

DMagic1 commented May 20, 2014

The blinking lights thing and the ideal altitude setting as it currently stands both aren't very good. A blinking indicator light is one option, at least as a stopgap measure, that shouldn't be too hard to implement.

@technogeeky
Copy link
Member

It's interesting that an attempt to account for color blindness was undertaken with the Big Map, but evidently not with these icons.

@DMagic1
Copy link
Contributor

DMagic1 commented May 20, 2014

The color scheme in general is designed to be distinguishable for colorblind and non-colorblind people. There is a pretty interesting link in SCANui discussing the ideal color combinations to use: http://jfly.iam.u-tokyo.ac.jp/color/

But you're right these icons switch between one of the barrier free colors, and one of the XKCD colors (pukegreen). Maybe just replacing that with the bluishgreen or the blue color would be enough.

@technogeeky technogeeky added this to the v7.0rc3 milestone Jun 12, 2014
DMagic1 added a commit that referenced this issue Dec 13, 2014
@DMagic1 DMagic1 mentioned this issue Dec 13, 2014
DMagic1 added a commit that referenced this issue Jan 23, 2015
This should work fine. The .csproj file only gets updated from one of the computers I work from, so it's frequently out of data, and a lot has been moved around.
@DMagic1
Copy link
Contributor

DMagic1 commented Apr 15, 2015

I'm wondering if this color combination is any better for the flashing sensor indicators.

@pjf
Copy link
Contributor Author

pjf commented May 19, 2015

I'm wondering if this color combination is any better for the flashing sensor indicators.

I can't tell if an indicator is orange or green. Apparently in the image below it's flashing, but I can only just tell that BIO and ANOM are flashing if I spend 30 seconds staring at it with my brightness turned up to full. I honestly can't tell you what colour the probe is, or if "Scanner 6" changes colour at all:

As for v11rc3:

I know that 'HI' and 'Tester MK I' have colours, but again I can't tell you if they're orange or green; they certainly don't appear to be flashing, nor can I tell a difference from the old indicators. That's the thing about being colour-blind, figuring out colours (hue) is hard. :)

Any sort of visual mark-up that doesn't use colour would be excellent. A 'tick' that appears when we're at an ideal altitude, an up or down arrow if we're too low or too high, or even just a '*' to indicate that a part isn't ideal would all work great. (Although I understand such things may be tricky, as they'd involve potentially moving around UI elements.)

Many, many thanks again!

~ pjf

mwerle pushed a commit to mwerle/SCANsat that referenced this issue Nov 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants