WowAce

Anyone having issues with the Remote Quest Tracker? I can't click on quests that trigger that widget. I've had to disable it to keep it from hanging out on the screen all day which is less than desirable.

In reply to Dzendrieh: I've had nothing but problems with the Remote Quest Tracker, and this has been at least 2 expansions so far. I first noticed with alts leveling in BFA, I was stuck on quests, then I realized Sorha wasn't auto-popping up the Remote Tracker so I could accept the new quest. If I "/reload" when the remote tracker is available, it will show up, but after I click it to accept or turn in a quest, it is stuck until I "/reload" again. Since very few people are complaining about it, I figure it must be one of my other addons causing the tracker to get stuck. But I don't see an error, and it's very difficult to troubleshoot as I do not know a good way to trigger a remote quest to test it, like with turning addons off to see if it stope occurring. /shrug. That fucntion is pushing me to other trackers, which I hate, 'cause Sorha is otherwise my favorite. I really like the way it's laid out.

is there a way to limit the height of the tracker? I love how it looks but with many quests it easily goes under the rest of my UI

The "-nolib" uploads are really annoying with addon managers... dependent of what file you upload last, is the one downloaded, which most of teh times seem to be the "-nolib" version.
Why not use a separate project for it? Do i really need to had a filter in my addon manager code specifically to this addon, to never download the "-nolib" version?
I basically seem to be forced to do:
if (addonName=="sorhaquestlog" && fileName.endsWith("nolib") { // skip file }
But i guess i will do what ive been thinking for a while and say fuck it... have an input to ignore based on regex.
This is the only addon that i have issues for downloading the wrong file 90% of the time, because this is the only project that uses the same project page for 2 different versions of the same addon for 1 game version.

Other than that, i love the addon and been using it since BFA.

In reply to Sorha2: Fair point, i get you for not wanting to break some old code or something/someones work that rely on that.

By now I created a workaround using a regex so if there is an addon file with nolib, it will skip. So far it has been doing fine, this is the only addon that needs it, but no issues since ;)

A lot of this error is showing up now, this is while doing m+

74x [ADDON_ACTION_BLOCKED] AddOn 'SorhaQuestLog' tried to call the protected function 'ObjectiveTrackerFrame:Hide()'.
[string "@!BugGrabber/BugGrabber.lua"]:480: in function <!BugGrabber/BugGrabber.lua:480>
[string "=[C]"]: in function `Hide'
[string "@SorhaQuestLog/Core.lua"]:776: in function `HandleBlizzardTracker'
[string "@SorhaQuestLog/Core.lua"]:698: in function `RefreshConfig'
[string "@SorhaQuestLog/Core.lua"]:987: in function `ShowSorhaQuestLog'
[string "@SorhaQuestLog/Core.lua"]:669: in function `?'
[string "@Ace3/CallbackHandler-1.0-7/CallbackHandler-1.0.lua"]:114: in function <...Ons/Ace3/CallbackHandler-1.0/CallbackHandler-1.0.lua:114>
[string "=[C]"]: ?
[string "@Ace3/CallbackHandler-1.0-7/CallbackHandler-1.0.lua"]:24: in function <...Ons/Ace3/CallbackHandler-1.0/CallbackHandler-1.0.lua:20>
[string "@Ace3/CallbackHandler-1.0-7/CallbackHandler-1.0.lua"]:59: in function `Fire'
[string "@Ace3/AceEvent-3.0-4/AceEvent-3.0.lua"]:120: in function <Ace3/AceEvent-3.0/AceEvent-3.0.lua:119>

Experienced a new error:

 [ADDON_ACTION_BLOCKED] AddOn 'SorhaQuestLog' tried to call the protected function 'ObjectiveTrackerFrame:Hide()'.
[string "@!BugGrabber/BugGrabber.lua"]:480: in function <!BugGrabber/BugGrabber.lua:480>
[string "=[C]"]: in function `Hide'
[string "@SorhaQuestLog/Core.lua"]:776: in function `HandleBlizzardTracker'
[string "@SorhaQuestLog/Core.lua"]:698: in function `RefreshConfig'
[string "@SorhaQuestLog/Core.lua"]:987: in function `ShowSorhaQuestLog'
[string "@SorhaQuestLog/Core.lua"]:669: in function `?'
[string "@Ace3/CallbackHandler-1.0-7/CallbackHandler-1.0.lua"]:114: in function <...Ons/Ace3/CallbackHandler-1.0/CallbackHandler-1.0.lua:114>
[string "=[C]"]: ?
[string "@Ace3/CallbackHandler-1.0-7/CallbackHandler-1.0.lua"]:24: in function <...Ons/Ace3/CallbackHandler-1.0/CallbackHandler-1.0.lua:20>
[string "@Ace3/CallbackHandler-1.0-7/CallbackHandler-1.0.lua"]:59: in function `Fire'
[string "@Ace3/AceEvent-3.0-4/AceEvent-3.0.lua"]:120: in function <Ace3/AceEvent-3.0/AceEvent-3.0.lua:119>

This was during a m+ key

BR

Will this be updated for dragonflight? Really like this addon and hope that it stays relevant for the next expansion as well

In reply to humfras:

I'm noticing since the update that quests in my log that have an item that is used in the completion of the quest and that appears to the left of the quest text in the log for easy access no longer works correctly. Prior to the patch, I could click on the item to use it while completing the quest rather than needing to access the item in my bags. Now, the item still appears where it should, but clicking on it doesn't do anything. An example of this would be: https://www.wowhead.com/quest=25701/you-are-rakhlikh-demon

It would be nice to have that functionality back. While it appears Blizzard did make a change that allows some quest items to be used while hovering over the target mob, not all quest items work that way and still have to be accessed manually from bags. Having them accessible in the quest log was a nice quality of life improvement.

In reply to humfras:

 Just wondering if this will be fixed soon (the quest item not being interactable)?  I love Sorha and don't want to have to switch!

In reply to humfras:

 Stil not working for me.  For example, the quest WYRYM FOOD, I have the quest item GULCHAKS POINTER showing next to he quest, and also the Smart Quest item icon showing- I can interact with and highlight it and click it, but nothing happens.  I have to find the item in my bag to click it and use with the quest.  Just one example, none of the quest items work that Ive tried

In reply to humfras:

 It's not a error but its just a UI thing. World quests are listed as level 60 and therefore are marked as grey since its low level according to the log