Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[In-app feedback] #626

Closed
alt-tab-macos-bot opened this issue Sep 28, 2020 · 2 comments
Closed

[In-app feedback] #626

alt-tab-macos-bot opened this issue Sep 28, 2020 · 2 comments
Labels
duplicate This issue or pull request already exists support/question The author was looking for help, or didn't understand something and though it was a bug

Comments

@alt-tab-macos-bot
Copy link

This issue was opened by a bot after a user submitted feedback through the in-app form.

Message:

AltTab doesn't bring the power of Windows alt-tab to macOS (uses unfamiliar key combinations by default)

So here's how alt-tab works on Windows PCs:

  1. pressing whichever-key-happens-to-be-next-to-the-space-bar + tab opens the window list / switches to the next window
  2. pressing whichever-key-happens-to-be-next-to-the-space-bar + shift + tab opens the window list / switches to the previous window

That's it, for better or for worse. That's how it has always been, so that's what people expect if you promise "Windows alt-tab" behavior. So basically the defaults should be Cmd-tab and Cmd-shift-tab.

I'm pretty sure Windows developers originally picked whichever button was next to the space bar on a PC keyboard, and that key just happened to have the word "Alt" written on it. If that particular key had had some other word written on it, and "Alt" was somewhere else, surely they would still have picked the key next to the space bar, and not Alt for Alt's sake.

Apple also picked the button next to the space bar on Apple keyboards (Command) for their own "alt-tab-like" feature. (And both macOS and Windows use that-key + shift + tab for previous.)

The problem is that in AltTab.app, the default key is currently Option for some reason, and the user has to manually change it to Cmd (the key next to the space bar on normal Apple keyboards) to make it work like Windows alt-tab. I think Option might have been selected because in the past, in some languages, the Option key used to have the word "Alt" written on it, but that's not a good reason, and also I dont't think it's even possible to buy a new Apple product with the word "Alt" written anywhere anymore.

So what I'm trying to say is that the "Alt" part in "Windows alt-tab" or AltTab should not be taken literally, more like a metaphor for the-key-next-to-spacebar-and-therefore-the-easiest-one-to-press-with-the-left-thumb :)

Also, whichever-key-is-next-to-spacebar + shift + tab doesn't work properly by default. It's mapped to Option + shift, without the tab (!). This confusing behavior makes a first-time user's default AltTab experience feel even less like the original Windows alt-tab experience: basically nothing works quite like in Windows alt-tab by default, and you only get one chance to make a first impression.

TLDR: If you want AltTab to fulfil the promise "AltTab brings the power of Windows alt-tab to macOS" / "Windows alt-tab on macOS", the default key combinations should be Cmd-tab / Cmd-shift-tab. Otherwise, it just isn't the Windows alt-tab experience. Not even close. It's something admittedly kind of similar, but different and confusing. So frankly, either try to do what you promise on the web page and provide a Windows alt-tab-like experience by default, or don't promise to do that at all (obviously I really hope you pick the first option and just make this small change to the default key combinations).

PS. I really hope this doesn't make you double down and dig in your heels. I really like AltTab but the defaults are, well, wrong, because they are not at all "Windows alt-tab-like"

@SoPat712
Copy link

The name of the app is Alt Tab? In preferences you have the ability to change the modifier key used? I don't see how this matters in any way, and changing the default is something that you can do in 10 seconds. @lwouis I entreat you to close this, because this is frankly a waste of time, changing the default shortcut would be even more confusing as the name of the app HIGHLIGHTS THE KEYBOARD SHORTCUT.

@lwouis
Copy link
Owner

lwouis commented Sep 28, 2020

Regarding the backwards-cycling shortcut using shift not being able to invoke the UI, there is already a ticket for that: #510

Regarding the idea that command is a better default than option, please understand that our experiences of life differ. It may be "obvious" to you that the other key is better, but most people think the option key is what it should be. How do I know that? Because i put command as the default key back in the early days of the app, and got lots of people complain that it was wrong, the same way you did here, so I changed it.

Also take a moment to consider how bare-bone the experience is on Windows. There is literally no preference. You can't change de shortcut, you can't have multiple shortcuts, you can't decide to show certain types of windows, change the layout, etc etc.

You keep copy-pasting the slogan like it's a holy gospel. This slogan is to quickly tell people what the app is about. It is not a promise to make a clone. My goal is to go beyond what the venerable tool has been doing on Windows for 25 years. 25 years during which they haven't updated it much. I intend on putting as much thought as possible and make it the best it can be. That includes better ergonomics by defaults, and a wide breath of customization options

@lwouis lwouis closed this as completed Sep 28, 2020
@lwouis lwouis added documentation Improvements or additions to documentation duplicate This issue or pull request already exists labels Sep 28, 2020
@lwouis lwouis added support/question The author was looking for help, or didn't understand something and though it was a bug and removed documentation Improvements or additions to documentation labels Oct 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists support/question The author was looking for help, or didn't understand something and though it was a bug
Projects
None yet
Development

No branches or pull requests

3 participants