MainTank Target

[neverg]

If I wanted to show the MainTank Target on my layout is there a way to do this without a .xml template?

I don't think there is as oUF don't feed this unit (I looked into the ouf source code), but I could be wrong of course.

I'm spawning the MainTanks like this:

-- Main Tank Frames
        if cfg.show_MainTanks then
            self:SetActiveStyle('lumen - Maintank')
            local maintank = self:SpawnHeader("oUF_MainTank", nil, "raid, party, solo",
            "showRaid", true,
            "xoffset", 7,
            "yOffset", 7,
            "maxColumns", 1,
            "unitsPerColumn", 5,
            "columnSpacing", 7,
            "point", "LEFT",
            "columnAnchorPoint", "TOP",
            "sortMethod", "NAME",
            "groupFilter", "MAINTANK",
            "oUF-initialConfigFunction", ([[
            self:SetWidth(%d)
            self:SetHeight(%d)
            self:SetScale(%d)
            ]]):format(cfg.mt_width, cfg.mt_height, cfg.scale))
            maintank:SetPoint("TOPLEFT", oUF_lumenTarget, "BOTTOMRIGHT", cfg.mt_pos_x, cfg.mt_pos_y)
        end
    end)

[yj589794]

You will need to use an XML template for MT targets.

I'll not post my implementation, as last time I tried it there were a bucket load of errors due to changes in oUF 1.5 and the secure template stuff.

I'll get round to fixing it soon(TM), but work is kicking my arse at the moment.

If anyone has a nice working solution for oUF 1.5 then please post any info you have. I may end up 'borrowing' your ideas as well

[neverg]

Thanks Evil, fast and direct as always.

Well I thought so, about not having alternative on the MT Target Template because of the secure headers, but one can always ask.

So... this being said, I'm always interested in an implementation that works! ^^

Thanks in advance.

[Dawn]

This is what I'm using for ages. So not sure if this is broken now or something, because I haven't raided in months...

spawn in layout

	self:SetActiveStyle"Slim - MainTank"
	local Main_Tank = self:SpawnHeader("oUF_MainTank", nil, 'raid, party, solo', 
		'showRaid', true, 
		"groupFilter", "MAINTANK", 
		'yOffset', -10, 
		"template", "oUF_SlimMTartemplate",		-- MT Target
		'oUF-initialConfigFunction', ([[
			self:SetWidth(%d)
			self:SetHeight(%d)
		]]):format(cfg.widthM, cfg.heightM))		
	Main_Tank:SetPoint("TOPRIGHT", UIParent, "TOPRIGHT", -80, -250)

xml template for Targets

	<Button name="oUF_SlimMTartemplate" inherits="SecureUnitButtonTemplate" hidden="true" virtual="true">
		<Frames>
			<Button name="$parentTarget" inherits="SecureUnitButtonTemplate">
				<Anchors>
					<Anchor point="RIGHT" relativePoint="LEFT" relativeTo="$parent">
					<Offset><AbsDimension x="-12" y="0"/></Offset>
					</Anchor>
				</Anchors>
				<Attributes>
					<Attribute name="unitsuffix" type="string" value="target"/>
					<Attribute name="useparent-unit" type="boolean" value="true"/>
					<Attribute name="type1" type="string" value="target"/>
					<Attribute name="initial-unitWatch" type="boolean" value="true"/>
				</Attributes>
			</Button>
		</Frames>
	</Button>

[haste]

You can actually do it without using templates through the magic that is oUF 1.5.x and WoW 4.x. It will only spawn the actual targets however, so you would have to spawn one header for the MainTanks and one for the targets.

local mtt = self:SpawnHeader(
    nil, nil, 'raid,party',
    'showRaid', true,
    'groupFilter', 'MAINTANK',
    'oUF-initialConfigFunction', [[
        self:SetHeight(22)
        self:SetWidth(220)
    ]]
)
local mtt = self:SpawnHeader(
    nil, nil, 'raid,party',
    'showRaid', true,
    'groupFilter', 'MAINTANK',
    'oUF-initialConfigFunction', [[
        self:SetHeight(22)
        self:SetWidth(220)
        self:SetAttribute('unitsuffix', 'target')
    ]]
)

[neverg]

That's very interesting, haste! Thanks. I am spawning another header just for the Main Tank anyway, so one more, one less... I guess the performance impact wouldn't be that great, right?

And duh, i tottally forgot about the Unitsuffix attribute.

@Dawn, thanks for the code.

[haste]

Originally Posted by neverg That's very interesting, haste! Thanks. I am spawning another header just for the Main Tank anyway, so one more, one less... I guess the performance impact wouldn't be that great, right?

The performance impact shouldn't be noticeable.

[neverg]

Here they are, set and ready without a template. Thanks for the help.

[haste]

Just fyi, you can remove the type1 and initial-unitWatch attribute from the XML template. oUF does this by default in 1.5.x.

[neverg]

I found a slight bug with the Main Tank Target, the alpha doesn't work for it, it always shows as Out of Range for me, but I disabled the alpha on those units, don't need it anyway. Just for future reference.

[yj589794]

It's not a bug, but just how the range checking is limited on Blizzards side.

The API given by Blizzard UnitInRange only returns values for party and raid members.

If you want to do range checking on target units then you'll need to use something like oUF_SpellRange

[neverg]

Originally Posted by yj589794 It's not a bug, but just how the range checking is limited on Blizzards side. The API given by Blizzard UnitInRange only returns values for party and raid members. If you want to do range checking on target units then you'll need to use something like oUF_SpellRange

Ye, I thought it was Blizzard fault tbh, since the Range element is from Blizzard in Raid. I do use SpellRange so ye, there it is the solution. Thanks Paul.

[Phanx]

Originally Posted by haste It will only the actual targets however, so ...

I think you accidentally a word there.

[neverg]

Originally Posted by Phanx I think you accidentally a word there.

Like you did, right?

[haste]

Originally Posted by Phanx I think you accidentally a word there.

I've had a splitting headache for the past three days due to my cold, so I'll just blame it on that :P. Today is actually the first day where I barely notice it \/.

I've edited the post and added the missing "spawn".