Closed christophknuth closed 1 year ago
Sorry, this only fixes the lua errors for me for the latest version, it does not fix the mouse-over tooltip showing currencies and correct amount of gold.
Any ideas would be welcome. Will test when new fix-attempts is suggested, I will use my modified 9.0.2.1 until then. :)
I have the same issue as TreizeEU. With this fix, there are no lua errors, and the Display options that show on the broker display are correct. But when I mouse over the broker display, the popup only has a list of character names, with no currencies at all. I verified I have some selected in my settings.
Not sure what's going on. Initially I wasn't experiencing problems with the mouse over issue. After logging in a few minutes ago - it's back doing to doing it again - so reverting.
The project is 4 months old, has it been abandoned?
I made fixes to an older version to allow gold and new 9.1 currencies to be listed and there are no bugs. If @Torhal is interested, I'd be happy to provide this to him so that a fix can be pushed while hopefully the April update is worked out. @Torhal if you're interested in these fixes, just drop a message below this one and I'll provide you with what I've got.
Hello Torhal.
I am getting the below lua errors when I try to use this new commit. The broker only saying Loading.
I'm still using the 9.0.2.1 version that I have uploaded to ticket #16 . All I've done to it was to add new currencies each patch, and I commented out lines 761-765 which broke in the 10.0 pre-patch.
1x Broker_Currency/Tooltip.lua:180: attempt to index local 'gainedReference' (a nil value) [string "@Broker_Currency/Tooltip.lua"]:180: in function <Broker_Currency/Tooltip.lua:177> [string "@Broker_Currency/Tooltip.lua"]:216: in function <Broker_Currency/Tooltip.lua:184> [string "@Broker_Currency/Tooltip.lua"]:274: in function
OnEnter'
[string "@ChocolateBar/Chocolate.lua"]:266: in function <ChocolateBar/Chocolate.lua:235>
Locals: currencyIDList =
Just wanted to offer my sincerest thanks for fixing this addon! After having implemented your fix - I'm using the latest version of the addon, and haven't had any problems thus far.