Meh, just ctlr+tab bro. shift+ctrl+tab to go reverse.
These use cases are not for pro users, they're for moms.
When you've got 30+ tabs it's not efficient to tab through them all.
Meh, just ctlr+tab bro. shift+ctrl+tab to go reverse.
These use cases are not for pro users, they're for moms.
and i'ts easier to single out one and press it on that tiiiiny little screen? pleaseWhen you've got 30+ tabs it's not efficient to tab through them all.
When you've got 30+ tabs it's not efficient to tab through them all.
and i'ts easier to single out one and press it on that tiiiiny little screen? please
Surprised nobody has linked to this yet. It's a touchbar app that lets you try it without Xcode. https://github.com/bikkelbroeders/TouchBarDemoApp
The ribbon was a clutter because it takes up a significant space on the screen. If I use Office, I tend to hide the bar to get more screen space.Ribbon bar or touch bar. Both cluttered useless interfaces in my opinion. Everyone of us can touch-type right? You learn it in school at least last time I checked. I still see SOME use to a broader touchbar attached as a dongle, a peripheral, with slider controls and configurable input for your favourite, most used apps. No need to annoy your whole bunch of customers with that hardware only a small fraction of them will use, if even.
Adding something that removes your focus from the screen and makes you look down on the keyboard is just backwards.
All opinions only of course.
Bringing in something new like that requires money.Would seem others also looked at the concept of a Touch Bar some time ago, equally they have not brought anything to market if ever at all...
Q-6
Bringing in something new like that requires money. Considering most PC OEMs are operating at razor thin margin, they don't have time to try things like this. They would rather keep making the same thing they have been making since it involves almost no extra cost.
Just look at the Surface Pro clones. It takes Microsoft to create that new form factor, then the OEMs just copied it, since they don't have capacity to come up with it themselves. Same thing on Android phones. Google has to make the Nexus One, the first super phone, for the OEMs to move up from the G1 (literally all Android phones that time are just a variation of the G1 internals, nobody wants to use the faster snapdragon SoC until Google did it with the Nexus One).
Ditto for me. And besides, I haven't used the F keys as function keys in... well, I can't remember when. I use them for volume controls and maybe screen brightness, and that's about it (which means that eight of the twelve keys go unused... and oh yeah, there's an eject key, I forgot...).The new touch bar is so close to the screen, it's probably within your visual field anyway.
And I have never developed muscle memory for any F keys, personally
Does this mean Apple will release a standalone keyboard with the touchbar in the future?
Do you look at the keyboard on your iPhone when you type? I don't, muscle memory.
I'm not sure about the Touch bar. They probably should have made it an option, considering how much your paying. I can't believe they are so confident. Makes you wonder.
Link to that video? The one I found it says is privateJust had a look on the French review video that's knocking about and must say, I'm still underwhelmed here....hopefully get to check it out in person before xmas!
Link to that video? The one I found it says is private
It seems like they have deleted it. (Maybe Apple didnt allow it till it's oficially released at stores)
Now this is a good point, and I think it would come in future versions. This is the version 1, and I think Apple focused more on the security first for TouchID.My biggest question still is, why didn't Apple use the haptic engine for the touchbars? That way you can simulate a click and still integrate the same software features.
How should this work when the buttons are dynamic and not always on the same positions?
In my eyes, thats a permanent problem between hardware and software.
Exactly. They keys will change on every app, but they will allways be the same in that app. The videogames example is a perfect one. Even on normal programs, when you use Microsoft Word there are some shortcuts with keys, and when you use Premiere those same keys do something else. I don't see the problem, you just memorize what they do in each program.Buttons are probably on the same place as you set them. It is like how you game and for different games/characters, you have to press different places for different abilities - you get used to it (For game/character 1, ability 1 is on key Q, for another game, it can be Z). The location of Q and Z don't move, neither does the location of the area's of the touch bars.
If you have a set of binds for Photoshop, and another for say Pages, after a while, I guess you get used to it? Or maybe I am overly optimistic.