Masque Questions

[Fox536]

I 've been looking at masque to see if I could add compatibility for my addon, and I can't seem to find any information on what I need to do in order for masque to see my addon. If anyone knows how it's done and has time to share that'd be awesome thanks.

[Seerah]

Have you checked out its Documentation? http://www.wowace.com/addons/masque/pages/

[Fox536]

Ya I've read through it again, and I just don't see what I need to do, to add my addon to have compatibility, any advice would be great.

[Phanx]

This part of the documentation is most relevant for addon authors:

http://www.wowace.com/addons/masque/pages/api/groups/

If you're still not able to figure it out, well, the exact code you need to write really depends on your addon. Are you just creating one button? Are you creating 1000 buttons in 10 distinct groups? Something in between? Post your code, or at least give a useful description of it.

[Duugu]

Basically you need to get a reference to Masque

local MSQ = LibStub("Masque")

create a group

local myGroup = MSQ:Group("MyAddon", "MyGroup")

and add your buttons to it.

myGroup:AddButton({Button} [, {ButtonData}])

[Fox536]

My add-on is a replacement action bar ui, but I'm trying to add this into my custom button library so skins could be used for more customization.


Ok, well for button data would it be like

-- mybutton.floating local ButtonData = { FloatingBG = { "floatingBg"},

Or something like

-- mybutton.floating local ButtonData = { FloatingBG = { "$parentfloatingBg"},

[Phanx]

If your buttons inherit from the standard ActionButtonTemplate or have regions with the same names, you do not need to explicitly map out the ButtonData. Just register your button:

<group>:AddButton(<button>)

Also, the second argument to :Group is optional. If you only want one group for your addon (eg. "MyAddon") instead of sub-groups (eg. "MyAddon > Bar 1", "MyAddon > Bar 2") that can be skinned separately, you only need to pass one argument:

Masque:Group("MyAddon")

Again, however, without seeing your actual code, it's impossible to tell you exactly how you should register your buttons with Masque.

[Fox536]

Well when I get home I'll upload my most current version of my button library, I've been updating to fix a lot of what got messed up since 6.0.2, I've got most of the problems fixed, at least until they fix the issues with the mountJournal and I either write a work around for toys or they fix it. But I don't know off the top of my head if I even gave most of my textures names or not, I doubt I did as most of them didn't need names, but I can add names to them, if need be. I probably need to look at what the masque library does with the buttonData table. I'll post a link to my library as soon as I get to my pc though.

[Duugu]

Originally Posted by Fox536 Ok, well for button data would it be like -- mybutton.floating local ButtonData = { FloatingBG = { "floatingBg"},

I would say Masque expects object references as table values - not names.

Like

local ButtonData = {
 FloatingBG = {<buttonobject>.floatingBg},

or

local ButtonData = {
 FloatingBG = {_G[<buttonobject>:GetName().."floatingBg"]},

or whatever your actual code to reference the button object looks like.

[Phanx]

It also expects the reference directly as the value, not in a sub-table:

ButtonData = {
     FloatingBG = <button>.floatingBG,
}

I'm not sure why you're adding those extra { brackets } around the values.

[Duugu]

Originally Posted by Phanx I'm not sure why you're adding those extra { brackets } around the values.

Oh. I've copied that from the Masque description. :/

[Fox536]

So I need a button table for each button added, that seems like an memory extensive way to do things lol, but I can try that and see if it works.

[Fox536]

Looks like that was the key, thanks for all the help guys.

[Phanx]

Originally Posted by Fox536 So I need a button table for each button added, that seems like an memory extensive way to do things lol, but I can try that and see if it works.

It's probably better in the long run to simply create your action buttons using the standard ActionButtonTemplate, so they have the expected regions with the expected names. Otherwise it's going to be a lot of unnecessary work to make your addon compatible with other addons like Masque that are designed to do stuff with action buttons.