Alt-Tab Toggle
Alt-Tab Toggle (ATT) will force WoW to the foreground on events when you're alt-tabbed. Optionally you can choose to only play a sound when one of these events fire. Then you can tab back into WoW at your leisure.
Events that ATT will toggle include
- Auctioneer scan, search and post complete [W]
- BankStack complete [W]
- BG Deserter debuff expire,
- BG idle debuff,
- BG gates opening
- Duel request (2.1.5beta),
Dungeon Deserter/Cooldown debuff expire
- Enemy detected,
- Enter Battleground window,
- Enter combat,
- Flight land,
- Group invite,
- Group ready check,
- LFG boot proposal,
- LFG enter proposal,
- LFG role check,
- Mailbox, finished looting (2.1.7beta) [W]
- Resurrection request (2.1.2beta)
- Summon request,
- Trade skill finish crafting [W]
- Whispers,
- Wintergrasp Starting,
- Zeppelin arrival
[W] = window mode only
Leave a ticket if you have another event that should be added.
FAQ:
Q) How does ATT bring WoW to the foreground?
A) ATT uses a console command gxRestart that inadvertently causes WoW to jump to the foreground (in full screen mode).
Q) I'm in window mode and WoW's not coming up.
A) Unfortunately the console gxRestart command doesn't work in window mode. You'll have to use the alert sound.
Q) I'm in window mode and ATT's alerting when I'm not alt tabbed.
A) The Alt-Tab Detection is giving false positive. This usually happens to slow PCs or under heavy load (-10FPS). If this is causing problems, turn off Alt-Tab Detection and manually activate ATT by typing /att before you alt tab out.
Q) How does Alt-Tab Detection work?
A 1) When fullscreen WoW loses focus, frames stop updating. ATT checks if it's been 5+ seconds since the last frame update.
A 2) When windowmode WoW loses focus, FPS drops to -10, ATT checks if your FPS has dropped below 10 for over 5 seconds. this could give false positives on slow PCs.
Q) What does AFK Activate do?
A) AFK Activate is a old feature that activated ATT when you went /afk. Once you returned you could move/jump and ATT would deactivate. AFK Activate isn't needed now with Alt-Tab Detection.
Q) Will you add a toggle for the ingame alarm clock?
A) Currently not possible. When WoW loses focus frames stop firing OnUpdate. The alarm clock uses OnUpdate to fire the alarm.
Q) ATT caused WoW to crash and give error #132.
A) Checkout Blizzard's Error #132 page. If that doesn't help try enabling ATT's Sound Only option on.
Q) AddonUsage / TitanPerformance claims ATT is using lots of CPU usage, why?
A) The Ace3 libraries ATT uses are probably being used by other addons and ATT is getting the blame. Try downloading Ace3 separately from here and see if that helps.
Q) Are there alternatives to Alt-Tab Toggle?
A) Yes, LFGMaximizer, EventNotifier and AltTabber that I know of.
Discussion page: here
Credits:
- CUDiLLA - German (deDE) translator
- kdw112 - Korean (koKR) translator
- fxpark - Korean (koKR) translator
- KAPMA - Russian (ruRU) translator
- zhTW - Traditional Chinese (zhTW) translator
- Mars1491 - Traditional Chinese (zhTW) translator
Translators needed - apply localizations here.
Donations welcome. There's a donate button here.
Bitcoin address: 13mvJMp8Z38SUAnZ4PgGpio5L2inqWQGsP
in line 116:
change
MAX_BATTLEFIELD_QUEUES
to
GetMaxBattlefieldID()
and delete line 111, if you want :)
This is to make the addon work with battleground pop-ups as well. Just for clarification: you need to change line 116 in the file "BGConfirm.lua", which is located in ...\AddOns\Alt-Tab_Toggle\modules
Hey thanks for the add-on helping me a lot ! However when i join a bg queue i see this error and addon doesn't work.
Date: 2012-02-26 10:28:14
ID: 1
Error occured in: Global
Count: 1
Message: ...nterface\AddOns\Alt-Tab_Toggle\modules\BGConfirm.lua line 116:
'for' limit must be a number
Debug:
(tail call): ?
...nterface\AddOns\Alt-Tab_Toggle\modules\BGConfirm.lua:116: ?()
...gle\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:147:
...gle\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:147
[string "safecall Dispatcher[2]"]:4:
[string "safecall Dispatcher[2]"]:4
[C]: ?
[string "safecall Dispatcher[2]"]:13: ?()
...gle\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:92: Fire()
...t-Tab_Toggle\libs\Ace3\AceEvent-3.0\AceEvent-3.0.lua:120:
...t-Tab_Toggle\libs\Ace3\AceEvent-3.0\AceEvent-3.0.lua:119
Thank you so much! Greatest under-rated plugin I've ever seen. Please keep up the good work!
Suggest you to add detection when DBM AFK timer finishes (Pizza!-like). Thanks in advance.
--- Update ---
Ok, since i love this addon and im determined to figure out whats going on, i have been playing around with the settings, a lot.
If i leave "Deactivate after Toggle" checked, the addon works correctly. It remember to turn the addon back on, after i relog, reload, or change characters.
I dont understand what the "Deactivate after Toggle" is really suppose to be used for. I was under the impression that this was an option, so you could set the addon to play an alert one time, and then disable the addon. Obviously thats not whats going on, since it will continue to do all the alerts, until you disable the addon via "Active".
So at the very least, i am now able to use the newer versions and have them save my settings. The problem with being forced to have "Deactivate after Toggle" enabled, is that if you have to reload during combat, the addon never has a chance to "Deactivate" and thus when you log back in, the addon is once again set to "Active" = unchecked.
Glad to see you started working on this again. Quite a few updates the last few days.
Unfortunately with R 2.3.0 the addon still shuts itself off when you logout, switch characters, or simply reload the UI.
Completely fresh install, with only ATT running. (deleted the saved variables for att, and removed the older version). I go to Interface > ATT. From here i set my options as follows:
Active - Checked
Deactivate after toggle - Not checked
Activate on Login - Checked
Ignore when DnD - Checked
Alt Tab Detection - Unchecked
Sound Only - Checked
AFK Activate - Unchecked
I go into combat, zepplin shows up, BG que pops, etc etc, the alerts work as intended. If i reload my UI, log out for any reason, or switch characters..... when i log back into the game all the settings stay the same except "Active" is now unchecked. No sounds play unless i remember to go back into Interface, Go to ATT, and re-enable the addon.
This has been an issue since the addon was upgraded to 2.X.X. The original version 1.4.0 works right out of the box, and saves yours settings between sessions. Not sure what has changed :(
------------------------
Also in the latest release, (as per the change log) the addon is now enabling all World of Warcraft sounds for 2 seconds, then shutting them off. Why was this added back in? Addons can fire sounds again, without forcing all sounds to enable. Listening to a train set, annoying mounts (choppers, trikes, etc) is unnecessary.
------------------------
Fixed ZeppelinArrival not detecting NPC names from their npcIDs.
This is working correctly now, at least for all the Zeps i tried.
------------------------
I believe the Wintergrasp timer still works correctly, but there has been a new "world" pvp encounter called Tol Barad. No one plays WG anymore (old content), but TB is the new WG. Any chance of getting an option to activate when TB is available (just like the WG option we have currently)?
@angrysteel
I haven't really played WoW in 6 months. Just noticed the copy of ATT on my PC was different from the version in WoWAce's repo. So I uploaded it as a alpha version. I probably won't be tagging any new beta/releases for awhile.
Hi Stealthmasta. I just checked in game and the per event options are still there. Maybe you're used to a older version. The event options are setup as submenus now. Click the [+] button next to the addon name in the list. Or type "/att x" to bring it up.
Don't know if you'll ever see this but is there any way to get the options of what notifies and what doesn't back? It seems like I can only edit the basic options but none of the toggles for what it will alt-tab for.
Date: 2010-09-27 09:48:19
ID: 1
Error occured in: AddOn: Alt-Tab_Toggle
Count: 1
Message: Error: AddOn Alt-Tab_Toggle attempted to call a forbidden function (FocusUnit()) from a tainted execution path.
Debug:
[C]: FocusUnit()
..\FrameXML\ChatFrame.lua:1247: ?()
..\FrameXML\ChatFrame.lua:4031: ChatEdit_ParseText()
..\FrameXML\ChatFrame.lua:3660: ChatEdit_SendText()
..\FrameXML\ChatFrame.lua:3698: ChatEdit_OnEnterPressed()
[string "*:OnEnterPressed"]:1:
[string "*:OnEnterPressed"]:1
AddOns:
*lots of addons*
BlizRuntimeLib_deDE v3.3.5.30300 <eu>
(ck=1450)
It happened only this one time, maybe it can help you somehow.
And I would like to thank you for this awesome addon which makes surfing on the net, during a wow session so much better.
it appears to deactivate itself when i logout/login.
Started about a week ago.
Unfortunately this is not the case.
Last part of the settings file:
["profiles"] = { ["Default"] = { ["disableAfterToggle"] = false, ["altTabDetection"] = false, }, },
Even if I enter the game, ATT is disabled by default.
Enabling the option, clicking ok, reopening the interface - addon frame, disable it, hitting ok. Typing /att. Logoff. Login, interface - addon - att -> att is disabled *sigh*
Tried it with r123, no change.
Regards, Highend
@Highend The option was renamed to Disable After Toggle. Disable the option then type /att. ATT will then always be on until logout.
Sine a few versions I'm just unable to use ATT in a "always on" mode, it's autodisabling and has to be set to on manually.
Active, Ignore when DND and Sound only are my standard settings and I tried every combination of the other three settings to no avail.
Is a "always on and don't disable ATT after toggling the game" not supported anymore?
I deleted all .lua setting files, installed 2.1.6beta just to be sure there is no misconfiguration through an older settings file. All chars use the default profile.
Regards, Highend