Quantcast
Download
(29 MB)
Download
Updated: 10-27-16 02:58 PM
Pictures
File Info
Compatibility:
Return to Karazhan (7.1.5)
Legion (7.0.3)
Warlords of Draenor (6.0.3)
Warlords of Draenor Pre-Patch (6.0.2)
Updated:10-27-16 02:58 PM
Created:unknown
Downloads:5,422,473
Favorites:7,723
MD5:
7.1.5

LightHeaded  Popular! (More than 5000 hits)

Version: v70100-1.0.0-2016-10-26
by: Cladhaire [More]

The last date of comment parsing is now part of the addon's filename.

Includes over 166,198 comments for more than 15,560 quests


LightHeaded is a very simple addon that displays quest information and comments from http://www.wowhead.com in game, eliminating the need to Alt-Tab when you get stuck on quest. This addon was inspired by qcomments and wowhead_quests, which both serve a similar purpose. Data is only loaded when you first request it, so you can be sure you're not using more memory than you need to.

I HIGHLY suggest using this addon with TomTom, another one of my addons (http://www.wowinterface.com/download...32-TomTom.html ). This allows you to simply click any coordinate in LightHeaded to add it to your map as a waypoint.

The following slash commands are valid:
  • /lh attach - Attaches the frame to the quest log
  • /lh detach - Detaches the frame, allows you to resize and move it
  • /lh sound - Toggles the open/close sound
  • /lh page - Toggles showing all comments on one page, or with multiple pages
  • /lh bgalpha <0.0-1.0> - Changes the alpha of the LH window background textures, so you can see the world.
  • /lh debug - Enables or disabled debug messages when loading quest databases
  • /lh config - Opens the LightHeaded configuration window
  • /lh autodetails - Toggle automatic opening of the Lightheaded window when clicking a quest in the objective tracker

LightHeaded now includes the English descriptions and introductory text for most of the quests in the game. This is disabled by default, but can be enabled for those players that are not playing in their native locale.

LightHeaded supports sending coordinates to TomTom, MapNotes, Cartographer2 and Cartographer3.

IMPORTANT: Addon authors that wish to use this API and data should
include the wowhead logo in the frame that displays this information.
They are kind enough to let me continue parsing their database, and we
owe them at least that much. Thank you.

Thanks for using my addons!

Donations:
Some people have asked, so here is a way to send me donations:

ommit ddba7c19eaca80dc207b7bccfd9f8c096d991aed
Author: Jim Whitehead <[email protected]>
Date: Thu Jan 12 21:23:29 2017 +0100

Add new parse, update integration, update toc.

Thanks to lunarwtr for the fixes

commit 547b33546eb69dccb662beffda2625d74bf11b74
Author: Jim Whitehead <[email protected]>
Date: Thu Oct 27 22:39:13 2016 +0200

Update for 7.1

commit ea5dd596d578663a34044137a34b04b42ff1a4ac
Author: Jim Whitehead <[email protected]>
Date: Wed Sep 7 15:35:26 2016 +0200

Disable auto-popup on SelectQuestLogEntry

commit c3e67123f3233e8e0abd1eb74562f74b1e005209
Author: Jim Whitehead <[email protected]>
Date: Mon Sep 5 14:54:46 2016 +0200

Update TOC for 70000

commit 14d8721ebb51a801b04f4bd7229a57ec5470412e
Author: Jim Whitehead <[email protected]>
Date: Mon Sep 5 14:52:45 2016 +0200

Update for new parsing script

Thanks to lunarwtr we're able to parse again, since I didn't have time
to fix the previous parser. This required some changes to the addon, but
this should get things back up and working.

commit f4a0f7d143c67eb1768662ca73073b103e9e861d
Author: Jim Whitehead <[email protected]>
Date: Sat Jan 31 15:35:53 2015 +0100

Remove dead code

commit 61d0d2ab136d5f79be4edc62e6ae3cbc2964431c
Author: Jim Whitehead <[email protected]>
Date: Sat Jan 31 15:27:56 2015 +0100

Fix LH waypoint set integration

- We now are able to properly reverse WowHead mapFileIds to the in-game
areaIds, so waypoints should be set in the correct zone.
- We don't know how to set a waypoint in an instanced zone, so we just
put those in the current zone
- Integration with MapNotes, Cartographer and friends always set in the
current zone.

commit ce35e8b832925ec497af58a9d53c70c9d387816a
Author: Jim Whitehead <[email protected]>
Date: Sat Jan 31 10:17:44 2015 +0100

Use new API to set waypoint in current zone

Beta Files (3)
File Name
Version
Hits
Size
Author
Date
v70100-1.1.0-2016-12-29
18
30MB
Cladhaire
01-12-17 02:27 PM
v70000-1.0.0-beta
131
27MB
Cladhaire
09-05-16 07:11 AM
v60000-0.1.0
709
22MB
Cladhaire
10-20-14 02:50 PM


Archived Files (42)
File Name
Version
Size
Author
Date
v70000-1.1.0-20
27MB
Cladhaire
09-07-16 07:39 AM
v60000-1.2.0-20
22MB
Cladhaire
12-21-14 10:28 AM
v60000-1.1.0-20
21MB
Cladhaire
12-13-14 05:13 AM
v60000-1.0.0-20
21MB
Cladhaire
10-26-14 10:37 AM
v60000-1.0.0
22MB
Cladhaire
10-14-14 02:01 PM
v50400-2014-07-
22MB
Cladhaire
07-26-14 04:14 AM
v50400-2014-01-
21MB
Cladhaire
01-05-14 12:42 PM
v50300-2013-06-
20MB
Cladhaire
06-18-13 11:35 PM
v50100-2013-03-
19MB
Cladhaire
03-24-13 01:54 PM
v50100-2013-03-
19MB
Cladhaire
03-24-13 09:59 AM
v50100-2013-02-
15MB
Cladhaire
02-18-13 02:37 PM
v50100-2012-10-
18MB
Cladhaire
11-28-12 02:22 PM
v50001-2012-10-
18MB
Cladhaire
10-10-12 11:45 PM
v50001-2012-09-
18MB
Cladhaire
09-29-12 02:39 PM
v50001-r352
17MB
Cladhaire
09-10-12 12:02 AM
v50001-r151
16MB
Cladhaire
09-09-12 02:56 AM
r344
16MB
Cladhaire
01-24-12 02:52 AM
r341
17MB
Cladhaire
07-13-11 04:46 AM
r339
15MB
Cladhaire
07-12-11 04:35 AM
r337
14MB
Cladhaire
05-13-11 10:26 AM
r333
13MB
Cladhaire
03-09-11 05:29 AM
r331
12MB
Cladhaire
02-20-11 12:00 PM
r330
12MB
Cladhaire
02-02-11 03:50 AM
r327
12MB
Cladhaire
01-13-11 11:16 AM
r326
12MB
Cladhaire
01-03-11 12:25 PM
r325
12MB
Cladhaire
01-02-11 12:22 PM
r322
11MB
Cladhaire
12-14-10 11:49 PM
r321
11MB
Cladhaire
12-08-10 10:36 AM
r320
11MB
Cladhaire
11-30-10 04:48 PM
r317
14MB
Cladhaire
11-25-10 06:07 AM
r316
14MB
Cladhaire
10-27-10 05:15 AM
r315
14MB
Cladhaire
10-13-10 11:28 AM
r310
14MB
Cladhaire
09-04-10 09:35 AM
r308
14MB
Cladhaire
09-03-10 04:53 AM
r306
13MB
Cladhaire
08-21-10 08:22 AM
r304
13MB
Cladhaire
03-29-10 05:07 AM
r303
13MB
Cladhaire
03-28-10 05:39 AM
r301
12MB
Cladhaire
12-09-09 12:19 PM
r298
12MB
Cladhaire
10-10-09 08:41 AM
r297
11MB
Cladhaire
08-09-09 07:36 PM
r295
11MB
Cladhaire
08-05-09 08:01 AM
r293
10MB
Cladhaire
06-03-09 03:08 PM


Post A Reply Comment Options
Unread 11-17-08, 02:35 PM  
Zidomo
A Cliff Giant
 
Zidomo's Avatar

Forum posts: 76
File comments: 1046
Uploads: 0
Yes, the fact it seems to throw the error even when no other quest mods/mods are active explains what I have been experiencing.

As well, out of all other quest mods tried with this, it only reported the name of one. Every other time the report came up, the mod name was not shown in the popup box ("LightHeaded has detected an addon conflict. The following addons may have a severe impact on the performance of your client in combination with LightHeaded; it is suggest that you disable these addons or contact the authors for a fix: |cffff1111%s|r")

The only time the name of the "conflicting" mod appeared in the text was with bEQL (latest r184). Also tried the following mods/mod combos alone with Lightheaded. None of them appeared in the conflict message; after the colon, it was blank:
--QuestGuru (v0.9.5)
--DoubleWide (v0.7-30000) + BetterQuest
--DoubleWide + SmoothQuest

None of them had "performance issues" on the client here. Either when used with r259 of Lightheaded now or with earlier versions of it with the message not present (in previous weeks).

(WoW 3.0.3 (WotLK installed), USEng client/server).
Report comment to moderator  
Reply With Quote
Unread 11-17-08, 01:09 PM  
Cladhaire
Salad!
 
Cladhaire's Avatar
Premium Member
AddOn Author - Click to view AddOns

Forum posts: 1935
File comments: 4646
Uploads: 18
Originally posted by Balsta
ok this is kinda funny. I did some research trying to find the conflicting mods. Monkeyquest and its libs are defiantly one conflict. I dropped that mod out the errors went away but i was still getting the addon conflict dialog from LH. So I started removing mods trying to find the conflict. Any guess as to what I found?

LH was causing the dialog to pop on its very own. lol I was getting the pop up with no other mods turned on at all. So there must be a flaw in the detection. Now to reproduce this I did have to open LH click a few quests then close the log. I would then reopen the log click a quest and bingo pop up.

Hope this helps. Let me know if I can do anything else.
There is a flaw in the detection and I'm hoping to improve it. You can reproduce it right now by opening the quest log 10 times without having QUEST_LOG_UPDATE fire. I hope to have an "improved" version posted relatively soon, but I'm still working out some of the kinks with it. The criteria to actually trigger it will be pretty high.. so it won't provide much use to those people who are actually experiencing the performance issues that it's meant to detect.

It's a tough problem either way you look at 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..."
Report comment to moderator  
Reply With Quote
Unread 11-17-08, 01:06 PM  
Balsta
Guest

Join Date: Not Yet
Forum posts: 0
File comments: 0
Uploads: 0
ok this is kinda funny. I did some research trying to find the conflicting mods. Monkeyquest and its libs are defiantly one conflict. I dropped that mod out the errors went away but i was still getting the addon conflict dialog from LH. So I started removing mods trying to find the conflict. Any guess as to what I found?

LH was causing the dialog to pop on its very own. lol I was getting the pop up with no other mods turned on at all. So there must be a flaw in the detection. Now to reproduce this I did have to open LH click a few quests then close the log. I would then reopen the log click a quest and bingo pop up.

Hope this helps. Let me know if I can do anything else.
Report comment to moderator  
Edit/Delete Message Reply With Quote
Unread 11-17-08, 12:07 PM  
Balsta
Guest

Join Date: Not Yet
Forum posts: 0
File comments: 0
Uploads: 0
Originally posted by Cladhaire
I do not understand why this is happening. There is clearly some conflict with another addon that I'd like you to try and figure out for me. Would you please do some more troubleshooting using the procedure I've outlined in the forums post?
KK will see what I can find
Report comment to moderator  
Edit/Delete Message Reply With Quote
Unread 11-16-08, 05:46 PM  
Cladhaire
Salad!
 
Cladhaire's Avatar
Premium Member
AddOn Author - Click to view AddOns

Forum posts: 1935
File comments: 4646
Uploads: 18
Originally posted by Aesir
In my defense, the top entries for the changelog (typically, the most recent comments) are now using some method of ordering that I'm not familiar with.

Thanks for the quick response.

[/b]
Aye, not sure how I screwed em up, sorry about 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..."
Report comment to moderator  
Reply With Quote
Unread 11-16-08, 04:47 PM  
Aesir
An Aku'mai Servant
 
Aesir's Avatar
AddOn Author - Click to view AddOns

Forum posts: 30
File comments: 148
Uploads: 1
In my defense, the top entries for the changelog (typically, the most recent comments) are now using some method of ordering that I'm not familiar with.

Thanks for the quick response.

Originally posted by Cladhaire
Both the changelog and the addon comments address this.
__________________
-- ęsir
Last edited by Aesir : 11-16-08 at 04:48 PM.
Report comment to moderator  
Reply With Quote
Unread 11-16-08, 04:43 PM  
Cladhaire
Salad!
 
Cladhaire's Avatar
Premium Member
AddOn Author - Click to view AddOns

Forum posts: 1935
File comments: 4646
Uploads: 18
Originally posted by Aesir
(paraphrasing)
At logon, LightHeader r259 reports that it has detected a conflict with another addon that can potentially impact client performance. It then recommends disabling the following addons and contacting their respective authors:
LightHeaded, QuestHelper

r257 didn't display this notification.

What's changed? What is LH evaluating that would lead it to arrive at it's conclusion? I'm looking for info so that I can make an informed decision about disabling either or neither addon.
Both the changelog and the addon comments address this. For the meantime this may be just a red-herring, and I'm working to improve the detection in the next version. I don't anticipate any conflicts with QuestHelper at this time.
__________________
"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..."
Report comment to moderator  
Reply With Quote
Unread 11-16-08, 04:40 PM  
Aesir
An Aku'mai Servant
 
Aesir's Avatar
AddOn Author - Click to view AddOns

Forum posts: 30
File comments: 148
Uploads: 1
(paraphrasing)
At logon, LightHeader r259 reports that it has detected a conflict with another addon that can potentially impact client performance. It then recommends disabling the following addons and contacting their respective authors:
LightHeaded, QuestHelper

r257 didn't display this notification.

What's changed? What is LH evaluating that would lead it to arrive at it's conclusion? I'm looking for info so that I can make an informed decision about disabling either or neither addon.
__________________
-- ęsir
Report comment to moderator  
Reply With Quote
Unread 11-16-08, 04:19 PM  
Cladhaire
Salad!
 
Cladhaire's Avatar
Premium Member
AddOn Author - Click to view AddOns

Forum posts: 1935
File comments: 4646
Uploads: 18
Originally posted by Balsta
With newest version I am getting the following errors. everything worked fine prior to the newest release. Sorry for large post.

[2008/11/16 14:32:55-242-x3]: LightHeaded-259\LightHeaded.lua:486: attempt to index local 'comment' (a nil value)
LightHeaded-259\LightHeaded.lua:531: in function `GetCommentText'
LightHeaded-259\LightHeaded.lua:745: in function `GetPageText'
LightHeaded-259\LightHeaded.lua:801: in function `UpdateFrame'
LightHeaded-259\LightHeaded.lua:211: in function `SelectQuestLogEntry'
LightHeaded-259\LightHeaded.lua:41: in function <Interface\AddOns\LightHeaded\LightHeaded.lua:40>
<in C code>: in function `SelectQuestLogEntry'
LibQuixote-2.0\LibQuixote-2.0.lua:245: in function `?'
LibQuixote-2.0\LibQuixote-2.0.lua:119: in function <...ns\EveryQuest\libs\LibQuixote-2.0\LibQuixote-2.0.lua:118>


[2008/11/16 14:32:55-242-x3]: LightHeaded-259\LightHeaded.lua:486: attempt to index local 'comment' (a nil value)
LightHeaded-259\LightHeaded.lua:531: in function `GetCommentText'
LightHeaded-259\LightHeaded.lua:745: in function `GetPageText'
LightHeaded-259\LightHeaded.lua:801: in function `UpdateFrame'
LightHeaded-259\LightHeaded.lua:211: in function `SelectQuestLogEntry'
LightHeaded-259\LightHeaded.lua:41: in function <Interface\AddOns\LightHeaded\LightHeaded.lua:40>
<in C code>: in function `SelectQuestLogEntry'
Altoholic-3.0.002b\Frames\Quests.lua:182: in function `UpdateQuestLog'
Altoholic-3.0.002b\Frames\Quests.lua:199: in function `?'
CallbackHandler-1.0\CallbackHandler-1.0.lua:146: in function <...ber\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:146>
<string>:"safecall Dispatcher[1]":4: in function <[string "safecall Dispatcher[1]"]:4>
<in C code>: ?
<string>:"safecall Dispatcher[1]":13: in function `?'
CallbackHandler-1.0\CallbackHandler-1.0.lua:91: in function `Fire'
AceEvent-3.0\AceEvent-3.0.lua:70: in function <...s\AckisRecipeList\libs\AceEvent-3.0\AceEvent-3.0.lua:69>


[2008/11/16 14:32:56-242-x12]: LightHeaded-259\LightHeaded.lua:486: attempt to index local 'comment' (a nil value)
LightHeaded-259\LightHeaded.lua:531: in function `GetCommentText'
LightHeaded-259\LightHeaded.lua:745: in function `GetPageText'
LightHeaded-259\LightHeaded.lua:801: in function `UpdateFrame'
LightHeaded-259\LightHeaded.lua:211: in function `SelectQuestLogEntry'
LightHeaded-259\LightHeaded.lua:41: in function <Interface\AddOns\LightHeaded\LightHeaded.lua:40>
<in C code>: in function `SelectQuestLogEntry'
MonkeyQuest-2.9\MonkeyQuest.lua:565: in function `MonkeyQuest_Refresh'
MonkeyQuest-2.9\MonkeyQuest.lua:217: in function `MonkeyQuest_OnEvent'
<string>:"*:OnEvent":1: in function <[string "*:OnEvent"]:1>
I do not understand why this is happening. There is clearly some conflict with another addon that I'd like you to try and figure out for me. Would you please do some more troubleshooting using the procedure I've outlined in the forums post?
__________________
"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..."
Report comment to moderator  
Reply With Quote
Unread 11-16-08, 02:33 PM  
Balsta
Guest

Join Date: Not Yet
Forum posts: 0
File comments: 0
Uploads: 0
With newest version I am getting the following errors. everything worked fine prior to the newest release. Sorry for large post.

[2008/11/16 14:32:55-242-x3]: LightHeaded-259\LightHeaded.lua:486: attempt to index local 'comment' (a nil value)
LightHeaded-259\LightHeaded.lua:531: in function `GetCommentText'
LightHeaded-259\LightHeaded.lua:745: in function `GetPageText'
LightHeaded-259\LightHeaded.lua:801: in function `UpdateFrame'
LightHeaded-259\LightHeaded.lua:211: in function `SelectQuestLogEntry'
LightHeaded-259\LightHeaded.lua:41: in function <Interface\AddOns\LightHeaded\LightHeaded.lua:40>
<in C code>: in function `SelectQuestLogEntry'
LibQuixote-2.0\LibQuixote-2.0.lua:245: in function `?'
LibQuixote-2.0\LibQuixote-2.0.lua:119: in function <...ns\EveryQuest\libs\LibQuixote-2.0\LibQuixote-2.0.lua:118>


[2008/11/16 14:32:55-242-x3]: LightHeaded-259\LightHeaded.lua:486: attempt to index local 'comment' (a nil value)
LightHeaded-259\LightHeaded.lua:531: in function `GetCommentText'
LightHeaded-259\LightHeaded.lua:745: in function `GetPageText'
LightHeaded-259\LightHeaded.lua:801: in function `UpdateFrame'
LightHeaded-259\LightHeaded.lua:211: in function `SelectQuestLogEntry'
LightHeaded-259\LightHeaded.lua:41: in function <Interface\AddOns\LightHeaded\LightHeaded.lua:40>
<in C code>: in function `SelectQuestLogEntry'
Altoholic-3.0.002b\Frames\Quests.lua:182: in function `UpdateQuestLog'
Altoholic-3.0.002b\Frames\Quests.lua:199: in function `?'
CallbackHandler-1.0\CallbackHandler-1.0.lua:146: in function <...ber\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:146>
<string>:"safecall Dispatcher[1]":4: in function <[string "safecall Dispatcher[1]"]:4>
<in C code>: ?
<string>:"safecall Dispatcher[1]":13: in function `?'
CallbackHandler-1.0\CallbackHandler-1.0.lua:91: in function `Fire'
AceEvent-3.0\AceEvent-3.0.lua:70: in function <...s\AckisRecipeList\libs\AceEvent-3.0\AceEvent-3.0.lua:69>


[2008/11/16 14:32:56-242-x12]: LightHeaded-259\LightHeaded.lua:486: attempt to index local 'comment' (a nil value)
LightHeaded-259\LightHeaded.lua:531: in function `GetCommentText'
LightHeaded-259\LightHeaded.lua:745: in function `GetPageText'
LightHeaded-259\LightHeaded.lua:801: in function `UpdateFrame'
LightHeaded-259\LightHeaded.lua:211: in function `SelectQuestLogEntry'
LightHeaded-259\LightHeaded.lua:41: in function <Interface\AddOns\LightHeaded\LightHeaded.lua:40>
<in C code>: in function `SelectQuestLogEntry'
MonkeyQuest-2.9\MonkeyQuest.lua:565: in function `MonkeyQuest_Refresh'
MonkeyQuest-2.9\MonkeyQuest.lua:217: in function `MonkeyQuest_OnEvent'
<string>:"*:OnEvent":1: in function <[string "*:OnEvent"]:1>
Report comment to moderator  
Edit/Delete Message Reply With Quote
Unread 11-16-08, 02:32 PM  
Felas08
A Murloc Raider
 
Felas08's Avatar

Forum posts: 4
File comments: 5
Uploads: 0
There's a typo fault on the addon info page its says: Comments parsed 2008-Nov-1, including WoTLK quests but it needs to be Nov-11!
__________________
Report comment to moderator  
Reply With Quote
Unread 11-16-08, 01:05 PM  
Cladhaire
Salad!
 
Cladhaire's Avatar
Premium Member
AddOn Author - Click to view AddOns

Forum posts: 1935
File comments: 4646
Uploads: 18
Originally posted by Allara
One of the things I did a lot with LH is re-click the same quest to jump back to the first page, usually so I could see who the turn in was really quick. That functionality will obviously no longer work that way, so I was wondering if you'd consider putting in some sort of little link/button on every page to jump back to the first page. Either "Home", "First", "<<" or some such would do the trick nicely.

So far I've gotten one warning from LH regarding QuestGuru. The warning occurred when I was just clicking the quest several times in a row in my quest log. I then reloaded the UI and tried that again to verify the steps to repro, and after clicking on the quest in my log 3 times rapidly, I got the LH warning again, but this time it did not identify any add-ons in the list.

What criteria do you use to issue the warning? Does my clicking repeatedly fake your code out to warn (thinking I'm an automated timer)? If so, no problem, because no sane user would actually click quests that fast like I just did.
Yes, its a heuristic and not a very smart one right now. I'll work to improve it. As for the first problem, I'll work on doing 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..."
Report comment to moderator  
Reply With Quote
Unread 11-16-08, 01:03 PM  
Allara
A Kobold Labourer
 
Allara's Avatar
Premium Member
AddOn Author - Click to view AddOns

Forum posts: 1
File comments: 123
Uploads: 3
One of the things I did a lot with LH is re-click the same quest to jump back to the first page, usually so I could see who the turn in was really quick. That functionality will obviously no longer work that way, so I was wondering if you'd consider putting in some sort of little link/button on every page to jump back to the first page. Either "Home", "First", "<<" or some such would do the trick nicely.

So far I've gotten one warning from LH regarding QuestGuru. The warning occurred when I was just clicking the quest several times in a row in my quest log. I then reloaded the UI and tried that again to verify the steps to repro, and after clicking on the quest in my log 3 times rapidly, I got the LH warning again, but this time it did not identify any add-ons in the list.

What criteria do you use to issue the warning? Does my clicking repeatedly fake your code out to warn (thinking I'm an automated timer)? If so, no problem, because no sane user would actually click quests that fast like I just did.
Report comment to moderator  
Reply With Quote
Unread 11-16-08, 12:15 PM  
Cladhaire
Salad!
 
Cladhaire's Avatar
Premium Member
AddOn Author - Click to view AddOns

Forum posts: 1935
File comments: 4646
Uploads: 18
Originally posted by Raventis
For some reason I cannot get LightHeaded to load anything. Upon opening the quest log, all I see a blank panel with greyed out page buttons and the WowHead logo. When I double-click a quest I will get an error box which says:

"Lightheaded has detected an addon conflict. The following addons may have a severe impact on the performance of your client in combination with LightHeaded; it is suggest[sic] that you disable these addons or contact the authors for a fix:"

No addons are listed below that.

I run the following addons:
Altoholic, AtlasLoot, ChatColorSync, ChatLink, Fizzwidget Faction Friend, FlagRSP WotLK, Gatherer, IceHUD, Identity, ItemRack, Lightheaded, Lore, Mobinfo, Omen3, OmniCC, Swatter, TomTom, VisualHeal, and TitanPanel: Friends, Guild, Quests, Bag, Clock, Coords, Performance, Repair, and XP.

I diabled all of the above in groups and could not seem to get LightHeaded to load anything.

Edit:

I just hopped onto a different realm and disabled all addons at once, ensuring that LightHeaded was the ONLY addon running, and still nothing loaded. I still received the same error message when double-clicking a quest, despite the fact it was the only addon running.
You need to follow the troubleshooting steps outlined here: http://www.wowinterface.com/forums/s...ad.php?t=18962

As for why you would get the conflict wiht no other addons running, I will look into it. Either way, your LightHeaded is not installed properly.
__________________
"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 : 11-16-08 at 12:19 PM.
Report comment to moderator  
Reply With Quote
Unread 11-16-08, 12:03 PM  
Raventis
A Kobold Labourer

Forum posts: 0
File comments: 11
Uploads: 0
For some reason I cannot get LightHeaded to load anything. Upon opening the quest log, all I see a blank panel with greyed out page buttons and the WowHead logo. When I double-click a quest I will get an error box which says:

"Lightheaded has detected an addon conflict. The following addons may have a severe impact on the performance of your client in combination with LightHeaded; it is suggest[sic] that you disable these addons or contact the authors for a fix:"

No addons are listed below that.

I run the following addons:
Altoholic, AtlasLoot, ChatColorSync, ChatLink, Fizzwidget Faction Friend, FlagRSP WotLK, Gatherer, IceHUD, Identity, ItemRack, Lightheaded, Lore, Mobinfo, Omen3, OmniCC, Swatter, TomTom, VisualHeal, and TitanPanel: Friends, Guild, Quests, Bag, Clock, Coords, Performance, Repair, and XP.

I diabled all of the above in groups and could not seem to get LightHeaded to load anything.

Edit:

I just hopped onto a different realm and disabled all addons at once, ensuring that LightHeaded was the ONLY addon running, and still nothing loaded. I still received the same error message when double-clicking a quest, despite the fact it was the only addon running.
Last edited by Raventis : 11-16-08 at 12:10 PM.
Report comment to moderator  
Reply With Quote
Post A Reply



Category Jump:

Support AddOn Development!

You have just downloaded by the author . If you like this AddOn why not consider supporting the author? This author has set up a donation account. Donations ensure that authors can continue to develop useful tools for everyone.