Clique 

EDIT: I have found the source of the problem! See my "edit 5" below. I would indeed call this a bug with Clique, but it might be something the author cannot do anything about.

EDIT: I apologize for how large this post has become!

Hello, Cladhaire! I want to say that I love your addon! I have recently begun having some issues, however. I apologize if they have been discussed below already.

I recently purchased the Razer Naga, and I use it in NumPad mode. If you aren't familiar with it, this simply means that pressing the side buttons is equivalent to pressing the numbers 1-9, 0, -, and + on the NumPad.

I heal on my resto shaman using Clique with the default Blizzard raid frames. Through Clique, I have bound all of the side buttons (really, the NumPad keys) for my various healing spells. Additionally, using the default Blizzard key bindings interface, I have some of the side buttons (again, the NumPad keys) bound to various cooldowns, totems, and self-buffs that do not require targets. For example, pressing button 1 when my cursor is placed over a raid frame casts Healing Wave (HW) via Clique, but pressing the same button when my cursor is elsewhere activates Water Shield (WS) from my action bars via Blizz's key bindings.

This works wonderfully most of the time. However, on occasion my bindings will behave as if my cursor is not over a raid frame when it actually is, or vice versa. I can't find a way to reproduce this bug reliably, but it does happen perhaps once or twice each raid boss encounter seemingly at random. For example, I may move my cursor over a raid bar that needs some healing, press 1 on my Naga, and instead of casting HW I see my WS refresh. If I press 1 repeatedly, WS will continue to cast until I move my cursor off my raid frames and back on. At that point my bindings will work fine again.

Sometimes the bug manifests itself in the opposite way, although this happens much more rarely. e.g., I may try to cast WS, with my cursor nowhere near a bar, and instead I will begin to cast HW on someone (who knows who?). Until I move my cursor onto a bar and back off, I cannot cast WS.

These problems occur with any and all of my side mouse buttons (again, the NumPad keys). Sometimes I will attempt to cast Healing Surge and instead I get the targeting reticule for Healing Rain. Sometimes I'll try to refresh Earth Shield on the tank and instead I pick up my totems. Sometimes I'll try to use a heal, and instead I burn my Mana Tide Totem cd. As you can imagine, this has caused wipes.

Whenever the bug occurs, the spell that is cast always would be the correct one had my cursor been someplace else, i.e. Clique behaves as if it is not properly registering the position of my cursor or the presence/absence of my raid frames. I do not have any way of knowing for sure that the problem is Clique. It may in fact be a problem with Blizzard's UI (I haven't tested other raid frames), but the fact that occasionally my Clique bindings will activate when my cursor is not positioned over a bar makes me suspect Clique. Furthermore, I believe that I have experienced this bug on occasion when using character portraits (again, the Blizzard default portraits) for healing instead of the raid frames.

I have seen this bug occur most commonly in raids (where I am, of course, using Clique the most), but I have also seen it occur sitting in a capital, out of combat. As I said before, it isn't until I move my cursor on or off a raid frame and back to its original position that the problem resolves itself.

Before I purchased the Naga, I used Clique without an issues. However, I used combinations of modifiers + left/right click to do my healing, and I didn't have any other spells bound to these keys through the Blizzard UI, so it's fair to say that I wouldn't have observed the problem if it occurred at all previously.

I will emphasize that each of my Clique bindings are set to "Default" (except for Hex and Bind Elemental, which are set to "Enemy"), and I have no "Global" or "Hovercast" Clique bindings.

I am wondering if you have any advise on how to go about troubleshooting this problem. Perhaps I should be using Clique exclusively, with my cooldown/WS/etc bindings set up as "Global" Clique bindings (if I understand that setting correctly)? Maybe this issue has been resolved previously. If posting my exact bindings or my addons used would be helpful, I will be happy to do so.

Any tips you can provide would be greatly appreciated! Once again, I love this addon! Couldn't live without it!

EDIT: I am using Clique v40000-1.3.4.

EDIT 2: In tonight's raid, I tried what I suggested above. I removed all my Blizz bindings for non-targeted abilities and rebound them as "Global" Clique bindings. Unfortunately, this did not fix my issue.

EDIT 3: If I use the following macro (found in this thread) whenever my bindings are malfunctioning, should I expect it to reveal any addons that might be interfering via hidden frames? (I know close to nothing of LUA or the WoW API.) I won't be able to test this tonight, but I will try it out tomorrow if I have time.
EDIT 4: I did some testing today. I disabled all addons except for Clique. I retained the Global bindings I set up last night. I replaced my HW binding with a macro that runs the script posted above and casts HW. I did the same for my WS binding. I grouped up, and I proceeded to click my mouse side button 1 furiously over the default party frames (which I have set to "Use Raid-Style Party Frames"). This was done out of combat sitting in a capital city. I was unable to reproduce my issue.

However, I did discover that if I clicked whenever my cursor was over a buff icon, my Global binding (in this case, WS) triggered instead of my Default binding (HW). It is very possible that some of the times during raids that I have thought I was experiencing a bug I was in fact clicking on buff or debuff icons. I'm still not convinced I have hallucinated this entire issue, but it is very likely that another addon is the source of the problem.

As far as I can tell, I should be able to click on buffs/debuffs and still have healing spells be cast. I do not have any frames blacklisted, and I have all Blizzard frames set to auto-register. Here are two screenshots of my Clique options:
http://img717.imageshack.us/i/cliqueblacklist.jpg/
http://img688.imageshack.us/i/cliqueblizzoptions.jpg/

I went a little over the top putting this image together:
http://img853.imageshack.us/i/cliqueframes.jpg/
(I was quite meticulous in getting the boundaries exact.) In that image, the red and orange areas (1-5) are the only places where "Default" Clique bindings trigger instead of "Global" bindings. In particular, when I clicked on the purple area marked as "12", my WS triggers and the script states that the frame is named "CompactPartyFrameMember1Buff1". I can see that this frame is not blacklisted. I experience the same behavior with buffs or debuffs, in a party or a raid, in or out of combat. Is this intended behavior? Could this possibly be changed so that I don't have to worry about dodging buff/debuff icons in the heat of battle?

EDIT 5: I have figured out how to reproduce the bug! As I said in my previous edit, if the cursor is placed over a buff or debuff icon in the default raid-style frames, Clique behaves as if the cursor is not over a unit frame at all. I just discovered that if a buff or debuff expires while the cursor is over its icon, Global bindings will continue to trigger until the cursor moves off the unit bar and back on. In other words, "onleave/onenter" events are not triggering when a buff/debuff icon disappears beneath the cursor, and the bindings are not being rebound properly.

Maybe there is nothing that can be done to fix this; this may be a case where the API isn't sophisticated enough for an addon author to do anything about it. However, like I said above, I don't know much about writing WoW addons. Cladhaire, can we expect a fix for this issue?

EDIT 6: I tried blacklisting all the frames with names of the following forms, but to my surprise this had no effect whatsoever on my problem. I did remember to /reload, and I tried logging out and back in.
CompactPartyFrameMemberXBuffX
CompactPartyFrameMemberXDebuffX
CompactPartyFrameMemberXDispellDebuffX
CompactRaidFrameMemberXBuffX
CompactRaidFrameMemberXDebuffX
CompactRaidFrameMemberXDispellDebuffX

So any update with the random breaking of bindings? Seems for me the only binding that breaks is right mouse click (constantly I might add) generally if I switch toons or get logged off I have to delete my binding then re-add it (or a ui reload as others have stated.) Most of the time that fixes it, but every so often even if I DO do that it'll break again some 20+ minutes later.

I just thought I'd repost this, since my original post just below is probably rather intimidating. This summarizes the issue nicely, I hope.

EDIT: I tried blacklisting all the frames with names of the following forms, but to my surprise this had no effect whatsoever on my problem. I did remember to /reload, and I tried logging out and back in.
CompactPartyFrameMemberXBuffX
CompactPartyFrameMemberXDebuffX
CompactPartyFrameMemberXDispellDebuffX
CompactRaidFrameMemberXBuffX
CompactRaidFrameMemberXDebuffX
CompactRaidFrameMemberXDispellDebuffX

Thank you for the response, Cladhaire!

I am afraid that I did confuse myself in that final edit about blacklisting, and that I didn't fully communicate what I had done. I suspect that there is nothing wrong with your blacklisting code, and I intend to test it once the servers come back online.

I had forgotten that I had removed my "Global" Clique bindings and returned to using the Blizz action bar bindings for my non-targeted cooldown abilities. If I now understand how the blacklist works, then I should not have expected any change in behavior. I suspect that if I had blacklisted the frames I mentioned when all my bindings were still Clique bindings, then clicking on buff/debuff icons in the compact raid frames would have caused nothing to happen at all.

This would be a partial solution to the issue I've been having, since it would prevent me from accidentally blowing cooldowns when I click directly on buff/debuff icons. However, if I understand this correctly, I will still experience the problem of being "locked into" "Clique Global binding mode" any time an icon disappears underneath my cursor, and my next click may trigger a cooldown instead of casting a healing spell. I would still need to move my cursor away from that bar and back before I could heal again.

I will try testing all of these things when the servers come back online. Do you think your suggestion about editing BlizzardFrames.lua is still relevant, now that I have (hopefully) clarified myself? Sorry for the confusion!

I'm curious which parts you have been unable to reproduce. You very well may be speaking of only the blacklisting issue I addressed below, in which case I again apologize for my mistake.

I had originally said that I had previously experienced the issue of the wrong bindings firing when healing using character portraits. If you take a look at this image,
http://img853.imageshack.us/i/cliqueframes.jpg/
you can see that for the target portrait and the focus portrait several buff icons (purple) overlap with the clickable (red) regions. It is possible that when I experienced this bug, it was another case of icons disappearing beneath my cursor. It is conceivable that I was moving my cursor from the middle of my screen upward toward either portrait, and one of the target's/focus's buffs expired as I passed over it on my way to the portrait proper, after I had entered the boundaries of the red region (where the purple and red overlap). I was able to reproduce this reliably yesterday. Regardless, I am much less concerned about portrait healing than I am with the Blizzard raid frames.

The other issue I described was the inverse of this one, which I said I had only experienced very rarely. I would click outside of my frames, and a heal would begin to be cast on a mysterious target. I actually experienced this yesterday in a 5-man, and I think I have some intuition about what happened.

One of our group members had disconnected, so I right-clicked that person's unit frame (I "Use Raid-Style Party Frames"; I did not right-click their portrait), navigated down the menu to Vote Kick, and we removed him from the group. Seconds later, we had a new dps enter via the Dungeon Finder. As we were regrouping, I discover that my bindings were stuck in "Clique default binding mode", and that the target of my healing spells was the new dps.

I can only guess that when I navigated the right-click menu, I managed to avoid an "OnLeave" event since I most likely passed out of the unit frame boundaries when moving over the menu. This is such an obscure, rare thing that it doesn't concern me at all, but perhaps it will irritate you.

I've been using a clique/grid for almost a year now for my healing/casting. I've recently had a virus and had to reinstall all my addons
I've got them all setup correctly but when I click (for example) shift + left click for my greater heal macro
/cast inner focus
/cast greater heal
it will only heal my literal target, or if no one is targeted, myself. I want to be able to cast these spells on any party member in the grid frame not only who i have targeted, its to cumbersome to have to target a new person every time i want to use my macro for gheal, poh. and binding heal.
Also i use pitbul for my target/self/targets target/ and focus frame

My email is [email protected], ign owim (sisters of elune)

I believe you need to change your macro to the following:

As I've said before, I know virtually nothing about LUA or the WoW API, and so most of these suggestions may be impossible. However, my naive mind can think of a few potential solutions to the problem. You have likely considered and discarded all of them because of the added cost to the performance or aesthetics of your code, but I'll throw them out there all the same. You may also consider this to be a minor issue, and I couldn't blame you, since I don't see anyone else complaining.

Below, I am operating on the assumption that Clique works by detecting whenever the cursor crosses the boundary of a frame registered by it and changing all bindings appropriately at that time. The primary issue then is the rare occurrence of a missed boundary-crossing, which can occur when an unregistered frame is placed between the cursor and a registered frame. The cursor can escape the registered frame via the unregistered frame without technically crossing the registered boundary, or the cursor can enter the registered frame when the unregistered frame is removed or hidden. These missed boundary-crossings will result in incorrect bindings.

1. Make the buff/debuff icons on the Blizzard compact party and raid frames and the right-click menu "Clique-compatible." If the icons were registered properly with Clique, there would be no issue. I have seen that it is simple for other addons to integrate Clique-ability in your tutorial. However, I have no doubt you would have done this already if the API allowed for it, unless you see it as the job of a third-party addon.
   
2. Check whether bindings need changed on-click. Not only are rebindings triggered by clicks probably forbidden by the API, but it is inefficient and could have a severe performance cost. However, if Clique could check the location of the cursor at the time a click is made, it could never fail.
   
3. Check whether bindings need changed periodically in addition to monitoring boundary-crossings. If you can check for the need to rebind when the cursor crosses a boundary, perhaps it is possible to check the current position of the cursor at regular intervals to see if all the bindings are properly set. This is probably even less efficient than the last suggestion, and if the sampling rate isn't high enough, clicks could get through before the bindings can be corrected. However, since this issue is relatively rare, using a low sampling rate would be okay.

If you do think that a third-party addon is needed here, and you would prefer not to take this on yourself, I may have an excuse to finally learn WoW addon coding. I am fluent or at least very familiar with C, C++, Java, R, Python, Mathematica, and MATLAB, so I might not have too much difficulty diving into things with a few pointers.

Excellent! I see you posted this while I was working on my most recent post. Maybe you have made it irrelevant.

I will try this out when the servers come back online. Thanks for taking the time when you are on holiday! (You really shouldn't have!)

EDIT: "The specified file was not found."