3 ms·
I'm sorry I wasn't quite happy myself how I worded it. "operating heaving machinery" I mean that as; While driving the car you should also use this smaller, di
by Already__Taken 13y ago
I'm sorry I wasn't quite happy myself how I worded it.
"operating heaving machinery" I mean that as; While driving the car you should also use this smaller, difficult to read and use interface.
I'm not going to defend it to the death, it's almost certainly not the best implementation in the world, nothing in software is. But a massive screen lets you make input so much bigger than they ever could be in hardware. You can't take up 17" just for the radio if it were real, you can on a screen. Or have a 17" 'Object in path' warning light.
I've had my car 5 years and can't operate the radio by touch. Or the fog light buttons on the far side of the dash.
- masklinn 13y ago> But a massive screen lets you make input so much bigger than they ever could be in hardware. Which does not actually matter. The problem is not the size of the control, it's 1. finding it, 2. distinguishing it from its brethren and 3. only activating it once 1 and 2 are unambiguously fulfilled. The core properties of a touchscreen, its usual advantages of being flexible and ever-changing, become drawbacks. And I think that's OK, use the right tool for the right job you know? There are situations where a touchscreen is not the right tool.