Contact
Reporting a problem
Tickets: sourceforge.net/p/alttab/tickets/
That is the right place for anything reproducible — a hotkey that does nothing, a window that is not listed, a setting that appears to be ignored, a crash. It is public, so it can be searched by the next person with the same problem.
What to put in it
Press Shift+F1 and then Copy details. That is the version, the commit, the build time, the architecture and the Windows build, all on the clipboard — the first question anyone reading a report has to answer is which build is this, and that line answers it.
Then, whichever of these apply:
| What was in front | And whether that window was elevated (Task Manager, an installer, anything "as administrator"). |
| Whether AltTab is elevated | The About box's version line says so, and only when it is. |
| The exact keys | "Held Alt, tapped Tab, pressed Apps, pressed Escape" tells far more than "the menu is broken". |
AltTabSettings.ini | For anything about appearance, filtering or which windows appear. |
%LOCALAPPDATA%\AltTab\AltTab.log | If you are running a build that logs — see below. |
About the log
The ordinary package is ReleaseNoLogger: logging is compiled out, so it writes no log file at all. If a log is asked for, the ReleaseLogger archive in the same download area is the one to reproduce against. It writes to %LOCALAPPDATA%\AltTab\AltTab.log.
A log holds the titles and paths of the windows that were open while it ran. Read it before you attach it, and if something in it should not be public, send it by email instead of putting it on a public ticket.
Ideas and questions
The tickets are as good for "could it do this?" as for "this is broken". Several settings exist because somebody asked for them.
If you are asking for a feature another switcher has, naming it and saying what you do with it helps more than the feature's name alone — the useful part is usually the gesture, not the label.
By email
For anything that should not be on a public ticket:
- a log or a screenshot with window titles you would rather not publish;
- something you believe is a security problem — please describe what it lets an attacker do, and give a little time for a fix before publishing it anywhere;
- the LGPL written offer of source for the log4cpp build (see About).
Privacy, in one line
AltTab sends nothing anywhere except the update check, which fetches a version file over HTTPS and uploads nothing about you. Crash reporting, when it is switched on, sends stack frames and cannot produce a memory dump or a screenshot — deliberately, because this application's memory is a list of every window you have open. PRIVACY.md in the release archive is the full account.
Before you write
Troubleshooting covers the three commonest reports, and each has a specific cause worth ruling out first:
- the hotkeys do nothing — usually an elevated window in front, which an unelevated AltTab cannot take the keyboard from;
- a window is missing from the list — three separate settings can each hide one, and none of them says so;
- a setting appears to be ignored — the Advanced page in the Settings dialog lists every key the application actually reads, with the value it currently holds beside the default.