2 ms·
> Except for the keybinds you now have to look at a separate screen to use, of course. The Touch Bar is always in your vision: http://i.imgur.com/En02SKA.jpg
by Razengan 10y ago
> Except for the keybinds you now have to look at a separate screen to use, of course.
The Touch Bar is always in your vision:
http://i.imgur.com/En02SKA.jpg http://i.imgur.com/En02SKA.jpg
http://i.imgur.com/DIN2fCE.jpg http://i.imgur.com/DIN2fCE.jpg
In any case, how is looking at something such an arduous action as to be a con, but searching and memorizing what each FN does in each app, isn't?
> Use a modifier. That brings you up to 48 without counting Alt.
Even more shortcuts to look up somewhere (in-app help? keybind settings? online?) and mentally associate with each number (and its modifier), instead of just seeing your available options for the current context on the Touch Bar.
In a complex app like an IDE, each FN could mean 10 different things depending on the context. How is that good, or sane?
We have toolbars in addition to menus for the same reasons.
> Different numbers remain "fixed" for different functions in different operating systems (e.g. F1 for Help, Alt+F4 for Quit.)
> That's a con?
It reduces the number of effectively available keys (minus shortcuts) to less than 12, and it differs across operating systems.
As for tactile feedback, we might as well go back in time to 2007 and rail against the introduction of touchscreen phones.
> Feedback on touch (to see where exactly is the finger positioned on the key and relative to the previous keyboard position) is more important than feedback on activation.
We're getting there with more precise and shorter vibrations. Compare the "Taptic Engine" of an iPhone 6S and an iPhone 7.