"In every study that considered the question"(unsung.aresluna.org) |
"In every study that considered the question"(unsung.aresluna.org) |
While it doesn't negate the iconography discussion throughout the rest of the article, the AUTO option is the intended default, because it turns on low beams in every case where they're needed, including daylight rain driving, which is based on the use of windshield wipers. I'm always a bit baffled at the modern cars driving around without their lights on. The car does it for you these days.
The ability to select low beams vs daylight running lights (DRLs) is mostly for convenience for one-off odd circumstances where you would want to override AUTO for whatever reason.
Then, when I leave, I forget to turn the lights back to AUTO. Now I have no lights at all except for the front DRLs. (Even then, though, the low beams still come on automatically when the wipers are turned on for more than a couple of cycles.)
Really, the OFF position should work only when the car is parked. Otherwise, it should be equivalent to AUTO.
Icons are still the same as they were 25 years ago AFAICT.
The real problem is that they get daytime running lights, instead of lights off or lights on.
Daytime running lights give them dim headlights that have headlight patterns so the driver might think his/her lights are on, but to people behind the tail lights are completely dark.
> “parking,” which activates only front lights, at half brightness, and (for some reason) leaves the tail lights off.
I've also just double checked the manual for my car to be sure I'm not talking out of my ass here: the symbol he calls "parking" activates the tail lights. From the manual:
> “[double headlights, one left one right symbol]” position:
> Instrument panel illumination, parking lights, front side marker lights, rear side marker lights, tail lights and license plate lights are on.
(My manual does not ascribe a name to it.)
Now, I suppose this could be an unexpected thing that differs between cars, but it also shouldn't really matter that much. The intro example is in the rain; you should be using the symbol he calls "park" in the rain, you should be using the "low beams" setting, and then your tail lights are definitely on. Or … just let "Auto" handle it?
(I've always called this symbol "daytime running lights". Wikipedia says that's a different symbol (a single headlight with stippled lines emitting from it), one I've definitely never seen before & isn't in TFA; Wikipedia claims it to be the ISO symbol, however, I've found the relevant ISO standard¹, but it seems to lack the symbol Wikipedia calls "daytime running lights". The symbol I call DRL is called "position" or "side" lights, and the term DRL is not used by ISO AFAICT, despite what Wikipedia claims. What a mess.)
(from TFA:)
> Many cars have an AUTO option now, but would you trust it to choose the right thing?
… yes? Absolutely yes. The car can just do the right thing for me, without me having to remember. Sensing ambient light is not complicated.
> pull on the stalk for high beams (another mode), or rotate the stalk left or right for turn signals.
There is absolutely no way whatever car this is a photograph of is rotating the stalk for turn signals. Turn signals are pull up or down, universally.
¹ISO-2575:2021, though technically a draft since ISO standards are not open. But this symbol has been around since forever, so unless it's changed recently…
Parking light does not make much sense.
At least they had the sense not to try to invent an icon for 'AUTO', to give credit where it's due. English subtitles or (better) dashboard 'tooltips' would have been a good idea, and tooltips are in fact used in quite a few other contexts.
Can anyone tell me what they’re supposed to be used for? Headlights are better in every scenario, the existence of parking lights only seems to force me to flash my brights at idiots that drive with parking lights at night. Removing the option would eliminate that.
"Driving" or "Parking" lights make no sense conceptually. Over this side of the pond, we just call these symbols by what they actually represent - tail lights, short lights, anti-fog lights, etc.
Which I guess kind of is a problem happening in UX right now. It's my firm belief that the buttons for operating equipment should be labeled by what the button does, not when to use it. In domain of illumination, "headlights" and "tail lights" are real concepts; "parking" and "driving" are category errors.
You're pulled into a parking spot and you want you're waiting with corner markers on for safety and illumination, bit you don't need or want your headlights blasting.
It'd be best to simply remind the driver that the lights are manually turned off with a subtle notification in the display, and leave it up to the driver to decide whether they should remain off.