Simple question, before I dive into code to learn myself...
Will LibButtonFacade allow skinning of things other than buttons? I'm pretty sure it can used to skin buff frames, or similiar. But can it be used to skin a frame panel, or status bar frame?
No. LibButtonFacade was written specifically to handle buttons only. However, a future version of "ButtonFacade" (Quoted because the name will be changing) will offer support for a few other UI elements. But of course the rewrite will be happening first.
Well, I'm not sure what else I'm going to add yet since I haven't delved into that aspect too much. For the most part, add-ons will no longer have to save the settings themselves. I've never liked that part of ButtonFacade. >.< But authors need not worry or hurry because it will be backward-compatible.
As I'm logging in to get a raid going I saw there is a buttonfacade update. So I grabbed it. I login and see that none of my skinned buttons are right. Logged out, rolled back to a previous version and everything is back.
I understand you're making some changes, but a smoother transition to the new version would be preferable. Do we need to manually rename the files that stored settings for "buttonfacade"? Isn't a name change a somewhat unnecessary and problematic move?
We just had a patch and I'm still waiting for everything to get back to normal in terms of addon updates. I guess I'll put off updating BF until the new bugs are resolved....I don't have the time or patience to sit and reconfigure everything under a new addon name if that is indeed the problem.
Whether or not the name change was "necessary" is irrelevant. It has no effect on how the settings are saved. The change that caused you to lose your settings was the transition from the add-ons saving their own skins to Masque doing it (which is a good thing). There is no "smooth" transition in this case.
And if having spend 30 seconds reselecting your skin is such a big deal, don't use it.
P.S. You might not want to use alphas if you don't want unexpected issues...
oPie, Raven, and Bartender4 don't appear to be skinnable at all any more. I change skins and the icons might change size, but no borders or anything of the like is applied.
I have tested it briefly on Raven and, with my usual skin (Renaitre Beveled) and the appropriate setting at the bottom of the Defaults panel for coloring borders, it seemed to work fine. I'll give it a more thorough testing with more skins over the next day or so.
This latest update has completely destroyed my Satrina Buff Frames
SBF has been broken for awhile. I am going to write a fix for it, though.
I have tested it briefly on Raven and, with my usual skin (Renaitre Beveled) and the appropriate setting at the bottom of the Defaults panel for coloring borders, it seemed to work fine. I'll give it a more thorough testing with more skins over the next day or so.
Thanks. I'll be running my own tests. I need to see how each add-on is implementing the original ButtonFacade to make sure that I've got it as "compatible" as possible.
To add to the already posted problems... the item count in Dominos is now under the button instead inside of it.
This is an issue with the skin being out of date. I'm going to go ahead and throw in a temporary work around for this until I have a chance to poke the authors or update the skins myself.
what about round button skins? the 'new' ability highlights do not seem to work with the new masqe version?
This is something I've been planning on doing. I just haven't got around to it.
this has had round highlight on round buttons since highlight were introtoduced... but now not work with masque!?
I may just ask him if I can borrow his round texture. :p
so is there any kind of support for round button highlight? or masque authors each have to do that themselves individually?
The plan is to create a "round" animation for those skins and then skin authors will have to flag their skin as being round.
I updated through the Curse Client, I wasn't aware I was using an alpha, till I started checking to see why my text was all wrong.
There is no reason whatsoever for the average user to have alphas installed via the client. They're alphas for a reason. Not trying to be an ass, but that's the reality of it. >.< Just go into the client options and make sure that you have it set to either download Releases or Betas.
There is no reason whatsoever for the average user to have alphas installed via the client. They're alphas for a reason. Not trying to be an ass, but that's the reality of it. >.< Just go into the client options and make sure that you have it set to either download Releases or Betas.
Storm, didn't take you as being an ass, I did have it set to install alphas, forgot to reset it after updating another addon. I've set it to releases only now, but its still showing me to update to r352, but that might be in curse client's cache or something. Thanks for you hard work.
If you don't want the inevitable bug reports, set your project to not package alphas in the first place.
It's not bug reports I have a problem with. I actually had the packager set to not package alphas, but sometimes we have to test our packer settings, which, you know, requires a package to be made. Not that I need to explain myself to you.
Will LibButtonFacade allow skinning of things other than buttons? I'm pretty sure it can used to skin buff frames, or similiar. But can it be used to skin a frame panel, or status bar frame?
Thank You.
JS
I am recoding an existing addon to utilize Ace3 libs and was looking for a skinning engine for the panels, etc.
I guess I can use button facade for the buttons and icons, then later add support for the new LibButtonFacade.
Any tips you can give for coding to easily account for the new lib when released?
If you need help testing anything, let me know, I can add in support now to alleviate double coding where not necessary.
JS
I understand you're making some changes, but a smoother transition to the new version would be preferable. Do we need to manually rename the files that stored settings for "buttonfacade"? Isn't a name change a somewhat unnecessary and problematic move?
We just had a patch and I'm still waiting for everything to get back to normal in terms of addon updates. I guess I'll put off updating BF until the new bugs are resolved....I don't have the time or patience to sit and reconfigure everything under a new addon name if that is indeed the problem.
And if having spend 30 seconds reselecting your skin is such a big deal, don't use it.
P.S. You might not want to use alphas if you don't want unexpected issues...
http://wow.curse.com/downloads/wow-addons/details/button-facade-trinity.aspx
this has had round highlight on round buttons since highlight were introtoduced... but now not work with masque!?
i tried renaitre but i guess its round buttons never worked with the highlight...
so is there any kind of support for round button highlight? or masque authors each have to do that themselves individually?
thanks
I updated through the Curse Client, I wasn't aware I was using an alpha, till I started checking to see why my text was all wrong. :(
Thanks. I'll be running my own tests. I need to see how each add-on is implementing the original ButtonFacade to make sure that I've got it as "compatible" as possible.
This is an issue with the skin being out of date. I'm going to go ahead and throw in a temporary work around for this until I have a chance to poke the authors or update the skins myself.
This is something I've been planning on doing. I just haven't got around to it.
I may just ask him if I can borrow his round texture. :p
The plan is to create a "round" animation for those skins and then skin authors will have to flag their skin as being round.
There is no reason whatsoever for the average user to have alphas installed via the client. They're alphas for a reason. Not trying to be an ass, but that's the reality of it. >.< Just go into the client options and make sure that you have it set to either download Releases or Betas.
While I may not be using the alpha Masque(ButtonFacade) I haven't had any issue(s) skinning Bartender4 with Renaitre, Darion and Vaka.
Storm, didn't take you as being an ass, I did have it set to install alphas, forgot to reset it after updating another addon. I've set it to releases only now, but its still showing me to update to r352, but that might be in curse client's cache or something. Thanks for you hard work.
If you don't want the inevitable bug reports, set your project to not package alphas in the first place.
It's not bug reports I have a problem with. I actually had the packager set to not package alphas, but sometimes we have to test our packer settings, which, you know, requires a package to be made. Not that I need to explain myself to you.