• 0

    posted a message on Secondary mouse buttons (m4&m5) and game windows
    Thanks for the information about the coding causing this. I was hoping it was something simple that could be fixed with a simple .lua change, but I guess not :)

    Quote from OrionShock
    clique and custom macros.

    /cast [target=target] <spell>

    while this might look redundant, it's an implicit definition so that it dosn't do anything weird.


    Quite the contrary! I gave clique a shot, as I was under the impression that it was only for mouseover casting. Using your suggested macro I was able to get it to do exactly what I wanted to do while I was mousing over the grid frame(and thanks to all for that, was a simple fix)... however it IS indeed doing something weird.

    When my target is/moves out of range and I hit my clique bind, instead of giving me the error "Out of range" like it usually would if the target was out of range... it just defaults my cursor to the glowy hand and waits for me to click on somebody. Pretty annoying, as I rely on that message/sound to let me know some bonehead is running away from me.

    I'm sortof curious as to why it would be doing this. It certainly is a minor issue, and I will continue to use clique to fix my problem even if this can't be fixed. However if you know why this is happening and have a workaround, feel free to let me know :D

    [edit] Nevermind what I said about the range thing above. More messing around with it reveals that it was due to me originally testing with a friend in orgrimmar while I was in dalaran :D Normal range behavior ensues when I try it on somebody in my zone, lol. Thanks for your help!
    Posted in: General Chat
  • 0

    posted a message on simpleMinimap, now with Ace2 goodness
    I take back what I said a few posts ago. I can only track 2-3 quests at a time before getting the error message. Though this is an improvement over my original situation, it still isn't satisfactory.

    Anybody else have any ideas?

    [edit]: Found a solution, make the following script a macro and run it:

    /script WatchFrame:SetHeight(400)
    /script WatchFrame_ClearDisplay()
    /script WatchFrame_Update(WatchFrame)

    Should help with the issue, even if its only temporary. The 400 in the first line is equal to how big the frame will be. Make it as big/small as you want(If you get the error again after tracking a certain amount of quests, make it bigger).
    Posted in: Map/Minimap AddOns
  • 0

    posted a message on Secondary mouse buttons (m4&m5) and game windows
    Well, i dont wanna cast via mouseover... thats what clique does right? I just want my bind to go off on my current target, regardless of where my mouse cursor is on the screen. It works that way with keyboard buttons, but because these side buttons are registered as mouse clicks, you have to be moused over a blank part of the screen in order for them to fire.
    Posted in: General Chat
  • 0

    posted a message on Secondary mouse buttons (m4&m5) and game windows
    I have these side-mouse buttons bound to certain casts, for instance my M5 is rejuv. If I use these keybinds while mousing over an addon window, say grid, the action won't execute for some reason. I'd have to drag my mouse over to a clean part of my screen, and THEN hit m5 in order for the cast to go off.

    I suspect this is because the game/addon is registering the actions as a mouseclick instead of a keybind? Is there any way to remedy this without using a 3rd party software to rebind these mouse keys to keyboard keys?
    Posted in: General Chat
  • 0

    posted a message on simpleMinimap, now with Ace2 goodness
    Quote from kalidav

    This is the resulting file from the quest/achivement tracker frame removals (since they both use the new UI).

    Just replace everything after the translations at the top of the file /simpleMinimap/modules/movers.lua with this code.


    I did this, and I still receive the same error while trying to track quests.

    Quote from Delc
    In modules/movers.lua change:

    QuestWatchFrame to WatchFrame
    QuestWatch_Update to WatchFrame_Update

    Everything should work after that.


    Tryed this as well, also did not have any effect.

    Any ideas? It seems from the other comments that both these fixes are supposed to work. I definitely didn't execute them incorrectly, so what gives?

    [edit] Was able to fix by deleting simpleminimap.lua files in wtf/account/accountname/savedvariables folder after doing the above.
    Posted in: Map/Minimap AddOns
  • 0

    posted a message on X-Perl Thread
    http://img262.imageshack.us/img262/953/wowscrnshot020809005238qw1.jpg

    Without buff: (#) experiencing some bugs with another mod. I cannot for the life of me figure out how to disable that, where is this option located? I'd really like to turn it off until its fixed x.x
    Posted in: Unit Frames
  • 0

    posted a message on Grid
    Quote from eddie270
    I've been getting this error since I updated WoW to 3.1

    http://img26.imageshack.us/img26/7383/errorjtj.jpg

    Any assistance is appreciated.


    Confirmed what the above said. Curse/Curse updater is out of date, always hated that thing.
    Posted in: Grid & Grid2
  • 0

    posted a message on simpleMinimap, now with Ace2 goodness
    Quote from Khanan
    Is this mod no longer in development? Curious, as 3.1.0 seems to have broken the movers and it's nigh-on imperative I be able to move these (without having to use other broken move mods such as MoveIt or MoveAnything!).


    As a side effect of this problem, it's impossible to use the questtracker now. You'll get an error about having too many quests currently tracked.

    Other then that, seems to work fine in 3.1. Little touchup is all it would need.
    Posted in: Map/Minimap AddOns
  • 0

    posted a message on Interface hiding if you open map while in combat
    Old problem I remember from a long time ago, started happening again in 2.3. Ive let it go, mostly because ive been unable to pinpoint it, but its starting to get on my nerves! Especially since ive updated everything I use for 2.3.2, and its still happening.

    Anyone know the culprit?
    Posted in: General AddOns
  • 0

    posted a message on Why does this Babble crap auto download with AceUpdater
    I was just trying to figure out how to turn it off ;o sorry if i sparked something
    Posted in: Libraries
  • 0

    posted a message on Why does this Babble crap auto download with AceUpdater
    Quote from Seerah »

    This is off by default, btw - you enabled it. ;)


    Not so much, I download the updater default and hit update. Thats all ive ever done.

    @sylvanaar, I've disabled it daily and like I said, everything still works. So no, its not a good thing.
    Posted in: Libraries
  • 0

    posted a message on Why does this Babble crap auto download with AceUpdater
    Quote from Siz »

    Or turn off the Automatic Dependency Download option in WowAceUpdater.


    Thats the one. Thanks bud
    Posted in: Libraries
  • 0

    posted a message on Why does this Babble crap auto download with AceUpdater
    Seriously, forget the fact that 3 of them starts me up with errors. Forget the fact that it almost doubles my addon scroll list. I just plain don't want them. And having to delete them every single time I make an update is getting irritating.

    Sure I can disable them, but then they just turn themselves right back on. Why are they downloading when they're not checked, and why are they being forced on me when they're clearly not needed... as I always delete them with no consequences to my running addons?

    Do not want.
    Posted in: Libraries
  • 0

    posted a message on FrameXML\WorldMapFrame.lua & \PaperDollFrame.lua errors
    Itemrack causes this error when you mouse over and item in your character equip window.
    Extended Quest Log causes this error when you mouse over any square in any bag of your inventory.
    (?)Tinytip causes this error when you mouse over any square on grid.

    I have no idea why, all except for the third are confirmed 100%. Only reason i'm saying the third isnt confirmed is because i havent disabled tinytip yet, but heres the error:

    Interface\FrameXML\GameTooltip.lua:74: Usage: GameTooltip:SetOwner(frame):
    Interface\FrameXML\GameTooltip.lua:74: in function `TinyTipAnchor_Original_GameTooltip_SetDefaultAnchor':
    TinyTip\TinyTipAnchor.lua:143: in function <Interface\AddOns\TinyTip\TinyTipAnchor.lua:140>
    (tail call): ?:
    Interface\FrameXML\UnitFrame.lua:66: in function `UnitFrame_OnEnter':
    Grid-49704\GridFrame.lua:185: in function `OnEnter'
    Grid-49704\GridFrame.lua:107: in function <Interface\AddOns\Grid\GridFrame.lua:107>

    It seems to be a pretty widespread problem with alot of addons. I hope they all get fixed.
    Posted in: General AddOns
  • 0

    posted a message on How is the partys-target feature coming along?
    I just dont want to use anything with a big fat "Beta" stamped on it.

    Back to the AGUF question please >.>;
    Posted in: Unit Frames
  • To post a comment, please or register a new account.