(234Kb)

Compatible with Retail, Classic & TBC

Updated: 03-21-24 12:45 PM

Add Favorite

Install Help

Pictures

File Info

Compatibility:	Plunderstorm (10.2.6) Classic (1.15.0) WOTLK Patch (3.4.3)
Updated:	03-21-24 12:45 PM
Created:	unknown
Downloads:	1,270,557
Favorites:	3,570
MD5:

10.2.6

Clique

Version: v3.5.7-release

by: Cladhaire [More]

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:

default - This set is always active on registered unit frames, unless overridden by another binding-set.
ooc - This set is only active when you are out of combat. Once you begin fighting, these bindings will no longer be active, regardless of what other bind-sets are selected.
friend - This set is only active when you are activating a binding on a friendly unit, i.e. one you can assist.
enemy - This set is only active when you are activating a binding on an enemy unit, i.e. one you can attack.
hovercast - These bindings will be available whenever you are over a unit frame, or a unit in the 3D world.
global - These bindings will be always available. They do not specify a target for the action, so if the action requires a target, you must specify it after performing the binding.
Talent: SpecName - When any talent bind set is selected, that binding will only be active when that talent specialization is active, regardless of other bind sets. A binding can be set for more than one talent spec at a time and it should function correctly.

Clique and dual talent specs
In addition Clique allows you to set up different profiles, and can automatically switch between them when your character changes talent groups. In order to set this up, click the 'Options' button, or navigate to the Clique options section of the Interface Options menu. Here you can create new profiles and change your options to activate different profiles depending on talent spec.

Bug reports:
If you are going to submit a bug report, please include the following information:

What version of Clique you are using (/dump Clique.version)
What unit frames you are using
What specific bindings are not working

Some folks have asked for how they can donate money, and for many years I've enjoyed hearing about how my addons have helped other people enjoy World of Warcraft. If you would like to donate, I'd ask you to make a donation to the Colorectal Cancer Alliance, a worthy organisation that helped my sister immensely from her diagnosis through her final years. If you or a family member suspect you might have something not right in your butt, please have a doctor check it out. Colorectal cancer is one of the most preventable cancers in the world.

Clique
v90005-1.0.1 (2021-04-07)
Full Changelog

Set up packaging for WowI and Curse
Previously Curse stopped generating new files, so that version has
been lagging behind slightly.
Update TOC for 9.0.5
Fix a taint issue relating to the spellbook
This should prevent certain errors that show Clique as being blocked
for showing action buttons and other odd behaviour.
Update TOC for 9.0.2
Fix an issue with nameplates
Fix TOC for 9.0.1 release
Add another backdrop template
Update for v90001 pre-patch
- Fix an issue with backdrop inheritance
- Stop using names to detect frame sub components
Fix issue with talent spec bindings
Shuffle some talent code
Fix issue with talent config
Update compat check to use WOW_PROJECT_ID
Add support for spell ranks
Attempt clean-up for Classic
Fixing a duplicate event registration issue
Update to 8.2
Update TOC for BfA
Fix option panel initialization
Update for 7.3
Don't try to enable nameplates or forbidden objects
Update for 7.2
Add a /clique profile <profileName> command
This makes it possible to change profiles without navigating the GUI.
Ensure we don't try to register nameplates
Update for 7.1
Fire bindings changed on player entering world
Some spec-based bindings are being lost in between instances, this
should help to mitigate that. It's difficult to reproduce without the
right character/instance which I'm not able to reproduce but this should
fix some of those issues.
It will cause Clique to do a slight bit more work when zoning between
instances, but I don't think there are any crucial points where that
happens.
Attempt to resolve the issue with "stuck" bindings
There are some situations in which the mouseover unit can go away, and
we're currently using this to detect if a frame might be obscuring the
current one or if the current frame has been hidden.
I have made this check smarter and it should be better at determining
when to clear the bindings that have been set. If you want to view more
information about when bindings are being clear (or not) you can run the
following in-game:
/run Clique.settings.debugUnitIssue = true
/reload
You can remove these messages later with the reverse:
/run Clique.settings.debugUnitIssue = false
/reload
Trigger bindings changed on P_E_W
Add support for automatically switching profiles on talent change
These different profiles can be configured on the general options
screen.
Update localization
Add support for new talent specializations
This new version works a bit differently than the old one in that the
same spell can be bound to multiple talent sets and it should work
correctly. Basically if a talent bind set is selected then the bind will
only be available when that spec is active, but it is no longer an ONLY
bind set.
Fix an issue with nameplates
Auto-blacklist buttons without RegisterForClicks
The new nameplates inherit from the compact raid frame templates, but
don't have all of the methods needed to work with click-casting, so for
now we'll auto-blacklist all of those frames.
Update TOC
Update TOC for 6.2.0
Update TOC for 6.1.x
Update AceDB3
Updates for WoD
- Handle 1nil change for Region:IsEnabled()
- Update TOC version
Update for 5.4
Enable status icon on compact raid frames
Temporarily fix an issue with unit menus
After 5.2 when Blizzard switched to 'togglemenu', there is a bug with
the dropdown code that requires raid frames to continue using 'menu'
instead in order to work properly. This change should properly use the
correct attribute until this bug has been fixed.
Fixing menu bindings
Updating TOC for 5.2
Make Clique PTR/Live compatible
Reduce the change of tainting with static popups
Update show menu binding
Update TOC for 5.1
Fix option for disabling target of target frame
Fixes 82
Fix bindings for spells needing AOE targeting
The 'stop casting fix' was being applied to global bindings in addition
to hovercast bindings, which was breaking spells like Hurricane and
Blizzard. This should resolve those issues.
Don't apply wrong-spec bindings
Previously, if you were in your primary spec and you had a spell that
was bound to secondary spec only, the binding would still be active
(although it would not do anything). Simple test:
1. Bind 'moonfire' to 1 on hovercast,secspec
2. Verify it works
3. Change to primary spec
4. You will be unable to use your '1' normal binding
Update TOC correctly
Update for UIPanelButtonTemplate2 rename
Update for talent group changes
Updated TOC
BindConfig template fixes for mop
Fix targeting with the stop casting fix
Add an option to call /stopcasting before each spellcast
Update .toc for 4.3.0
Guard for corrupt saved variables
Add more unit tests for attributes
Add binding-sets for primary/secondary talent spec
Make the bindings list slightly more stable
Fix the setting/clearing of ooc bindings
Fix whitespace
Fix some whitespace/comments
Added a unit test framework for attributes
Enable mousewheel events as well as clicks
This was previously only working on frames that registered using the
RegisterFrame or ClickCastFrames mechanism.
Updating TOC for 4.2
Add missing Localization.ruRU.lua file
Revert "Use 'secure' registration for RegisterFrame"
Clarify license as All rights reserved
Use 'secure' registration for RegisterFrame
Update TOC to 40100
Fix support for compact party frames
Attempt to fix the dangling bindings issue
If the player is over a frame that has key bindings active and that
frame is hidden or obscured then those bindings will remain active until
another Clique-enabled frame is moused over. This fix uses the attribute
driver template to clear this dangling button when the player no longer
has a 'mouseover' unit.
This change could potentially cause problems for small corner cases
where non-unit-frames are enabled for Clique casting, but I do not
currently know of any uses where this is the case.
Add ruRU localization thanks to StingerSoft
Add support for the 'backspace' key, possibly
Fix a bug with arena frames integration
Fix group header template click applications
There was a problem with some frames (Pitbull party frames, for example)
that was causing out of combat bindings to not properly apply. This was
due to a weird behaviour of the secure environment system.
Update AddonCore to re-include Printf
Fix a bug that was causing some bindings to fail
Add the blacklist code back in
Revamp of attribute calculation/setting
The logic seems to be a bit more straightforward and it seems that the
ooc/friend/enemy layering is working properly. The major changes are:
* Clique will only calculate new attributes when you change bindings
* Clique will apply the attributes when bindings change
* If you have ooc bindings, then they will swap on enter/leave combat
* Otherwise, they will not change, so there's no overhead from that
out-of-combat bindings should now correctly be applied over any other
type of binding with the same key. If this isn't the case, please report
it to me.
Add an addon:Defer() function for deferral
This function will defer the execution of a method or function until the
player as exited combat.
Fix a bug in FireMessage argument checking
Make emergency debug mode more informative
Add support for buff/debuff on raid frames
Adding support for CompactParty pet frames
Add a pet header to the header test code
Fix hovercast/default combination to work properly
Move options panels around to be clearer
Allow for string = true in localization files
Fix a typo in blizzard frame options
Fix a bug in the blacklist editor due to prior change
Fix some issues with registering group-header-based frames
This should fix the reported issues with 'AnyUp' and 'AnyDown'
registration not happening properly on those frames.
Convert strings to frames
Try to run RegisterForCLicks on all frames during a full update
Fix modified special keys, like dash and backslash
Revert "Bind spells by spell id, see if this resolves the Blizzard issues"
Allow 'Backslash' to be used as a binding key
Fix enemy/friend bindings when used with default/hovercast.
Thanks to JTrent82 for the thorough bug report that helped me track this
one down.
Add friend/enemy attributes to remote snippet as well
Bind spells by spell id, see if this resolves the Blizzard issues
Update localization (added zhCN and zhTW)
Add a selection dropdown to the "options" button
Fix a bug that was causing edited macros to lose their binding
Add a basic test suite
Fix several bugs with mouse-button-based bindings
Add an addon-wide index/newindex debug mode
Hide UI panel when spellbook is hidden and both are open
Fix another corner case where escape could get eaten
Fix the issue that was causing escape to be eaten
Disable button-based hovercast/global bindings on unit frames
Fix the 'Select None' button in the frame blacklist editor
Remove debug message
Ensure onenter/onleave attributes don't get 'stuck'.
Only register clicks on enabled, non-blacklisted frames
Some comment and text updates
Fix bindings with non-latin keys, such as ö
Enabled frame unregistration
Addons that are registering using ClickCastFrames should run
ClickCastFrames[frame] = nil or ClickCastFrames[frame] = false.
Addons that are using the group header, and are registering using
the secure snippet method should do the following:
local header = self:GetFrameref("clickcast_header")
header:SetAttribute("clickcast_button", button)
header:RunAttribute("clickcast_unregister")
This code expect to be run on the header, but needs access to the
button. This can probably be passed into your header via a frame
reference, i.e:
MyGroupHeader:SetFrameRef("foo", MyGroupHeaderUnitButton1)
MyGroupHeader:Execute[[
local button = self:GetFrameRef("foo");
local header = self:GetFrameRef("clickcast_header")
header:SetAttribute("clickcast_button", button)
header:RunAttribute("clickcast_unregister")
]]
Hide the bindAlert if the spellbook frame isn't open
Fix an issue where backslash could not be bound
Add a notice when binding mode is active
Fix a critical bug, thanks for the reports
Try to guard all instances of bad input for listing, so user can fix their own problems
Change terminology from click-set to binding-set
Fix an issue where setting a new profile did not change profile on next reload
Allow the dash key to be bound without errors
Don't update the config if it is not visible
Add headers to each file to make viewing source a bit easier
Fix blizzard frames settings not saving
Throttle mousewheel bindings on the spellbook to prevent duplicates
Clear focus from editbox when mousing over binding button
Replace the 'Change binding' menu with 'Edit macro' for macros
Merge branch 'editmacro'
Ensure deletion actually deletes correct binding
Allow editing of macros, both binding and text
Fix error with registration queue
Do not allow AddBinding/DeleteBinding while in combat
Add 'hovercast' click set, to replace the old 'global'. New 'global' is truly global, with no target specified. These binding sets are mutually exclusive
Queue any frame registrations during combat until we leave combat
Change any stray instances of getglobal to _G
Updated .pkgmeta to properly include tools used
Use Ace3 for database management and associated cleanup
* Fix an issue where a macro could be created without a binding
* Widen profile dropdowns
Fix a bug in database upgrade/initialization
Hide the Clique spell tab when appropriate
Ensure attributed are updated when settings change.
This fixes a bug where changign a binding via the menu did not update
the actual bindings that were set on frames
Give out-of-combat clicks priority
This does not fix the bug arising from conflicts between 'ooc' and
'friend' clicks. That will come in a future update.
Added name-based frame blacklist and interface options panel
Hide spellbook/clique when opening options panel
Add an 'ooh-shiny' box when spellbook/clique are both open
Remove addon initialised message
Change window opening so it works on high-ui-scale screens
Force a saved variables reset to fix the 'blizzframes' issue
Remove database upgrade code for V3->V4.
Fixed an issue preventing you from using mousewheel for macro binds
Fix the issue with nil 'blizzframes'
Added options to limit Blizzard frame integration
Remove stale readme file
Remove HeaderTest code from TOC
Fix a number of stray globals
Fix a bug where options panel was not initialized properly
Update credits for icon images
Update icons to the contest winning icons by d87
Fix binding configuration to allow for delete and change binding
Add an option to trigger 'combat' changed based on party members
This option, when enabled, will do a bit more work trying to check for
when your party or raid members enter combat. When this happen, your
click set will be changed and your 'ooc' clicks will be removed, even
though you aren't strictly in combat. This feature is very experimental,
and should be enabled with care.
Update BindConfig when changing profiles
Add options panel, spec-based profile swaps and profile support
Fix dialog so position is not saved
Formalize database layout, making way for full database profiles
Add spellbook tab to toggle Clique UI
Allow global bindings to also use friend/enemy
Sort click-sets when displaying in spell info
Added support for harm/help click-sets
Add support for 'global' clickset, as global bindings
Add support for the 'ooc' click set
Add dropdown menu toggles for basic click-sets
Use dark-background version of Jesse Talks's mouse
Added click-set indicator to binding config
Remove frames that are erroring, and delay arena frame registration
Change Blizzard frame registration to use names instead of frames
Added possible Clique portrait icon with CREDITS file
Support cleaning of attributes and add DeleteBinding() function
Add macro creation and bind deletion
Implemented macros, srsly.
Make the dialog mouse-enabled so it doesn't bleed down a level
Implemented target unit/show menu actions and binding captures
Rename files to remove over-namespacing
Add options panel, remove page3
Reorganize files to allow for options dialog
Abstract out frame registration
Add initial Blizzard frames integration
Continued revmap of Clique user interface
Add comments to Clique.lua about click-set priorities
Run xmllint on Clique.xml
Fix page2 and navigation between pages
Make columns clickable to sort by action text or binding
Massive advancements towards working version:
* Fixed in-combat registration
* Fixed out-of-combat registration
* Adding bindings works properly
* Attributes are updated properly after changes to bindings
* Altered options screen to display
* Changed display of BUTTONX and BACKSPACE, etc.
Working group header registration and attribute generation system
Working proof-of-concept implementation of in-combat registration
Add test function, fix spellbook binding, add comments
Add code for ClickCastFrames and group header registration
Initial commit of Clique revamp
Added an option to trigger spellcast on the down portion of a click
This option can be found in the Clique UI, under the 'options' panel. When this option is active, any buttons that register for click-casting will be registered for 'AnyDown', which will cause spells to trigger on the down portion of the click. By default, Clique continues to function as usual, triggering spellcasts on the up portion of a click.
Fix click-casting for Target of Target frame, and add click casting for focus-target and boss frames
Removing leftover debug messages
Fix for out-of-combat helpful spell bug
TOC Update for 3.3
Fix a bug that was causing helpful/harmful bindings to override out-of-combat bindings
Fix a display issue for binding entries
Fix the sorting of higher button options
Added support for Steelseries MMO Gaming Mouse, with a few caveats and setup requirements:
* You must open the Steelseries mouse configuration screen and set each button (except Left/Right/Middle/Button4/Button5) to "Disable/Clear". This ensures they don't try to send WoW commands, which it does by sending keyboard keys (like M to open the map).
* You should disable "Enable in-game mode".
* In-game you must open interface options, and go to the mouse configuration tab. There you need to select "Detect WoW Mouse". If it doesn't work, you'll need to play with things a bit.
Then you should be able to use the mouse natively, taking advantage of all buttons in Clique and WoW in general (as buttons, not as keys).
Added support for extra mouse buttons
Fixing a localization issue when applying clicks in combat
Interface version update
Allow Clique to make changed in combat.. using frame:CanChangeAttribute()
Added preliminary support for Blizzard's arena frames
Fixed the code used to detect talent changes, should work correctly now
Fixed an error that could occur when mousing over empty slots in the spellbook
Updated Clique to use ACTIVE_TALENT_GROUP_CHANGED
* Fix profile switching system so it stores the options in 'char' rather than 'profile'.. duur
* Removed old "MAX" button, since the game no longer encourages downranking.
* Added an "options" button that allows you to enable/disable profile switching when changing talent specs
* Fixed a taint issue due to using UIFrameFlash
* Fix an error that caused custom pet actions to have a display error
* The Clique configuration window will now properly be visible on the pet tab
Make ruRU locale only apply when the user is using a ruRU client
Added ruRU localization courtesy of gzukka
* Added localization for esES and esMX thanks to iflores23
* Fix an issue with the new profile dialog when clicking the "Accept" button
Fixed an error when mousing over an empty spellbook slot
Removed conditional WoTLK code
* Fixed deprecated use of 'this' in a number of places
* Fixed an issue where the icon selection screen gave an error
* Added a tooltip to the dropdown selector button and the Clique tab button
* Fixed the toggling behavior of Clique when entering combat
* Altered frame levels of the Clique UI so the windows should be usable in all situations
* Double-clicking an entry will edit it
* Rephrased "Stop Casting" to "Cancel Pending Spellcast", since it reflects what the option does
Only specify a spell rank when the "Show all spell ranks" button is selected
Make the spellbook tab/button disappear when we're on the glyph screen
Update table of contents
Added reference to IsWrathBuild()
Added code to fix the scroll and dropdown frames in WoTLK
Fixed an issue with mousing over a spellbook button in WoTLK
Fixed a number of issues with the edit UI
Remove a stray SetMultiline(true)
Make the one-line argument boxes not accept the enter character
* Added wowi:dirname so zips are generated properly
* Fixed tooltip bindings so there are no more duplicates
* Added a /clique showbindings command that will show a draggable window that shows the current clique bindings. This window will not update when your bindings change and currently doesn't retain its position on-screen.
* Removed old database upgrading code
* Added version field to table of contents
* Updated .toc
* Fixed an issue relating to Polymorph (Rank 1: Pig) and the way the rank text was changed. The system should now work for any ranks, numeric or not.
* Renamed the "Options" button to "Frames"
Added COPYING and LICENSE.
* .toc update
* Updated to Dongle-1.1
* Currently in patch 2.2 Blizzard changed the unit attribute resolution. As a result, a unit attribute of "nil" is different from a unit attribute that has never been set. This release works around this issue by only setting the attribute if you've set it in your configuration.
* If you set the "unit" argument for a given custom type, and then clear it, you will need to reload your UI in order to get teh change applied. This should not affect the average user in any way.
* Update to fix issues with TargetUnit and other attributes
* .TOC update
* Fix for the 2.2 issue with odd cast targets
* Updated localisations and altered the .toc file to ensure they load properly
* Update to Dongle-1.0-r871 to fix the profile issue
* .toc update for 2.1.0
* Guard the sv conversion code to prevent an error
* Updating to Dongle-1.0-r863
* Updated to Dongle-1.0-r859
* Base the options title off Clique.rev, which is pulled from Clique.luq
* Removed a number of debug procedures
* Changed the upgrade procedure to be more rigid, based on revision number
* Fixing issue 44, with PROFILE_RESET localisation
* Updated localisation for deDE and pulled out the custom help and labels.
* Updated the logic for rank parsing. Should be more robust and work with other locales.
* Fixed logic so you can assign clicks on PTR
* Updated to Dongle-r849
* Menu no longer requires an arg, so remove that from the options code.
* Updating to Dongle-r315 to fix an issue with logout errors
* Added error checking to the macro type
* tostring() on entry.arg2
* Trying to fix a clique macro issue
* Attempt to fix an issue with numeric macro indices
* Fixed an issue where macros would fail if they had no text, and no index.
* Fix to sv conversion code
* Dongle-1.0
* Due to changes in Dongle, added a script to convert savedvariables, to retain profiles
* Corrected locale string in frFR (closes issue 28)
* Tooltip lines are only added when we're mousing over a frame.
* Added an option for /clique tooltip, which toggles the listing of clique-bindings in the unit tooltips
* Initial work on tooltip listing of bindings
* When a user learns a new spell tab, the Clique button will reposition accordingly.
* Updated to Dongle-Beta1
* Added support for changing profiles on commandline.
* Updated to use Dongle-Beta1
Resolved an issue where custom edited macros were not saving harm/help buttons properly.
Added a small debug function for troubleshooting that can be activated using /clique debug.
Fixed a stray character
* Resolved an issue where helpful and out-of-combat clicks could conflict, with the helpful click taking prescendence.
Removed a stray "frame" argument in PLAYER_REGEN_ENABLED() that was causing clicks to not be set properly. Thanks [Ammo]!!!
Fixed an issue where clicks weren't applying after the MAX or EDIT buttons were used
Updated to Dongle-Beta0. Updated .toc file for 2.0.3.
Updated to Dongle-Beta0
Fixed a typo
Added version checks and warnings for Dongle
Removed clique "special" mode
Fixed a typo, appears to have resolved any clickset issues we've had
Updated to work with Dongle-Beta0, at least in spirit
* Updated to remove some stray globals from Copy/Paste of Blizzard code.
* Urgent update to Dongle-0.5.1-Alpha
* Fixed an issue where frames were registering too early
* Fixed an issue where framed wouldn't unregister properly if deselected
* Dongle-0.5.0-Alpha
* Cleaned up a TON of attribute nastiness, which appears to have resolved any outstanding issues.
* Trying to debug the ooc issue.
* Updated to use new Dongle events for database/profiles
* Fixed an issue where spells were not being masked properly due to 1 ~= "1"
* Added helpful clicks to the masking process, so they are applied ooc.
* Removed random test code
* Fix for custom macros, which wouldn't work after editing
* Updated to Dongle-0.4.2-Alpha
* Fixed an issue with profile changes due to empty blacklist
* Update to the clickset functionality to improve the logic and speed. Should greatly improve loadtimes when large raid mods (RDX) are loaded
* Fixed an issue where attributes were being deleted on blacklisted frames
* Updated to Dongle-0.3.1-Alpha
* Resolved another outstanding issue with out-of-combat clicks
* Updated to Dongle-0.3.0-Alpha
Clique:
* Change API to reflect changes to Dongle
* Resolved some outstanding issues with click priority, required signifgant changes
* Out-of-combat clicks should now have the highest priority, followed by harm/help, followed by default
* Resolved an issue with "Click Button"
* Identified an issue with the left click binding not working across reloads on the default blizzard raid frames. Do not have a fix for this yet, waiting on Blizzard
* Fixed an issue where the blacklist was not properly being applied. Blacklisted frames will no longer have attributes applied to them.
Clique:
* Fixed icon issues, all non-set icons should now properly use the questionmark
* Added custom radio buttons, courtesy Beladona
Clique:
* Moved some localisation around
* Added an edit box for macrotext when making a custom macro
* Removed outdated Print() function
* Added a "menu" action which will show the unit menu, if stored in the frame.menu variable
* Updated to Dongle-0.2.2-Alpha to fix a potential issue with missing libraries
* Fixed an issue with the new profile static pop-up, where clicking the "Accept" button would cause an error
* Updated to Dongle-0.2.1-Alpha
* Fixed an issue where the based actions would not display properly, and would error in the UI
* Fixed a typo when leaving combat
* Added some separation to the potential bug in CliqueOptions.lua
Clique:
* Too many updates to list
* Added a profile window where you can change/set profiles
* Added an options window where you can disable click-casting for named frames
Clique: Some basic change to the profile system
Clique: Changed line-ending bits, just to be done with it
Clique: Removed truncating of profile names, and re-anchored. Trying to get the nested delete working properly
Clique: Initial commit from old svn
Initial directory structure.

Beta Files (8)

File Name	Version	Hits	Size	Author	Date
beta_Clique-v90001-0.1.0-beta.zip	v90001-0.1.0-beta	3,686	103kB	Cladhaire	08-16-20 12:47 PM
beta_Clique-v40000-1.2.7-7e91cea.zip	v40000-1.2.7-7e91cea	2,931	79kB	Cladhaire	10-16-10 10:31 AM
beta_Clique-2.0.0-abfbb36.zip	2.0.0-abfbb36	2,410	43kB	Cladhaire	10-11-10 04:34 PM
beta_Clique-r129.zip	r129	2,800	67kB	Cladhaire	11-14-09 11:55 AM
beta_Clique-r125.zip	r125	2,474	67kB	Cladhaire	11-14-09 11:46 AM
beta_Clique-r127.zip	r127	2,383	67kB	Cladhaire	11-03-09 01:54 AM
beta_Clique-r121.zip	r121	2,701	67kB	Cladhaire	04-17-09 01:49 AM
beta_Clique-r108.zip	r108	3,590	58kB	Cladhaire	10-13-08 02:55 PM

Archived Files (39)

File Name	Version	Size	Author	Date
Clique	v3.5.6-release	234kB	Cladhaire	01-17-24 01:13 AM
Clique	v3.5.5-release	234kB	Cladhaire	11-09-23 03:25 PM
Clique	v3.5.4-release	234kB	Cladhaire	09-08-23 01:08 PM
Clique	v3.5.3-release	234kB	Cladhaire	08-30-23 04:05 AM
Clique	v3.5.2-release	235kB	Cladhaire	07-12-23 12:33 PM
Clique	v3.5.1-release	234kB	Cladhaire	05-03-23 09:47 AM
Clique	v3.5.0-release	234kB	Cladhaire	04-01-23 04:55 AM
Clique	v3.4.15-release	234kB	Cladhaire	03-22-23 12:35 PM
Clique	v3.4.14-release	234kB	Cladhaire	01-25-23 09:26 AM
Clique	v3.4.13-release	234kB	Cladhaire	01-21-23 02:39 AM
Clique	v3.4.12-release	234kB	Cladhaire	11-29-22 01:55 AM
Clique	v3.4.11-release	234kB	Cladhaire	11-28-22 06:32 AM
Clique	v3.4.10-release	234kB	Cladhaire	11-06-22 02:25 PM
Clique	v3.4.7-release	233kB	Cladhaire	11-02-22 02:28 AM
Clique	v3.4.6-release	233kB	Cladhaire	10-27-22 04:08 AM
Clique	v3.4.5-release	233kB	Cladhaire	10-26-22 07:55 AM
Clique	v3.4.4-release	232kB	Cladhaire	10-26-22 01:05 AM
Clique	v3.4.2-release	233kB	Cladhaire	10-25-22 01:18 PM
Clique	v3.4.1-release	232kB	Cladhaire	10-25-22 08:52 AM
Clique	v3.4.0-release	233kB	Cladhaire	10-25-22 08:47 AM
Clique	v3.3.0	154kB	Cladhaire	09-02-22 06:36 AM
Clique	v3.2.1	153kB	Cladhaire	08-31-22 11:13 AM
Clique	v3.2.0	151kB	Cladhaire	08-21-22 08:26 AM
Clique	v3.1.5	105kB	Cladhaire	08-17-22 11:13 AM
Clique	v3.1.4	105kB	Cladhaire	06-02-22 11:53 AM
Clique	v3.1.3	105kB	Cladhaire	02-22-22 04:40 PM
Clique	v3.1.2	105kB	Cladhaire	11-04-21 01:13 PM
Clique	v3.1.1	105kB	Cladhaire	06-30-21 06:15 AM
Clique	v3.1.0	105kB	Cladhaire	06-01-21 04:05 AM
Clique	v3.0.2	104kB	Cladhaire	05-30-21 02:03 AM
Clique	v3.0.1	102kB	Cladhaire	05-15-21 01:46 AM
Clique	v3.0.1	102kB	Cladhaire	05-15-21 01:43 AM
Clique	v3.0.0	102kB	Cladhaire	05-15-21 01:39 AM
Clique	v90005-2.0.2	102kB	Cladhaire	04-08-21 09:36 AM
Clique	v90005-2.0.2-beta	102kB	Cladhaire	04-08-21 09:30 AM
Clique	v90005-1.0.1	112kB	Cladhaire	04-07-21 12:13 AM
Clique	v90005-1.0.0	102kB	Cladhaire	04-07-21 12:03 AM
Clique	v90005-1.0.0	103kB	Cladhaire	03-12-21 11:07 AM
Clique	v90002-1.1.0	103kB	Cladhaire	02-21-21 05:33 AM

Comment Options

Page 61 of 220

08-24-11, 08:27 AM

Zidomo

A Cliff Giant

Forum posts: 76

File comments: 1046

Uploads: 0

Originally posted by Cladhaire
I am sorry, I normally don't like to muscle around, but you are just flat out wrong.

Whatever.

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.

Originally posted by Cladhaire
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.

Wrong. The "entire crash report"s are 40-60KB in size each, which will not fit in the comments here. So I submitted here only the most relevant parts of them. Up till now, you haven't asked for them, just denied there was anything happening with Clique being the trigger cause.

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).

Originally posted by Cladhaire
You're completely unwilling to open the client and purposely crash your client in controlled circumstances to provide the information that *ANYONE* would need to fix this issue? That's patently absurd.

Huh? I take it you missed the qualifiers at the end of the sentence: "I'll test anything...except things that cause crashes and/or perma-freezes in a group or logon situation" (make that logon in a group situation). Is it really "patently absurd" to let your guild raid sit around for 10+ minutes while you relog and/or reboot your PC after a crash?

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?

Originally posted by Cladhaire
Pawn did not fix the issue. Pawn avoided the symptom. Pawn could not fix a bug in the WoW client. The terminology is incredibly important, because it underscores that the addon author, or user who is able to reproduce the issue needs to work with Blizzard to fix the actual bug.

Fine; I didn't state that the issue was a fixed bug within Pawn. Brought it up just as another example of a mod triggering a crash, but one that was later resolved/avoided, whether through Blizzard code or otherwise.

Originally posted by Cladhaire
I need you to provide me with the ENTIRE crash report (feel free to email it or attach it) in an absolutely minimal test case, i.e. Clique as the only addon. If for some reason you can't reproduce it with only Clique enabled, it would be useful to determine if there's another addon that causes the magic mix of destruction.

Cool, will email all the crashes involving the mod since it first happened last October. As noted previously, each one is too large to post here.

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.

08-24-11, 02:52 AM
Cladhaire Salad! Forum posts: 1935 File comments: 4939 Uploads: 19	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..."

08-24-11, 02:32 AM

Cladhaire

Salad!

Forum posts: 1935

File comments: 4939

Uploads: 19

Originally posted by Zidomo
No, of course I didn't waste the time reporting it to them. The _only_ time this particular issue has ever happened (since I first reported it here last October after WoW 4.0.1 was released) is when trying to close the spellbook frame (via the "X" icon) when the Clique binding configuration is active.

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.Nope.

I am sorry, I normally don't like to muscle around, but you are just flat out wrong. You are absolutely right that the average WoW developer is not going to pay much attention to a bug report that is filed that involves an addon, however the report you JUST had does not include an addon in any way. It is a bug in the client. Also, if you report the issue to them, it's in their system and when I am in contact with the UI developers, they can refer to it.

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.

When I first reported this issue last October (and times since then), the trigger was the identical Current Addon function: SpellBookFrame:Hide. However in that first report I filed here, the following surrounded that:
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..

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.

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.

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.

A problem with the WoW client (perhaps) helped along by the way Clique affects the spellbook frame when its binding configuration is active.

I still regularly close the spellbook with the "X" when the Clique binding configuration is not active; never, ever a problem or crash.

I'd love to crash reliably in raids to help you debug, but that goes beyond what I'm willing to do. I'll test anything...except things that cause crashes and/or perma-freezes in a group or logon situation.

You're completely unwilling to open the client and purposely crash your client in controlled circumstances to provide the information that *ANYONE* would need to fix this issue? That's patently absurd.

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.

Actually, Clique is the contributing addon trigger of the crashes. Whether a trigger of a bug in the Blizzard code or otherwise.

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.

Pawn did not fix the issue. Pawn avoided the symptom. Pawn could not fix a bug in the WoW client. The terminology is incredibly important, because it underscores that the addon author, or user who is able to reproduce the issue needs to work with Blizzard to fix the actual bug. Otherwise another addon author and addon user coming down the line is going to run into *exactly* the same issue with even more obfuscated path.

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. [/b]

I didn't ask you to crash in raids, ever. That would be absurd. I need you to provide me with the ENTIRE crash report (feel free to email it or attach it) in an absolutely minimal test case, i.e. Clique as the only addon. If for some reason you can't reproduce it with only Clique enabled, it would be useful to determine if there's another addon that causes the magic mix of destruction. If you choose not to submit this to Blizzard, I'll do it myself and work with them to get the issue as resolved as possible.

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.

08-24-11, 02:15 AM

Zidomo

A Cliff Giant

Forum posts: 76

File comments: 1046

Uploads: 0

Originally posted by Cladhaire
Okay, did you report this to Blizzard? Did your provide your email address so they can contact you to help resolve the issue if they have further questions?

No, of course I didn't waste the time reporting it to them. The _only_ time this particular issue has ever happened (since I first reported it here last October after WoW 4.0.1 was released) is when trying to close the spellbook frame (via the "X" icon) when the Clique binding configuration is active.

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.

Originally posted by Cladhaire
The crash log you are showings seems to be quite clear about the fact than an addon is not responsible for the memory access violation; there is no current addon listed.

Nope.When I first reported this issue last October (and times since then), the trigger was the identical Current Addon function: SpellBookFrame:Hide. However in that first report I filed here, the following surrounded that:
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.

Originally posted by Cladhaire
I must reiterate again, I am unclear on how you expect me to fix this issue. You are getting a full WoW crash. This indicates a problem with the WoW client that needs to be addressed by Blizzard.

Originally posted by Cladhaire
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'd love to crash reliably in raids to help you debug, but that goes beyond what I'm willing to do. I'll test anything...except things that cause crashes and/or perma-freezes in a group or logon situation.

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.

Originally posted by Cladhaire
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.

Actually, Clique is the contributing addon trigger of the crashes. Whether a trigger of a bug in the Blizzard code or otherwise.

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.

08-24-11, 01:40 AM
Cladhaire Salad! Forum posts: 1935 File comments: 4939 Uploads: 19	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..."

08-21-11, 05:07 AM

Cladhaire

Salad!

Forum posts: 1935

File comments: 4939

Uploads: 19

Originally posted by Zidomo
Latest full WoW crash attributable to Clique, same circumstances as happened before.

Okay, did you report this to Blizzard? Did your provide your email address so they can contact you to help resolve the issue if they have further questions?

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:

I continue to be unable to reproduce this issue.

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>

Since the last crash some months ago reported here and no code changes to resolve it have been closing the Clique frame via ESC. But forgot to do that this time in the middle of a raid and the crash happened.

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.

I must reiterate again, I am unclear on how you expect me to fix this issue. You are getting a full WoW crash. This indicates a problem with the WoW client that needs to be addressed by Blizzard. The crash log you are showings seems to be quite clear about the fact than an addon is not responsible for the memory access violation; there is no current addon listed.

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.

08-21-11, 02:53 AM
Zidomo A Cliff Giant Forum posts: 76 File comments: 1046 Uploads: 0	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> Since the last crash some months ago reported here and no code changes to resolve it have been closing the Clique frame via ESC. But forgot to do that this time in the middle of a raid and the crash happened. 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.

08-17-11, 02:18 AM
Cladhaire Salad! Forum posts: 1935 File comments: 4939 Uploads: 19	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..."

08-17-11, 12:12 AM
Yimmeryams 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

08-10-11, 01:06 AM

Cladhaire

Salad!

Forum posts: 1935

File comments: 4939

Uploads: 19

Originally posted by Iziola
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.

Scroll down, as I said in the first post. There is clearly a scrollbar visible on the right-hand side. The reason the list is not completely filling the window is because Blizzard changed the size of their options pane, but the list is still all there..

08-09-11, 07:08 PM
Iziola 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.

08-08-11, 04:09 PM
Cladhaire Salad! Forum posts: 1935 File comments: 4939 Uploads: 19	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..."

08-08-11, 02:48 PM
Iziola 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.

08-08-11, 02:30 PM
Cladhaire Salad! Forum posts: 1935 File comments: 4939 Uploads: 19	Have you scrolled down? Have you ensured that the frames registered have names? /dump GetMouseFocus():GetName() Do that when your mouse is over one of the frames. If it has a name, it will be printed to the chat frame. If not, then Clique can't show it in the list. __________________ "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..."

08-08-11, 01:43 PM
Iziola A Kobold Labourer Forum posts: 0 File comments: 3 Uploads: 0	Problems with framelist. Hello, I seem to be having a framlist problem as my Clique wont show either Grid or LUI on my framelists, so can't enable/disable them. It works perfectly fine for one of my friends that uses the same addon set-up as I do. The Clique vesrion that im currently using is: v40200-1.4.0. And I've tried to reinstall with removing all my old content for both Clique and Grid but it haven't changed a thing as far as I can see. Thanks for your help beforehand //Iziola

Page 61 of 220

Category Jump: