Authors CurseForge

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?

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.

Quote from Marandopsu

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?

What's happening is that Grid (in your example) has told the game that it will handle ALL mouse clicks made while the mouse is hovering over one of its frames. There's not much you can do about that unless Grid lets you make its frames noninteractive (sometimes called "clickthrough" behavior because it describes a mode where you can "click through" the frame onto the game world).

I try to keep a decent portion of the center of my screen clear of click-catching things to avoid this problem.

Frames are either "click-through" or not "click-through". You can't selectively intercept, say, left-click, but pass right-click or button4-click through to whatever's underneath. Since there's not much point in having unit frames that don't respond to the mouse, you're pretty much out of luck unless you remap those buttons to keyboard keys like you mentioned, or install Clique. Since click-bindings only apply to unit frames, your mouse5 click on the world frame would still do whatever it does now, and you could set up a mouse5 click binding in Clique to execute a macro such as "/cast [target=target] [] Rejuvenation". Clique isn't limited to mouseover casting, and since there are only a small number of bindings that can be affected by this issue, it wouldn't take too long to set it up that way.

Actually Phanx is wrong, give me a sec to dig up the documentation.

http://www.wowprogramming.com/docs/widgets/Button/RegisterForClicks

Grid is probably using frame:RegisterForClicks("AnyUp") when you would rather it use frame:RegisterForClicks("LeftButtonUp", "RightButtonUp", "MiddleButtonUp"). You could try making a suggestion that Grid2 allow for this behavior to be customizable in the user settings.

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!

Quote from Arrowmaster

Grid is probably using frame:RegisterForClicks("AnyUp") when you would rather it use frame:RegisterForClicks("LeftButtonUp", "RightButtonUp", "MiddleButtonUp"). You could try making a suggestion that Grid2 allow for this behavior to be customizable in the user settings.

Maybe I'm doing it wrong, but my experience has always been that registering a frame for LeftButtonUp just causes all right-clicks over the frame to vanish into a black hole rather than being passed through to whatever's underneath the frame.

As for including this in Grid(2), it's unlikely it will happen. Restricting the frames to left- and right-clicks only would break things for click-casters, but adding in options to toggle every possible click (most of which are only useful for click-casters) would be too far down the road of building in click-casting, which is something the authors of Grid have always declined to do, and for good reason.