I'm getting Zomg has attempted an action only allowed by the Blizzard ui (Disable, Ignore)
On my paladin with any attempt to buff, either by the mousewheel, or even if I rebind it to spacebar.
I think it's because I have those bound to something else already? I did manage to get it to stop if I bound it to something that has no binding associated with it, maybe something wrong with how it's trying to override bindings?
Well first, I don't have epic flight, so <f280> .. stays <f280>, but <f60> changes to Flight Form() as expected.. and <ff> still changes to <f>
Edit: also it appears it's not reading Shattrah as Flyable, at least, it's still showing my 'ground' macro in the mounted macro, strange.
Edit2: Ok, toasted savedvars, Flight menu, both Default and Default Dismount change from <ff> to <f> on preview.
Edit3: Just to provide some background, I have 1 flying "mount", flightform, and 2 ground mounts, frostsaber and the stormpike ram, might be something to do with not having a 'regular' flying mount, though just about any fresh druid would be in the same situation since druids get flight at 68.
Okay, with the new one, it doesn't throw an error, but it still doesn't work right, at least in my estimation, it's still defaulting to a ground mount in outlands, the default dismount looks as:
It was the default dismount flight, I believe. And, just tested 1.3.3 and.. it still throws up when hitting preview, making the entire flight menu go blank, different error though, and flight is only showing up when moving, not stationary.
[2008/11/06 03:16:14-13350-x1]: Mounted-1.3.3.20081106022520\Mounted.lua:212: bad argument #3 to 'format' (string expected, got nil)
Mounted-1.3.3.20081106022520\Mounted.lua:212: in function `GetRandomMount'
Mounted-1.3.3.20081106022520\Mounted.lua:250: in function <Interface\AddOns\Mounted\Mounted.lua:242>
(tail call): ?:
(tail call): ?:
AceConfigDialog-3.0\AceConfigDialog-3.0.lua:245: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:193>
AceConfigDialog-3.0\AceConfigDialog-3.0.lua:367: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:340>
AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1032: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1028>
AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1466: in function `FeedGroup'
AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1388: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1368>
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[3]":9: in function <[string "safecall Dispatcher[3]"]:5>
...:
...ns\Ace3\AceGUI-3.0\widgets\AceGUIWidget-TabGroup.lua:139: in function `SelectTab':
AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1502: in function `FeedGroup'
AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1708: in function `Open'
AceConfigDialog-3.0\AceConfigDialog-3.0.lua:811: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:600>
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[3]":9: in function <[string "safecall Dispatcher[3]"]:5>
(tail call): ?:
AceGUI-3.0\AceGUI-3.0.lua:264: in function `Fire'
...ns\Ace3\AceGUI-3.0\widgets\AceGUIWidget-CheckBox.lua:51: in function <...ns\Ace3\AceGUI-3.0\widgets\AceGUIWidget-CheckBox.lua:47>:
---
Not considering Flight form a valid flying mount with 1.31
Doing preview on Flight makes it throw up.
[2008/11/05 07:33:45-13337-x1]: Mounted-1.3.1.20081104215838\Mounted.lua:213: bad argument #1 to 'pairs' (table expected, got nil)
Mounted-1.3.1.20081104215838\Mounted.lua:213: in function `GetRandomMount'
Mounted-1.3.1.20081104215838\Mounted.lua:249: in function <Interface\AddOns\Mounted\Mounted.lua:241>
(tail call): ?:
(tail call): ?:
AceConfigDialog-3.0\AceConfigDialog-3.0.lua:245: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:193>
AceConfigDialog-3.0\AceConfigDialog-3.0.lua:367: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:340>
AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1032: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1028>
AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1466: in function `FeedGroup'
AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1388: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1368>
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[3]":9: in function <[string "safecall Dispatcher[3]"]:5>
...:
...ns\Ace3\AceGUI-3.0\widgets\AceGUIWidget-TabGroup.lua:139: in function `SelectTab':
AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1502: in function `FeedGroup'
AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1708: in function `Open'
AceConfigDialog-3.0\AceConfigDialog-3.0.lua:811: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:600>
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[3]":9: in function <[string "safecall Dispatcher[3]"]:5>
(tail call): ?:
AceGUI-3.0\AceGUI-3.0.lua:264: in function `Fire'
...ns\Ace3\AceGUI-3.0\widgets\AceGUIWidget-CheckBox.lua:51: in function <...ns\Ace3\AceGUI-3.0\widgets\AceGUIWidget-CheckBox.lua:47>:
---
Replace those 2 functions and it works just fine, even catches the new talents. The only thing is it won't catch any new items that are not standard, which is really only an issue with northrend/beta.
Not to drag up an old thread, but Crowbar appears to not see Jaggal Clams anymore, maybe other clams too, probably something to do with the fact that it appears clams stack now.
Bit more fiddling, and it appears to be something specific to Mouse Anchor for nonunit tooltips, either smart or normal anchor and it works normally with no flicker, so strange. Ah well, close enough.
It doesn't happen with the regular tooltip no, and I would, if any of those actually did what I want, cowtip is a monsterous mess, and tiptop is too limited and bland, so.. yah
Hmm, well I just tried Fortress, same problem, so that makes ButtonBin, DbIcon, and Fortress all exibiting the same thing, click2cast, bugsack, magictarget, closet gnome, bigwigs, bartender4, ora2 all do it, Skinner, yurrcombatlog do not, not sure what the deal is.
Also, it appears the tooltip will stay solid, if I find the exact spot on the icon, like on the minimap icon if I find the more or less exact center it will stay solid, anywhere else and it flickers.
No increase that I can determine, cpu profiling on or not, I also tried with just bugsack, buggrabber, tiptac, and it still flickers.
I know it doesn't 'feed' a tooltip, but I imagine there is a standard way the display addons are creating tooltips for ldb, which from all apperances here, is causing it to flicker badly with tiptac, regardless of ldb display, which makes me think there is a flaw in how the tooltips are being created for ldb, shrugs.
No, but I also don't get it with any other tooltip other than the ldb feeds, with multiple displays, which led me to believe it being something odd in the way that ldb feeds its tooltips.
0
goes with it.
0
0
On my paladin with any attempt to buff, either by the mousewheel, or even if I rebind it to spacebar.
I think it's because I have those bound to something else already? I did manage to get it to stop if I bound it to something that has no binding associated with it, maybe something wrong with how it's trying to override bindings?
0
0
Edit: also it appears it's not reading Shattrah as Flyable, at least, it's still showing my 'ground' macro in the mounted macro, strange.
Edit2: Ok, toasted savedvars, Flight menu, both Default and Default Dismount change from <ff> to <f> on preview.
Edit3: Just to provide some background, I have 1 flying "mount", flightform, and 2 ground mounts, frostsaber and the stormpike ram, might be something to do with not having a 'regular' flying mount, though just about any fresh druid would be in the same situation since druids get flight at 68.
0
#showtooltip
/dismount [mounted]
/cancelform [stance:4/6]
/cast [nomodifier] <ff>; <gf>
but when I do a preview, that last line changes to :
/cast [nomodifer] <f>; Swift Frostsaber()
0
0
Doing preview on Flight makes it throw up.
0
0
0
0
0
Also, it appears the tooltip will stay solid, if I find the exact spot on the icon, like on the minimap icon if I find the more or less exact center it will stay solid, anywhere else and it flickers.
0
I know it doesn't 'feed' a tooltip, but I imagine there is a standard way the display addons are creating tooltips for ldb, which from all apperances here, is causing it to flicker badly with tiptac, regardless of ldb display, which makes me think there is a flaw in how the tooltips are being created for ldb, shrugs.
0