21 - conflict when used with GoblinVendorFilter
What steps will reproduce the problem?
1. Install both addons (GoblinVendorFilter can be found here: http://www.wowace.com/addons/goblinvendorfilter/)
2. Open a vendor window and filter it's content (doesn't matter how)
3. Try to buy something
What is the expected output? What do you see instead?
Instead of buying what you click an error is generated.
What version of the product are you using?
GoblinVendorFilter 0.7.2b
NazScrooge 1.9
Do you have an error log of what happened?
Yes, see below
1x NazScrooge-1.9\Core.lua:580 attempt to perform arithmetic on local 'price' (a nil value)
(tail call): ?:
(tail call): ?:
GnomishVendorShrinker-3.2.0.4\GnomishVendorShrinker.lua:59 in function <...dOns\GnomishVendorShrinker\GnomishVendorShrinker.lua:49
GnomishVendorShrinker-3.2.0.4\GnomishVendorShrinker.lua:70 in function `BuyItem'
GnomishVendorShrinker-3.2.0.4\GnomishVendorShrinker.lua:30 in function <...dOns\GnomishVendorShrinker\GnomishVendorShrinker.lua:22
Locals:
(*temporary) = "LeftButton"
(*temporary) = false
(*temporary) = nil
(*temporary) = nil
(*temporary) = nil
(*temporary) = <function> defined =[C]:-1
---
Please provide any additional information below.
When NazScrooge is disabled no error is generated and buying things when a filter is active is working as it should.
When both addons are active, but no filters are used things also work normally, it's only with an active filter that this error occurs.
- 1 comment
- 1 comment
- Reply
- #1
gramg Jan 21, 2010 at 03:00 UTC - 0 likesFrom what I can tell GVF messes up a Blizz function by changing indexes. I have no idea how I can fix this on my end as without a reliable GetMerchantItemInfo NazScrooge cannot work. You can create a ticket with GVF and explain what is happening is this:
A hooked BuyMerchantItem in NazScrooge is calling GetMerchantItemInfo and relying on the return of an item's price. Price is being returned as nil and thus causing an error, this only occurs when GVF is running and a filter is active.
Please make sure to create a ticket for feature requests/bug reports. A comment on curse.com is unlikely to be seen very soon and if seen unlikely to be remembered when I have time to code.