oneclick unlearn talent script

[philipe24]

Hello,
I was wondering if its possible to kinda "remove" the confirmation for unlearn talents.
I've been trying it out like this but didnt came to a result really:

PlayerTalentFrameTalentsTalentRow1Talent1:RegisterForClicks("LeftButtonUp");
PlayerTalentFrameTalentsTalentRow1Talent1:SetScript("OnMouseDown", function(self, button)

StaticPopup1Button1:Click(MouseButton, Down)

end)

Anyone got an Idea?

[Codelogic]

Originally Posted by philipe24 Hello, I was wondering if its possible to kinda "remove" the confirmation for unlearn talents. I've been trying it out like this but didnt came to a result really: PlayerTalentFrameTalentsTalentRow1Talent1:RegisterForClicks("LeftButtonUp"); PlayerTalentFrameTalentsTalentRow1Talent1:SetScript("OnMouseDown", function(self, button) StaticPopup1Button1:Click(MouseButton, Down) end) Anyone got an Idea?

Without knowing anything about programming i think this is very likely possible, like you can create a function that can Abandon more quests at once and even automatically click the confirm button. But i think you're approaching it wrong. I think it requires a click handler for them all, and not a OnMouseDown?

[Dridzt]

I'd recommend QuickTalents.

[semlar]

Here's a hackish way to bypass the confirmation dialog with the default interface..

LoadAddOn('Blizzard_TalentUI')
local macro = CreateFrame('button', nil, nil, 'SecureActionButtonTemplate')
macro:SetAttribute('type', 'macro')
macro:SetScript('OnLeave', function(self)
    self:Hide()
    GameTooltip_Hide()
    self:GetParent():SetScript('OnLeave', GameTooltip_Hide)
end)
 
hooksecurefunc('PlayerTalentFrameTalent_OnEnter', function(self)
    if InCombatLockdown() then return end
    local _, _, _, _, selected, available = GetTalentInfo(self:GetID())
    if not selected and not available then
        macro:SetParent(self)
        macro:ClearAllPoints()
        -- You can't set the points directly to the frame because it's not protected
        macro:SetPoint('TOPLEFT', nil, 'BOTTOMLEFT', self:GetLeft(), self:GetTop())
        macro:SetSize(self:GetSize())
        self:SetScript('OnLeave', nil) -- Temporarily prevent it from hiding the tooltip
        macro:SetAttribute('macrotext', format('/click %s\n/click StaticPopup1Button1', self:GetName()))
        macro:Show()
    end
end)

If you make this into an addon you should remove LoadAddOn('Blizzard_TalentUI') and add "##Dependencies: Blizzard_TalentUI" to the toc file.

[Codelogic]

Originally Posted by semlar Here's a hackish way to bypass the confirmation dialog with the default interface.. LoadAddOn('Blizzard_TalentUI') local macro = CreateFrame('button', nil, nil, 'SecureActionButtonTemplate') macro:SetAttribute('type', 'macro') macro:SetScript('OnLeave', function(self)     self:Hide()     GameTooltip_Hide()     self:GetParent():SetScript('OnLeave', GameTooltip_Hide) end)   hooksecurefunc('PlayerTalentFrameTalent_OnEnter', function(self)     if InCombatLockdown() then return end     local _, _, _, _, selected, available = GetTalentInfo(self:GetID())     if not selected and not available then         macro:SetParent(self)         macro:ClearAllPoints()         -- You can't set the points directly to the frame because it's not protected         macro:SetPoint('TOPLEFT', nil, 'BOTTOMLEFT', self:GetLeft(), self:GetTop())         macro:SetSize(self:GetSize())         self:SetScript('OnLeave', nil) -- Temporarily prevent it from hiding the tooltip         macro:SetAttribute('macrotext', format('/click %s\n/click StaticPopup1Button1', self:GetName()))         macro:Show()     end end) If you make this into an addon you should remove LoadAddOn('Blizzard_TalentUI') and add "##Dependencies: Blizzard_TalentUI" to the toc file.

can i ask what the _, _, _, _, does? Is it because you added return values selected and available, and those are the only two you wish to focus on and ignore the rest?

[semlar]

I only care about 2 of the return values so I discard the ones that come before them by assigning them to a throwaway variable.

[Codelogic]

Originally Posted by semlar I only care about 2 of the return values so I discard the ones that come before them by assigning them to a throwaway variable.

Thank you

[Phanx]

To elaborate, naming the variable _ doesn't actually do anything that naming it selected or NYAN_CAT or anything else does; it's just a programmer's naming convention. If you're only going to use the last 2 values, then these all do the same thing:

1. local _, _, _, _, selected, available = GetTalentInfo(self:GetID())
2. local name, texture, tier, column, selected, available = GetTalentInfo(self:GetID())
3. local selected, selected, selected, selected, selected, available = GetTalentInfo(self:GetID())
4. local available, available, available, available, selected, available = GetTalentInfo(self:GetID())
5. local selected, available, selected, available, selected, available = GetTalentInfo(self:GetID())
6. local cat, cat, cat, cat, selected, available = GetTalentInfo(self:GetID())
7. local cat, dog, pony, unicorn, selected, available = GetTalentInfo(self:GetID())

Using an underscore is just an easy way to make it obvious (to you and anyone else reading your code) that a particular variable isn't important.