Go to Page... |
Compatibility: | The War Within (11.0.2) The War Within Beta (11.0.0) Cataclysm Classic (4.4.0) Classic (1.15.2) WOTLK Patch (3.4.3) TBC Patch (2.5.4) |
Updated: | 09-15-24 08:58 AM |
Created: | unknown |
Downloads: | 1,274,485 |
Favorites: | 3,564 |
MD5: |
Clique is a simple addon that enables powerful click-casting and hover-casting on your unit frames and in the 3D game world. You can bind virtually any mouse or keyboard combination to a spell or macro. In it's normal configuration this enables you to use the bindings over your unit frames in order to cast spells directly on that unit. This allows you to more quickly select both the spell to cast, and the target of the spell without requiring an extra click.
To begin with Clique, open your spellbook and click on the new tab that is shown there. You can also open the configuration GUI by running the /clique slash command. From this binding interface you can add, remove and alter any of your Clique bindings. You will be unable to make these changes when you are in combat due to limitations in the Blizzard API.
Binding a spell
Binding a spell is just a matter of finding the spell in your spellbook, putting your mouse over it, and performing the binding you would like to add. For example, if you'd like to set 'Regrowth' to activate on 'Shift-LeftButton', then you just find that spell in your spellbook and then Shift-LeftClick on it. You can also bind keyboard combinations, so you could do the same with Shift-R if you'd like.
Keep in mind when you are setting your bindings that they will override any bindings that are already set on the frame, for example the default bindings to 'Target unit' and 'Show unit menu'. You can override these bindings if you would like, but you should then set a new different combination that will activate the original functions
Binding the 'Target unit' or 'Show unit menu' actions
If you've rebound or lose these default bindings, you can re-bind them using the 'Bind other' button in the Clique configuration. Click on the button, and choose the correct action and you will be presented with a dialog box that allows you to set the binding for that action. Simply choose a new key combination, and you will be able to target units and open your menu again.
Binding a macro
Binding a macro can also be found on the 'Bind other' button. You'll be given a new window with instructions and suggestions about writing your macros, but other than that the process should seem very similar.
Managing click-sets
Each binding can belong to a number of binding-sets. These sets determine when the binding is active. The built-in binding-sets are as follows:
File Name |
Version |
Hits |
Size |
Author |
Date |
v90001-0.1.0-beta |
3,686 |
103kB |
Cladhaire |
08-16-20 12:47 PM |
|
v40000-1.2.7-7e91cea |
2,931 |
79kB |
Cladhaire |
10-16-10 10:31 AM |
|
2.0.0-abfbb36 |
2,410 |
43kB |
Cladhaire |
10-11-10 04:34 PM |
|
r129 |
2,800 |
67kB |
Cladhaire |
11-14-09 11:55 AM |
|
r125 |
2,474 |
67kB |
Cladhaire |
11-14-09 11:46 AM |
|
r127 |
2,383 |
67kB |
Cladhaire |
11-03-09 01:54 AM |
|
r121 |
2,701 |
67kB |
Cladhaire |
04-17-09 01:49 AM |
|
r108 |
3,590 |
58kB |
Cladhaire |
10-13-08 02:55 PM |
File Name |
Version |
Size |
Author |
Date |
v4.0.26-release |
252kB |
Cladhaire |
09-15-24 01:34 AM |
|
v4.0.25-release |
252kB |
Cladhaire |
08-19-24 03:26 PM |
|
v4.0.24-release |
252kB |
Cladhaire |
08-18-24 11:03 AM |
|
v4.0.23-release |
251kB |
Cladhaire |
08-17-24 07:29 AM |
|
v4.0.22-release |
251kB |
Cladhaire |
08-13-24 11:12 AM |
|
v4.0.21-release |
251kB |
Cladhaire |
08-13-24 10:06 AM |
|
v4.0.20-release |
251kB |
Cladhaire |
07-26-24 01:09 AM |
|
v4.0.19-release |
251kB |
Cladhaire |
07-25-24 02:34 AM |
|
v4.0.17-release |
251kB |
Cladhaire |
07-24-24 12:31 AM |
|
v4.0.16-release |
252kB |
Cladhaire |
07-23-24 03:35 PM |
|
v4.0.15-release |
252kB |
Cladhaire |
07-23-24 03:33 PM |
|
v4.0.15-release |
251kB |
Cladhaire |
07-23-24 03:31 PM |
|
v4.0.14-release |
252kB |
Cladhaire |
07-23-24 11:13 AM |
|
v3.6.3-release |
236kB |
Cladhaire |
05-08-24 01:10 PM |
|
v3.6.3-release |
236kB |
Cladhaire |
05-08-24 11:44 AM |
|
v3.6.2-release |
236kB |
Cladhaire |
05-08-24 12:28 AM |
|
v3.6.1-release |
236kB |
Cladhaire |
05-02-24 09:50 AM |
|
v3.6.0-release |
235kB |
Cladhaire |
04-29-24 12:32 AM |
|
v3.5.7-release |
234kB |
Cladhaire |
03-21-24 12:45 PM |
|
v3.5.6-release |
234kB |
Cladhaire |
01-17-24 01:13 AM |
|
v3.5.5-release |
234kB |
Cladhaire |
11-09-23 03:25 PM |
|
v3.5.4-release |
234kB |
Cladhaire |
09-08-23 01:08 PM |
|
v3.5.3-release |
234kB |
Cladhaire |
08-30-23 04:05 AM |
|
v3.5.2-release |
235kB |
Cladhaire |
07-12-23 12:33 PM |
|
v3.5.1-release |
234kB |
Cladhaire |
05-03-23 09:47 AM |
|
v3.5.0-release |
234kB |
Cladhaire |
04-01-23 04:55 AM |
|
v3.4.15-release |
234kB |
Cladhaire |
03-22-23 12:35 PM |
|
v3.4.14-release |
234kB |
Cladhaire |
01-25-23 09:26 AM |
|
v3.4.13-release |
234kB |
Cladhaire |
01-21-23 02:39 AM |
|
v3.4.12-release |
234kB |
Cladhaire |
11-29-22 01:55 AM |
|
v3.4.11-release |
234kB |
Cladhaire |
11-28-22 06:32 AM |
|
v3.4.10-release |
234kB |
Cladhaire |
11-06-22 02:25 PM |
|
v3.4.7-release |
233kB |
Cladhaire |
11-02-22 02:28 AM |
|
v3.4.6-release |
233kB |
Cladhaire |
10-27-22 04:08 AM |
|
v3.4.5-release |
233kB |
Cladhaire |
10-26-22 07:55 AM |
|
v3.4.4-release |
232kB |
Cladhaire |
10-26-22 01:05 AM |
|
v3.4.2-release |
233kB |
Cladhaire |
10-25-22 01:18 PM |
|
v3.4.1-release |
232kB |
Cladhaire |
10-25-22 08:52 AM |
|
v3.4.0-release |
233kB |
Cladhaire |
10-25-22 08:47 AM |
|
v3.3.0 |
154kB |
Cladhaire |
09-02-22 06:36 AM |
|
v3.2.1 |
153kB |
Cladhaire |
08-31-22 11:13 AM |
|
v3.2.0 |
151kB |
Cladhaire |
08-21-22 08:26 AM |
|
v3.1.5 |
105kB |
Cladhaire |
08-17-22 11:13 AM |
|
v3.1.4 |
105kB |
Cladhaire |
06-02-22 11:53 AM |
|
v3.1.3 |
105kB |
Cladhaire |
02-22-22 04:40 PM |
|
v3.1.2 |
105kB |
Cladhaire |
11-04-21 01:13 PM |
|
v3.1.1 |
105kB |
Cladhaire |
06-30-21 06:15 AM |
|
v3.1.0 |
105kB |
Cladhaire |
06-01-21 04:05 AM |
Comment Options |
08-27-11, 10:51 PM | |
|
Not sure how I've managed to get along in this game for so long without this. I feel like I've discovered fire.
Thanks. |
|
jmcgrath |
View Public Profile |
Send a private message to jmcgrath |
Find More Posts by jmcgrath |
Add jmcgrath to Your Buddy List |
Cladhaire |
View Public Profile |
Send a private message to Cladhaire |
Find More Posts by Cladhaire |
Add Cladhaire to Your Buddy List |
08-24-11, 08:27 AM | ||||||
|
The two times I have submitted crash reports separately direct to Blizzard via email (not involving Clique) that included the "full crash reports"with addon lists, memory addresses, DLLs and so on, the replies received were slightly modified form letters. Stating, in effect, that "thank you for the report" and "to disable your addons to see if it happens again". As they do to every average, clueless user or otherwise, unless they have an inside track as you do, apparently. So no further time has been wasted in submitting further crashes to them.
Which caused frustration on this end, as reproducible errors under similar circumstances are not fancifully "imagined" by me to be an issue involving a mod (and/or Blizzard code).
Then again, you seemed to accept the qualifier later: "I didn't ask you to crash in raids, ever." Not the best start to a tester-author relationship. Can we start anew?
If I feel up to it later, will do solo testing with this alone as well as the standard raid mod load here to see if can get it to reproduce. May (or may not) be heading down a blank path, however, as the crashes have only happened previously when a member in a party or raid. |
|||||
|
Zidomo |
View Public Profile |
Send a private message to Zidomo |
Find More Posts by Zidomo |
Add Zidomo to Your Buddy List |
08-24-11, 02:52 AM | |
|
Let me try this again, with a bit less frustration.
If you are interested in getting this issue resolved, please attempt to reproduce the issue with only Clique enabled. If you are able to, please supply me with the *entire* crash log, including the stack traces. Please submit the crash report to Blizzard using MY email address ([email protected]). Once I have the crash report, I will get back in contact with them to see if there is a way to resolve the issue. Note: I am not removing my response below because it is still incredibly relevant. It is also written from a very frustrated position and is far more abrasive than it needs to be. My apologies for responding without taking the opportunity to rein in my frustrating.
__________________
"There's only one thing that I know how to do well and I've often been told that you only can do what you know how to do well, and that's be you-- be what you're like-- be like yourself. And so I'm having a wonderful time, but I'd rather be whistling in the dark..." |
|
Cladhaire |
View Public Profile |
Send a private message to Cladhaire |
Find More Posts by Cladhaire |
Add Cladhaire to Your Buddy List |
08-24-11, 02:32 AM | ||||||||
|
You can talk about how much experience you have, but the fact remains that I have been in contact with Blizzard attempting to resolve this issue, but our hands are tied because you seem to think you know better than I do about what this issue is and how it needs to be resolved. You are mistaken.
That's fine. You have to report these to Blizzard, and let me know. I cannot fix the bug because it is not a bug in Clique. I cannot fix the issue because it is not a bug in Clique. I cannot fix the bug because it is not a bug in Clique. I cannot fix the issue because it is not a bug in Clique. The bug exists in the WoW client. That much is so embarrassingly obviously. The most that even them most intelligent addon author can possibly do is attempt to avoid the circumstances that caused the crash to happen in the first place. That is avoiding the symptom, it is not fixing the bug, because the bug is a bug in the WoW client.
And I've asked you to help work with me to provide more information. You seem unwilling to do this. I need the entire crash report, I need you to report the entire crash report to Blizzard and to put your email/my email or some other identifiable string in the text you supply to them so we have a common reference.
I'm bending over backwards trying to help you. I don't need to be lectured by my users, I understand *fully* that this problem affects you, but I've told you every single time that you've reported it that my hands are tied. I've written three books about writing addons for World of Warcraft. I have over 12 million downloads of my addons. I know the code of Clique inside and out, and I am not doing anything that would be considered even slightly 'off-key' or unsavoury. I'm using the API as Blizzard designed it, and in that use the client crashes. I cannot fix a bug in the WoW client, and that is what this is. The best I could *ever* hope to do is help you to avoid the symptom. This is made even more difficult by the fact that you are the only person I have ever report this issue. I think it's a legitimate issue, and the concerns of a single user are important enough for me to spend as much time as I do responding to user requests.. but I can't do things that are beyond my ability as a human being.
__________________
"There's only one thing that I know how to do well and I've often been told that you only can do what you know how to do well, and that's be you-- be what you're like-- be like yourself. And so I'm having a wonderful time, but I'd rather be whistling in the dark..."
Last edited by Cladhaire : 08-24-11 at 02:48 AM.
|
|||||||
|
Cladhaire |
View Public Profile |
Send a private message to Cladhaire |
Find More Posts by Cladhaire |
Add Cladhaire to Your Buddy List |
08-24-11, 02:15 AM | ||||||
|
As it has never happened when Clique's binding configuration isn't active, I know from experience that they aren't interested in issues that may have an addon contributing to it.
Current Addon: Clique Current Addon object: CliqueConfigPage1ButtonOptions In a second crash mentioned in the same report that happened two weeks later in the same circumstances (but with a later retail WoW build), same addon function, but Current Addon: (null), etc.. Sometimes the error report catches & reports Clique, sometimes it doesn't. The Current Addon function and the things being done by me in the UI (_only_ with the Clique binding functions open, in different party/raid circumstances) have been identical in every single crash for the past year.
I still regularly close the spellbook with the "X" when the Clique binding configuration is not active; never, ever a problem or crash.
Since I last crashed in the identical Clique circumstances in January or so of this year (and reported it here), I have been completely avoiding clicking the "X" to close the spellbook when the Clique binding configuration is open at any time. Instead, have been closing it via ESC (Windows) to (unreliably) "work around" the problem. Latest crash here clicking the "X" is when I forgot to do that in the middle of a raid, as noted.
I've long seen full game crashes due to bugs/problems in addon code that affect Blizzard code/bugs. One notable one was with the Pawn addon several years ago (since fixed), among others. If testing a debug version--only when playing solo here--can contribute to a useful code workaround in the next version of Clique, I'm willing to help do that. I will not test crashing in a group situation, but solo, its not a problem. |
|||||
|
Zidomo |
View Public Profile |
Send a private message to Zidomo |
Find More Posts by Zidomo |
Add Zidomo to Your Buddy List |
08-24-11, 01:40 AM | |
|
Further to my prior comments, I've reported this to Blizzard since I've seen no response from you, and they can't do anything without the stack trace, the rest of the crash report. Hopefully you submitted it.
__________________
"There's only one thing that I know how to do well and I've often been told that you only can do what you know how to do well, and that's be you-- be what you're like-- be like yourself. And so I'm having a wonderful time, but I'd rather be whistling in the dark..." |
|
Cladhaire |
View Public Profile |
Send a private message to Cladhaire |
Find More Posts by Cladhaire |
Add Cladhaire to Your Buddy List |
08-21-11, 05:07 AM | ||||
|
If you can reliably (every single time) reproduce this issue, then you are the only one that can help anyone fix it. It is *remotely* possible that there is something I can change in the Clique code to BYPASS the issue, but I cannot fix it, because it is an issue in the WoW client and needs to be fixed by Blizzard. I'm incredibly willing to help, but I cannot reproduce this issue, and it is an issue with the WoW client. I could work with you to add some manner of debugging and tracing to try and see if we can figure things out. I'm sorry you lost data, but that is a result of the game crashing, and I don't have anything to do with that.
__________________
"There's only one thing that I know how to do well and I've often been told that you only can do what you know how to do well, and that's be you-- be what you're like-- be like yourself. And so I'm having a wonderful time, but I'd rather be whistling in the dark..." |
|||
|
Cladhaire |
View Public Profile |
Send a private message to Cladhaire |
Find More Posts by Cladhaire |
Add Cladhaire to Your Buddy List |
08-21-11, 02:53 AM | |
|
Latest full WoW crash attributable to Clique, same circumstances as happened before.
WoW 4.2.0a live, USEnglish client/server, Clique v40200-1.4.0. In a (10-man) raid out of combat. Opened up the spellbook, clicked the Clique binding configuration icon to open the binding frame. Made an adjustment, unfortunately clicked the "X" on the upper right of the spellbook frame to close it and the Clique frame. Full crash: Code:
============================================================================== World of WarCraft: Retail Build (build 14480) Exe: C:\Program Files\World of Warcraft\WoW.exe Time: Aug 20, 2011 2:42:18.468 PM User: (anonymous) Computer: (anonymous) ------------------------------------------------------------------------------ This application has encountered a critical error: ERROR #132 (0x85100084) Fatal exception! Program: C:\Program Files\World of Warcraft\WoW.exe ProcessID: 3864 Exception: 0xC0000005 (ACCESS_VIOLATION) at 001B:00501DD7 The instruction at "0x00501DD7" referenced memory at "0x00000050". The memory could not be "read". WoWBuild: 14480 Version: 4.2.0 Type: WoW Platform: X86 Realm: (anonymous) Local Zone: Beth'tilac's Lair, Firelands Local Player: (anonymous), 0200000000328497, (-4.37298,347.048,76.3501) Total lua memory: 120594KB Current Addon: (null) Current Addon function: SpellBookFrame:Hide Current Addon object: <unnamed> As a result, lost HeadCount2/OuroLoot recording of the two bosses prior. Along with chat logs, combat logs and everything else. If this also happened clicking ESC to close both frames, would have long ago moved to Healbot. Its still the nastiest variety of mod/WoW problem there is; hopefully it can be fixed sometime. |
|
Zidomo |
View Public Profile |
Send a private message to Zidomo |
Find More Posts by Zidomo |
Add Zidomo to Your Buddy List |
08-17-11, 02:18 AM | |
|
I've responded on the Curse ticket. Let me know if you need additional help.
__________________
"There's only one thing that I know how to do well and I've often been told that you only can do what you know how to do well, and that's be you-- be what you're like-- be like yourself. And so I'm having a wonderful time, but I'd rather be whistling in the dark..." |
|
Cladhaire |
View Public Profile |
Send a private message to Cladhaire |
Find More Posts by Cladhaire |
Add Cladhaire to Your Buddy List |
08-17-11, 12:12 AM | |
A Kobold Labourer
Forum posts: 0
File comments: 1
Uploads: 0
|
Clique support for CompactRaid
Posted on CompactRaid's Curse, Clique's CurseForge and WoWInterface, because I'm not sure which of you adds support to what.
Would it be possible for Clique support / CompactRaid support? I know CompactRaid already supports mouseovers, but I've already set up Clique and I prefer Clique's interface for setting up the spells. http://wow.curse.com/downloads/wow-a...mpactraid.aspx http://wow.curse.com/downloads/wow-a...ls/clique.aspx |
|
Yimmeryams |
View Public Profile |
Send a private message to Yimmeryams |
Find More Posts by Yimmeryams |
Add Yimmeryams to Your Buddy List |
08-10-11, 01:06 AM | ||
|
__________________
"There's only one thing that I know how to do well and I've often been told that you only can do what you know how to do well, and that's be you-- be what you're like-- be like yourself. And so I'm having a wonderful time, but I'd rather be whistling in the dark..." |
|
|
Cladhaire |
View Public Profile |
Send a private message to Cladhaire |
Find More Posts by Cladhaire |
Add Cladhaire to Your Buddy List |
08-09-11, 07:08 PM | |
A Kobold Labourer
Forum posts: 0
File comments: 3
Uploads: 0
|
Got one Lua error and disabled the addon for the character that I use clique on, after that i reinstalled clique again but it still wont register on my actual framelist.
Spoke to my friend that have used clique for a long time and she couldn't even think of what was wrong, since the options for LUI and Grid just dissapered. And since it apparently wont work to reistall the addon then I myself are clueless of what that could've happened. So just to clarify the problem, Grind and LUI wont show on my frame blacklist so I can't tick/untick for what clique should work on. Submitting a screenshot so that you can see what I mean. |
|
Iziola |
View Public Profile |
Send a private message to Iziola |
Find More Posts by Iziola |
Add Iziola to Your Buddy List |
08-08-11, 04:09 PM | |
|
Then there is an error occurring somewhere. Please provide a screenshot. Please ensure that Lua Errors are enabled (Interface Options -> Help -> Display Lua Errors). You should be getting an error if something isn't working.
__________________
"There's only one thing that I know how to do well and I've often been told that you only can do what you know how to do well, and that's be you-- be what you're like-- be like yourself. And so I'm having a wonderful time, but I'd rather be whistling in the dark..." |
|
Cladhaire |
View Public Profile |
Send a private message to Cladhaire |
Find More Posts by Cladhaire |
Add Cladhaire to Your Buddy List |
08-08-11, 02:48 PM | |
A Kobold Labourer
Forum posts: 0
File comments: 3
Uploads: 0
|
For starters thanks for the quick reply!
And to get on the framelist, it wont even give me enough options to scroll down anymore, used to be loads there before. Only BossTarget and CompactRaidFrame are the once showing atm. When i did the mousover command it showed me 'GridLayoutHeader1UnitButton1'. And for LUI it said 'oUF_LUI_player'. So it seems to be able to identisy them there but not in the actual addon interface. |
|
Iziola |
View Public Profile |
Send a private message to Iziola |
Find More Posts by Iziola |
Add Iziola to Your Buddy List |