4 ms·
The problem with putting keys on the keyboard that radically change depending on context is that you cannot use them from memory just like the other keys. Of co
by dep_b 7y ago
The problem with putting keys on the keyboard that radically change depending on context is that you cannot use them from memory just like the other keys. Of course CMD+C doesn't copy when you didn't select anything nor will CMD+W close a tab in a tabless application but when I want to lower the volume on a TouchBarless Mac it's always the same key in the same place while it might exist or not exist depending on the application I'm in.
Perhaps in Final Cut Pro I'm not able to lower the volume anymore because there's a video scrubber in the place of that key instead. So I cannot depend on that key anymore.
- mistersquid 7y ago> The problem with putting keys on the keyboard that radically change depending on context is that you cannot use them from memory just like the other keys. Yes, this is one of the tradeoffs the Touch Bar makes in order to have a dynamically changing touch interface. I wouldn't really call it a "problem", though many do in light of the Touch Bar taking the space of function keys. I do miss the function keys, but I also sort of like the Touch Bar in certain circumstances. Anecdotally, I was pretty fed up with my 2017 MacBook Pro (butterfly keyboard) and so made the change to the 16-inch. Apparently, I've gotten so used to the soft "Esc" key that I frequently rest my finger on the 16-inch's physical "Esc" key for a few monents before realizing I actually have to push down to activate it.
- dep_b 7y agoThe touchbar should been an extension at bottom of the screen where you would always be able to see it’s state, not of the keyboard.