3 ms·
I do like key-driven soft menus (like the steering wheel controls commonly used for HUDs or gauge cluster menus), but they get a bit unwieldy with longer lists.
by kube-system 7y ago
I do like key-driven soft menus (like the steering wheel controls commonly used for HUDs or gauge cluster menus), but they get a bit unwieldy with longer lists. Some automakers (GM) address this by nesting all the options in a bunch of sub-menus, but I find this frustrating because I end up just having to search through a bunch of menus to find what I want.
Some automakers (Mazda, BMW) use a knob instead, which makes it a bit quicker to scroll through a longer list, but I have found myself overshooting and then having to back track which is sometimes annoying.
There's really pros and cons to whatever implementation is used. While I completely agree that any function that might be operated while driving needs to be able to be operable with hard controls, I also don't think it's a good idea to clutter those menus with a bunch of junk that you don't want or need while driving.
I think there's a good case to be made for 3 levels of controls:
* Things that must have dedicated hard keys: anything that must be adjusted rapidly for driver attentiveness, control, or comfort -- HVAC, audio levels and basic tuning, all lighting and vehicle controls.
* Things that must have hard keys, but can live in a shared menu: anything that a driver may want to adjust while driving, but is not essential for immediate use -- trip data, infotainment, non-critical gauge monitoring etc.
* Things that don't need hard keys and should not clutter any of the above interfaces: odd-ball configuration settings that a driver would not need to operate while driving -- key fob configuration, entry-exit preference configuration, software updates, integrations with external services, maintenance logs, etc.