WowAce

Hi,

After downloading the last version of Rarity through the Twitch App, the tooltip doesn't seem to show up when hovering over the minimap button. I couldn't find any fix about that online, so I am asking directly if somebody could assist me with this.

Cheers!

Just to clarify, the issue also happens when I only have Rarity alone on, so I don't think the issue comes from a conflict with another addon.

Please try the latest release. There was a bug in the UI code, which should now be fixed.

I've just tried both r697 and r697-release2, rebooted the game and the issue is still happening for me.

In that case I'll need an error message to see why it isn't working for you.

Here is what is written on the chat as I hover over the minimap icon:

Rarity: addGroup(Montures, nil) took 222.592500ms (Total: 222.585300, Sort: 87.076700, Iteration: 135.502600, Tooltip: 0.000100

Rarity: addGroup(Mascottes de combat, nil) took 423.776700ms (Total: 423.770200, Sort: 419.532100, Iteration: 2.999600, Tooltip: 1.233000

Rarity: addGroup(Jouts & Objets, nil) took 77.649200ms (Total: 77.629800, Sort: 74.565000, Iteration: 1.760600, Tooltip: 1.299100

Rarity: BuildStatistics: 0.653200ms

Rarity: ScanStatistics: 3.904000ms

Rarity: Scanning calendar (DELAYED INIT)

Rarity: Scanning toys (DELAYED INIT)

Rarity: Scanning transmog (DELAYED INIT)

Rarity: UpdateText: 0.061300ms

Still no tooltip showing up as I hover over the icon.

I will try to downgrade to a less recent version to test if the issue is still here, but I haven't changed any of the config so it shouldn't come from that... Release r695 was working fine.

Maybe an issue with the French localization?

Edit: I've just tried release r695 and the tooltip does show.

Apologies, I meant an actual Lua error. I assumed there'd be one since the addon is probably crashing when it tries to display the tooltip. Please consult the FAQ: https://www.wowace.com/projects/rarity/pages/faq/how-to-enable-and-disable-script-errors-lua-errors

The latest releases had a lot of changes; it's quite possible there are more bugs that I haven't found yet.

My bad... here is the error message returned:

Message: Interface\AddOns\Rarity\Core\GUI.lua:1198: Usage: GetItemInfo(itemID|"name"|"itemlink")
Time: Fri Mar 20 19:28:58 2020
Count: 1
Stack: Interface\AddOns\Rarity\Core\GUI.lua:1198: Usage: GetItemInfo(itemID|"name"|"itemlink")
[string "@Interface\AddOns\Rarity\Core\GUI.lua"]:404: in function `OnEnter'
[string "@Interface\AddOns\Decursive\Libs\LibDBIcon-1.0\LibDBIcon-1.0.lua"]:77: in function <...ddOns\Decursive\Libs\LibDBIcon-1.0\LibDBIcon-1.0.lua:60>

Locals: self = LibDBIcon10_Rarity {
0 = <userdata>
fadeOut = <unnamed> {
}
dataObject = <table> {
}
isMouseDown = false
db = <table> {
}
icon = <unnamed> {
}
}
frame = LibDBIcon10_Rarity {
0 = <userdata>
fadeOut = <unnamed> {
}
dataObject = <table> {
}
isMouseDown = false
db = <table> {
}
icon = <unnamed> {
}
}

Here is the error message if I disable Decursive (still doesn't show the tooltip):

Message: Interface\AddOns\Rarity\Core\GUI.lua:1198: Usage: GetItemInfo(itemID|"name"|"itemlink")
Time: Fri Mar 20 19:30:56 2020
Count: 1
Stack: Interface\AddOns\Rarity\Core\GUI.lua:1198: Usage: GetItemInfo(itemID|"name"|"itemlink")
[string "=[C]"]: ?
[string "@Interface\AddOns\Rarity\Core\GUI.lua"]:1198: in function <Interface\AddOns\Rarity\Core\GUI.lua:1127>
[string "@Interface\AddOns\Rarity\Core\GUI.lua"]:1704: in function `ShowTooltip'
[string "@Interface\AddOns\Rarity\Core\GUI.lua"]:404: in function `OnEnter'
[string "@Interface\AddOns\Details\Libs\LibDBIcon-1.0\LibDBIcon-1.0.lua"]:77: in function <...\AddOns\Details\Libs\LibDBIcon-1.0\LibDBIcon-1.0.lua:60>

Locals: (*temporary) = nil

Hope this helps :)

Hmm. Well, apparently Rarity tries to add an item to the tooltip that isn't working. It's not evident which item causes the error.

I tried setting my client to French and did not encounter any errors. I'm afraid that in order to find out why it isn't working for you, we'll have to do some digging...

1. If you swap to a different profile, does the error persist? (Might have to reload to be sure)

2. Particularly, if you create a new (empty) profile, does the error still occur?

3. If not, something in your SavedVariables likely causes it. Please PM them to me and I'll see if I can reproduce the error! They're found in the World of Warcraft\_retail_\WTF\Account\<AccountName>\SavedVariables folder, the file would be called Rarity.lua

4. If yes... I need to think of other potential causes.

Before trying anything else, however, I must be sure I understood you correctly and the following assumptions are true:

* The error message you posted is the ONLY error given. If there are multiple, the very first one is all that matters

* There is no error at all when switching to r695, regardless of whether the tooltip shows or not

I've also reviewed the changes made to this part of the addon and see no reason for why it would suddenly fail to display an item, unless you've added some custom items I don't have in my settings, and they're causing this problem. Still, more info is needed so hopefully you don't mind following the above steps :)

This was also happening for me and after reading your explanation of the error, I went in to look at my custom items. One of them was no longer able to be retrieved from the database and showed up as a different color (default green I think, not positive because I'm colorblind). For me it was the Tusks of Mannoroth, there seemed to be two for some reason, even though I'm pretty sure I only ever added it once. I deleted that item from rarity and the tooltip worked again.

I found the item that was triggering this issue as well. For me it was the Piccolo of the Flaming Fire (lootable in Stratholme). I think it came from the item pack available in the description the I installed way back. Anyway, I removed it and it now works as intended :)

Thanks for the help!

Very peculiar, but unless either of you still has the data (i.e., in the saved variables) that was stored for those items, I doubt I can find out what happened there. I'll consider this issue resolved, for now.

I tested it by making another custom item, and it turns out this happens any time there is any item that can't be retrieved from the server. All I did was create a new item and not fill in any of the information, and the same error happened.

Thanks, I will look into this again as soon as I'm able. It confuses me why this would suddenly break and seemingly never was an issue before.

Status: https://github.com/SacredDuckwhale/Rarity/issues/166