I gain memory with bartender (bt3 : ~420k, bt4 : ~236k), but no with buttonfacade (cyC : ~256k, bf : ~357k and ~600k after config).
You use embedded libraries. Since "B" comes early in the alphabet, Bartender and ButtonFacade both load very early (if not first). The copies of libraries embedded in Bartender and ButtonFacade are used not only by Bartender and ButtonFacade, but by all other addons that load after them. This means that the memory and CPU use of other addons using those libraries is attributed to Bartender and/or ButtonFacade by in-game performance profiling functions. As a result, any performance data gathered for addons that use embedded libraries are totally meaningless. There are dozens, if not hundreds, of posts explaining this in great detail all over these forums. If you're interested in learning more about this subject, I recommend you look around for some of them.
Basically, if you want to see the real numbers, run your addons with standalone libraries. If you want to use embedded libraries, the numbers you will see are wrong.
Open the lua file of the skin, and edit the alpha on AutoCastable :)
There is no aplha anywhere hear any of the 2 AutoCastable entries :/
(there actually isn't a single alpha entiry at all in the lua, and im not comfortable enough with lua to just add stuff like that without some very specific info as to where and how to make the edit.)
Well, I just checked my numbers, and on my main character, ButtonFacade occupies 227kb of memory on load, and 342kb after playing around with the configuration menus. However, logging in with only ButtonFacade enabled, no skins, and no addons that support ButtonFacade, it occupes 96kb of memory before and after playing with the configuration menus. I suspect your higher numbers mean that either your addons that register elements with ButtonFacade are more numerous than mine (I use InfiniBar, Poppins, and Satrina Buff Frame) or they register more individual elements, both possibilities adding more data for the ButtonFacade engine to keep track of and hold in memory.
At no time during testing did I see any increase in memory outside of configuration, so unless your machine is 20 years old and struggling to run WoW already, I would say that even 600kb or more in static memory will have no performance impact whatsoever, and is simply a side effect of ButtonFacade's more "friendly" skinning tactics, as opposed to cyCircled's one-size-fits-all brute-force hack method.
ButtonFacade uses a different framework (and different libraries) than cyCircled. ButtonFacade does things differently than cyCircled does. ButtonFacade =/= cyCircled. Unless you are having issues with performance, pay no attention to memory usage. It also may be like what Phanx says - it could be the result of the addons that use ButtonFacade.
Well, here's how cyCircled works:
Player loads BarModX and cyCircled. cyCircled supports BarModX, meaning that someone, probably not the author of BarModX, added a file in the cyCircled addon that generated a list of buttons visible from BarModX and handed that list to cyCircled. Then, without knowing anything about those buttons aside from their names, cyCircled attempted to apply the skin textures, which worked to varying degrees in different addons. No information whatsoever is passed between cyCircled and BarModX, and BarModX is not aware that it's been skinned or how. The author of BarModX has no control over how cyCircled skins its buttons.
Here's how ButtonFacade works:
Player loads BarModX and ButtonFacade. BarModX supports ButtonFacade (note this is the opposite order from above), meaning that the author of BarModX explicitly added code to compile a list of each button created by BarModX, along with some information about each of those buttons, and hands that list to ButtonFacade. ButtonFacade then skins each button using the information provided by BarModX. All of the information passed to ButtonFacade is stored in memory under ButtonFacade's name. BarModX is aware that ButtonFacade has skinned it, and knows exactly how this was done because it, not ButtonFacade, specified how it should be skinned. The author of BarModX has complete control over how ButtonFacade skins its buttons.
Knowing that difference, it makes sense that cyCircled occupies the same amount of memory whether it's skinning no addons or 50 addons, whereas ButtonFacade occupies very little memory if it's skinning no addons (basically just enough to hold a registry of available skins and a GUI) but much more memory if it's skinning 50 addons. cyCircled was like those "tech support" people we all know and hate who send form letters that may or may not address your actual question; ButtonFacade is like those rare souls who actually have the time to respond individually to your question and give you exactly the answer you need.
Thanks for the detailed reply. That was better than the stock "you're running embedded libraries".
Actually, mine was non-standard, as I said "If you're running embedded libraries...". :P As Phanx mentioned, in some cases, libraries will make it look like a mod is using more memory than it is. In the case of BF, a mod can actually make BF look like it's using more depending on how the add-on author coded it.
In the case of BF, a mod can actually make BF look like it's using more depending on how the add-on author coded it.
Actually, an addon won't just make BF look like it's using more memory, it will be using more memory. However, the additional memory is a completely static registry of "stuff to skin" and should have no performance impact on any machine capable of running WoW reasonably well.
i tryed first to use the cyCircled mod to change the skin of my bongos2 action bar and it didn't work...and i see that clickin right mouse button on the minimap tracker of cycircled the menu didn't show me either the name of my action bar addon (bongos) below the voice "elements"
so i'm triyng button facade but doesn't work...my action buttons it's still the same...no matter what i try and it doesn't send me any UI error message
I'm pretty sure there is no support for ButtonFacade in Bongos2.
ButtonFacade does not actively support addons. Addons themselves must implement support for the ButtonFacade system by registering their buttons with ButtonFacade.
Check the description of the addon you want to use (in this case, Bongos2) to find out if it supports ButtonFacade. If you can't find any information, you might ask the addon's author to add support. However, in your case, the author of Bongos2 is no longer developing (or probably supporting) Bongos2; instead, he has moved on to his new bar addon, Dominos. You might take a look at it to see if it will meet your bar addon needs.