NPC names are clickable, and show their locations if available
Showing a sample comment from http://www.wowhead.com
Quest overview screen
LightHeaded's Detatched Frame
Item tooltips, and using the /lh bgalpha 0.5
LightHeaded
Rate:
Comments parsed 2008-Apr-26
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.
The addon I use to make my quest log wide, is called DoubleWide, and you can download it here at http://www.wowinterface.com/downloads/info6887-DoubleWide.html. LightHeaded should work with any quest log that uses QuestLogFrame.
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
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.
The World of Warcraft 2.4 patch brings lots of API changes in particular to the combat log, but they also snuck in a nice change. You can now shift-click a quest in the quest log to send a link to another player. A side-effect of this is that the internal numeric quest ids that are used to identify each quest have been exposed.
This means I am now able to correlate quest data between wowhead.com and the game client, to display more accurate quest information. In addition, this instantly localized the addon so it works with any game client. The comments will still appear in English (as will the names in the Quest Series) section of the information, but I no longer need to distribute a large database for other locales.
When installing this version of the addon, please remove any prior versions of LightHeaded (and it's data addons) that you might have laying around. They are not needed in this version, and deleting them ensures you get the latest version of the addon.
There may be bugs as we work through these changes, so thank you in advance for reporting them to me so I can fix them as soon as possible.
* Fixed a bug that caused the wrong quest to be displayed after the frame was unhidden
* Changed the behavior of the close button to close the quest log instead of the frame
* If you are using a quest log other than the default, the behavior shoudl be unchanged
* Fixed an issue where the page would flip back to 1 due to other addons
* Fixed an issue where the close button wasn't clickable
* Fixed a bug that prevented you from clicking on the quest title to go back to page 1
* Fixed a bug that could occur when loading item tooltips
* Fixed two bugs with unknown quest names
* Fixed an issue where waypoints were being set without proper titles
* Fixed a bug due to stray calls to QuestLogTitleButton_OnClick
* Patch from Fin that enables /lh autodata, a slash command to toggle the automatic loading of quest data.
* This will make all quest series information show up with quest titles, when enabled.
Originally posted by thegriffgeeks Hey Clad, I've gotten this error over the last few days. Sorry I didn't post it earlier.
[2008/05/11 16:51:51-1125-x2]: LightHeaded-233\LightHeaded.lua:114: attempt to compare number with string
---
That would be an addon calling LightHeaded, but not being updated to work with the new 2.4 API. Do you have another quest addon that might not be updated yet?
__________________
"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..."
Originally posted by Sidewalk First off, not fighting you on this. I said I had not deep dived and wasn't sure what they are doing.
Second, it's not my place to tell others how to code or how to fix it. If it's a simple fix, you as a developer can talk to them.
Lastely, this is not a pissing match to see how's code is right or wrong. If YOUR code needs everyone else to be "pristine" for it to function correctly, then yours will only be used in "pristine" environments.
When I write objects for production software, I don't assume anything and write stuff knowing other developers objects will most likely function in the worst possible scenario where my objects are concerned.
Take that any way you want ... I am done here. Maybe there is nothing you can do on your end, and I don't desire to learn yet another programming language. Personally, for this user, I will use the mod that is the most valuable to me ... this mod is off the list ... sorry.
There is nothing Cladhaire can do. Period. If he didn't use that function, there would be no other way to know. Surely sometimes you can deal with other addons causing trouble, but sometimes you can't. This is one of those times that you can't. Period.
Let's look at Microsoft Windows. Now we all know that Windows doesn't work anyway, but bear with me. Let us assume that I wrote a driver that's completely unrelated to some driver that you are writing, but we both use the same tools. I corrupt memory in that tool. You use that tool and cause a bluescreen because the data is invalid. Now you tell me, is it your fault?
__________________
"A life spent making mistakes is not only more honorable, but more useful than a life spent doing nothing. " ~George Bernard Shaw
Originally posted by Sidewalk First off, not fighting you on this. I said I had not deep dived and wasn't sure what they are doing.
I responded answering your question, and you came back and told me that I was wrong, basically. Forgive me for not taking that very well.
Quote:
Second, it's not my place to tell others how to code or how to fix it. If it's a simple fix, you as a developer can talk to them.
I barely don't have time to develop my own addons, or do my own work, let along contact other authors to explain why what they are doing is causing issues with my addons. Feel free to have the author get in contact with me and I'll speak with him.. but I can't do all of the running here.
Quote:
Lastely, this is not a pissing match to see how's code is right or wrong. If YOUR code needs everyone else to be "pristine" for it to function correctly, then yours will only be used in "pristine" environments.
When I write objects for production software, I don't assume anything and write stuff knowing other developers objects will most likely function in the worst possible scenario where my objects are concerned.
Take that any way you want ... I am done here. Maybe there is nothing you can do on your end, and I don't desire to learn yet another programming language. Personally, for this user, I will use the mod that is the most valuable to me ... this mod is off the list ... sorry.
Wow, this is about the rudest thing I've ever read. Why would you think you can just waltz in here and continue to tell me that I'm wrong when you obviously haven't even spent 15 seconds looking into the code to see what is wrong. You will find that I am one of the most accommodating authors out there always willing to work hard to make things work well for my users. Since you REFUSE to figure out how things work and regardless continue to tell me that I'm not only wrong, but somehow doing you a disservice let me explain exactly what is happening here and WHY this doesn't work.
The Quest API returns data about the quests in your quest log but requires the quest to be "selected" in order to return something like the description or rewards. Every X seconds, QuestHelper scans through the quest log and selects each quest in order to obtain information about it. When it is done, it sets the quest log selection back to the original selection.
The only reasonable way for LightHeaded to detect the quest selection changing is by hooking the SelectQuestLogEntry() function, which is the one I'm discussing above.
The _problem_ is, QuestHelper doesn't need to do this. The information it needs to get can be gotten from the API without needing to scan through each of the quest log entries, in particular through watching events.
I'm not really sure what the problem is here, and why you're being so combative, but I'm doing everything I can to try to help here.
Sorry if that's not good enough for you.
__________________
"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..."
Or you could do what I said, and talk to the author of QuestHelper to get the issue resolved. The quest log scanning that is being done is absolutely unnecessary and there is no way to work around it. [/b]
First off, not fighting you on this. I said I had not deep dived and wasn't sure what they are doing.
Second, it's not my place to tell others how to code or how to fix it. If it's a simple fix, you as a developer can talk to them.
Lastely, this is not a pissing match to see how's code is right or wrong. If YOUR code needs everyone else to be "pristine" for it to function correctly, then yours will only be used in "pristine" environments.
When I write objects for production software, I don't assume anything and write stuff knowing other developers objects will most likely function in the worst possible scenario where my objects are concerned.
Take that any way you want ... I am done here. Maybe there is nothing you can do on your end, and I don't desire to learn yet another programming language. Personally, for this user, I will use the mod that is the most valuable to me ... this mod is off the list ... sorry.
Originally posted by Sidewalk I didn't say "updating", I said "querying". I haven't looked at the code, but it updates the map when you complete any particular part of a quest.
ie: go 3 places, 3 things show up on the map, get to one of them, and it removes the map icon and gives you a new Cartographer way point to the next one with ant trails to the following.
Yes, and none of this requires repeatedly scanning the quest log, considering absolutely nothing changes without an event firing. You can either believe me or not, I'm not going to continue trying to convince you.
Quote:
Whether or not Lightheaded should be doing something different, or Quest Helper should be doing something different I can't tell right now as I didn't dive into the code. I would think though, the light headed being a mod that only runs when the quest log is open, vs a mod that is running all the time ... that light headed should change.
This just doesn't make sense to me. LightHeaded needs some way to know that you've selected a new quest. The _ONLY_ reliable way to do this is via the SelectQuestLogEntry() function. I'm not particularly sure why you're fighting me on this, but QuestHelper calls SelectQuestLogEntry in an OnUpdate function, which is causing the issue. There is absolutely and 0 way for me to "fix" this problem, whether you like that or not.
Quote:
I have already disabled lightheaded cause Quest helper is what I consider an essential mod for question ... and lightheaded functionality I can get from alt-tabbing. I would like to not have to alt tab ... but based upon that comment, that is my only choice.
Or you could do what I said, and talk to the author of QuestHelper to get the issue resolved. The quest log scanning that is being done is absolutely unnecessary and there is no way to work around 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..."
Originally posted by Cladhaire Unfortunately, this addon will need to alter its behavior. Updating the quest log this frequently is completely wasteful and unnecessary and obviously causes issues.
I didn't say "updating", I said "querying". I haven't looked at the code, but it updates the map when you complete any particular part of a quest.
ie: go 3 places, 3 things show up on the map, get to one of them, and it removes the map icon and gives you a new Cartographer way point to the next one with ant trails to the following.
Whether or not Lightheaded should be doing something different, or Quest Helper should be doing something different I can't tell right now as I didn't dive into the code. I would think though, the light headed being a mod that only runs when the quest log is open, vs a mod that is running all the time ... that light headed should change.
I have already disabled lightheaded cause Quest helper is what I consider an essential mod for question ... and lightheaded functionality I can get from alt-tabbing. I would like to not have to alt tab ... but based upon that comment, that is my only choice.
Not trying to advertise another site or mod, just wanted to make sure you could find / download the mod to help debug.
Unfortunately, this addon will need to alter its behavior. Updating the quest log this frequently is completely wasteful and unnecessary and obviously causes issues.
__________________
"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..."
Originally posted by Jaim Sandar Regarding the problem several including myself have posted about, the inability to get the Lightheaded pages to scroll or to change from the first page: I have been using Armory for a long time with no problem to Lightheaded that I could tell. I stopped using Carbon Quest and the Lightheaded problem stopped, but came back after a few weeks. That time I removed EquipCompare and the problem stopped. Now, a week or so later, the problem came back again. This time it WAS removing Armory that fixed it. http://www.wowinterface.com/download...52-Armory.html
I had to play my regularly scheduled Friday night game without Armory so I could use Lightheaded, and also because of another problem that always seems to happen when I have the Lightheaded paging problem: opening the Quest Log causes my screen frame rate to go down to 1 fps, and the selected quest in the log won't stay selected... it will change after a second or two to another specific quest. When I close the quest log, the frame rate goes back to normal.
Anyway, this morning I was going to load Armory and run the macro you told Maleren about. But now... IT'S WORKING GOOD!!! None of any of the problems I mentioned are apparent at this time! Very strange.
I ran the script anyway, and it doesn't output anything unless I click on something. I guess that is the way it is supposed to work.
If the problem comes back, I'll run that script again and let you know.
Unfortunately Armory does some really nasty thing with the quest log and until they stop doing that there isn't all that much I can do =(.
__________________
"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..."
Regarding the problem several including myself have posted about, the inability to get the Lightheaded pages to scroll or to change from the first page: I have been using Armory for a long time with no problem to Lightheaded that I could tell. I stopped using Carbon Quest and the Lightheaded problem stopped, but came back after a few weeks. That time I removed EquipCompare and the problem stopped. Now, a week or so later, the problem came back again. This time it WAS removing Armory that fixed it. http://www.wowinterface.com/download...52-Armory.html
I had to play my regularly scheduled Friday night game without Armory so I could use Lightheaded, and also because of another problem that always seems to happen when I have the Lightheaded paging problem: opening the Quest Log causes my screen frame rate to go down to 1 fps, and the selected quest in the log won't stay selected... it will change after a second or two to another specific quest. When I close the quest log, the frame rate goes back to normal.
Anyway, this morning I was going to load Armory and run the macro you told Maleren about. But now... IT'S WORKING GOOD!!! None of any of the problems I mentioned are apparent at this time! Very strange.
I ran the script anyway, and it doesn't output anything unless I click on something. I guess that is the way it is supposed to work.
If the problem comes back, I'll run that script again and let you know.
Last edited by Jaim Sandar : 05-10-2008 at 02:46 PM.
Originally posted by BooHag The screenshots show quest levels next to the quest names. Is this from LightHeaded, and if so, how can I turn this on?
It's another addon. In that screenshot it's Gazmik Fizzwidget's Levelator, specifically.
__________________
"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..."
