I know that 1.10 patch is this week, we are currently working on putting the finishing touches on Auctioneer/Enchantrix/Informant. We "should" have a release ready by this friday but this largely depends on our availability and the completion of the translations. If you want to help out with the translations please go to http://norganna.org/localizer.

Please note that current enchantrix version have bug, that leads to incorrect disenchant data when disenchant spell bound to a hotkey, i make a fix, that is much simplier and reliable that current method for detection disenchant target, i post it after test in 1.10 path

The old method have long in code and not fully reliable, current method is more unreliable that old and some others addons like wowecon also suffers from this problem.

The problem is in that program assumes that when your mouse enter to bag slot or tooltip appears, you already have disenchant spell turned on (if SpellIsTargeting() then …), but in my case that not true, i first hover my cursor on item, then press hotkey for disenchant spell (binded to mouse and save my time), so code may not have know yet my target or think that my target is something that i hover last time when SpellIsTargeting() has true.

P.S. sorry if my english is bad.

Posted by: Quark on Mar 29 2006, 04:40 PM
[b]The problem is in that program assumes that when your mouse enter to bag slot or tooltip appears, you already have disenchant spell turned on (if SpellIsTargeting() then …), but in my case that not true, i first hover my cursor on item, then press hotkey for disenchant spell (binded to mouse and save my time), so code may not have know yet my target or think that my target is something that i hover last time when SpellIsTargeting() has true.

Woops, didn't think of that...

I'm trying to hook PickupInventoryItem and PickupContainerItem instead. Might be enough to simply remove the check for SpellIsTargeting() though.

ok, it's works, so here is complete patching instructions ‹(^.^)›
Please note that it is for newer versions of enchantrix where disenchant target detection code is changed, previous method for disenchant target detection has been much longer, but works reliable for me…

1. Go to «World of Warcraft\Interface\Addons\Enchantrix» folder and open Enchantrix.lua in any text editor.
2. Find     Â Â Â Â -- Remember this link if user is targeting a spell
    if SpellIsTargeting() then
        DisenchantEvent.spellTarget = link
    end
3. Comment it out, for example--[[
    -- Remember this link if user is targeting a spell
    if SpellIsTargeting() then
        DisenchantEvent.spellTarget = link
    end
]]
4. Find function Enchantrix_OnLoad()
    -- Hook in new tooltip code5. Replace it withfunction Enchantrix_DetectSpellTarget(funcVars, retVal, bag, slot)
    if SpellIsTargeting() then
        DisenchantEvent.spellTarget = GetContainerItemLink(bag, slot);
    end
end

function Enchantrix_OnLoad()
--!!
    Stubby.RegisterFunctionHook("PickupContainerItem", -1, Enchantrix_DetectSpellTarget)
--!!
    -- Hook in new tooltip codesimply, isn't it? ‹(^.^)›

This code will always work for bags (don't know if it possible to disenchant weared items), no matter how you try to disenchant and no matter what you hover with mouse or where you move it ‹(^.^)›

And final question — why it is not done before? ‹(°.°)›

P.S. i use non-breaking spaces to format code, dont know what effect it will do in lua, for me copy-paste operation replace it with normal spaces, so if code will not work, just remove spaces in begin of lines

and i don't check what will happend if you click disenchant one item, then click to disenchat another, you can test it yourself or don't do it ‹(•.•)›

eh, and finally, please someone make code for me to remove incorrect disenchants from my item database, for example remove all reagents that have <1% probability, and i upload it.

Posted by: Quark on Mar 30 2006, 02:15 AM
and a feature suggestion: make some option to check if HSP/Median is less that vendor sell price and abort disenchant if it is true (rare)

This is NOT the place for feature suggestions.