And then on top of that people want AA/CarPlay which is designed around touch inputs first, so you're going to have that screen be touch anyways.
None of that should really be changed by the driver when the car is in motion, and you'd have to manage the deep navigation of a bunch of button presses on a screen anyways so arguing you'd be less distracted is a moot point.
Sadly all other GPS navigators we used to use has gone downhill to the state of unusable so this is what we turned out using all vacation.
[F1] FOO
[F3] BAR
[F5] BAZ
[F7] BAL
Small enough to instantly absorb in the wetware. Depending on how frequent the choice was used one would push options further down the sub menus. Say, something like this for HN (I made a tree, they would normally be separate pages) [F1] Index
[F3] Threads
[F5] Comments
[F7] More [F1] Ask
[F3] Show
[F5] Jobs
[F7] More [F1] Profile [F1] View
[F3] Submissions
[F5] Logout
[F3] New
[F5] Past
[F7] Submit
After you've submitted 2-3 things you just know you have to bash [F7] three times. To view jobs you hammer the bottom button then the one above. The hands will learn how to use the menus really quickly. I was often surprised that my hands knew how to take me places before really reading anything. Every time one used such menu it went slightly faster and it kept going faster. Pointing a mouse or using a touch screen is really slow. Could say it gets slower every time by comparison.(The use of odd numbers wasn't even optimal)
On this feature (which itself can be enabled/disabled), sometimes you can choose how far back it'll move the seat automatically for you.
Its this setting that you're suggesting you're going to mess with enough to have decent muscle memory to change without looking. That you'd want as a top-level feature setting option, practically a dedicated button to change it.
The video below shows what I'm talking about. Note in a lot of cars it's just a basic toggle. Sometimes you can set how far back you want the seat to go, if you want the steering wheel to move, how far you want the steering wheel to move, etc.
If I was making such an interface, that would be a dial or knob instead of buttons.
I've had far more rotary encoders fail than I've had capacitive screens fail, so even an argument of higher reliability is pretty moot. Most damage that would break the capacitive touch is going to damage the rest of the screen anyways.
Finally, if it's so I can change those settings while wearing gloves, wow I'm going to increase the complexity of the car and take up more space so I can change the settings on the secondary keys without taking off my gloves when it's really cold outside someday. So much stuff just so I can do that thing I rarely do anyways slightly easier for a few days of the year, assuming I'm changing those settings while also getting in and out of the car a lot so I wouldn't want to take off my gloves for a minute.
Just put the settings behind a touchscreen. It's fine.
That doesn't sound like a dial/knob. You'd give it a single big twist or scroll to get the cursor around the right spot first. Same as old-fashioned radios.
At least with an old-fashioned radio knob you got the feedback of if you were tuning into the station by hearing it. But moving a selector on a screen?
It's like you're arguing for the MacBook Wheel, as if a knob is the most optimal way to input arbitrary choices on a computer.