I played with the plugin Jazzyfox wrote for TrinketMenu (with some of StormFX's skins which are very cool) and it works very well. I'll likely keep it as a separate plugin.
Also, whenever I login or reloadui, the global level says the current skin is Blizzard instead of whatever it has actually applied.
Right. The data is saved on a per group/button basis (depending on how the add-on saves it, since it's actually the add-on the does the saving, not BF). The "global" option is there simply to make the selection for all the groups at once.
...I played with the plugin Jazzyfox wrote for TrinketMenu (with some of StormFX's skins which are very cool) and it works very well. I'll likely keep it as a separate plugin.
1) Thank goodness you are back Gello. I was starting to dread the day ItemRack broke and I would have to abandon it.
2) For some of us ButtonFacade is a huge improvement over cyCircled. cyCircled continuously broke AutoBar or caused uneccessary lag or any number of stupid things that wasted my time. Furthermore its bassAckwards nature meant its support was always flaky. ButtonFacade just works, and more than that it works appropriately without forcing itself onto me against my will. That is why within 2 or 3 weeks of being told about ButtonFacade cyCircled was kicked to the curb and ButtonFacade adopted as the only skinning option for AutoBar. The amount of code devoted to skinnng dropped to about an 1/8th of what it used to be to "support" cyCircled, and that is without counting the cyCircled module itself.
3) The code and data to support skinning if ButtonFacade is present is very minimal. I would highly recommend just plain supporting it up front.
Not sure if this is the correct place to post this but since it only started once I installed ButtonFacade + Bongos3_ButtonFacade...
Getting quite a few of these errors. Seem to be occurring when I turn off Show Empty Buttons in Bongos:
[2008/05/19 13:55:43-4384-x7]: C stack overflow:
<in C code>: ?
<in C code>: ?
<in C code>: ?
<in C code>: ?
<in C code>: ?
<in C code>: ?
<in C code>: ?
<in C code>: ?
<in C code>: ?
<in C code>: ?
<in C code>: ?
<in C code>: ?
...:
Bongos_AB-1.1\actionBar\button.lua:551: in function `Update'
Bongos_AB-1.1\actionBar\button.lua:323: in function <Interface\AddOns\Bongos_AB\actionBar\button.lua:317>
<in C code>: in function `SetAttribute'
Interface\FrameXML\SecureStateHeader.lua:585: in function <Interface\FrameXML\SecureStateHeader.lua:536>:
Interface\FrameXML\SecureStateHeader.lua:774: in function `SecureStateHeader_Refresh':
Bongos_AB-1.1\actionBar\bar.lua:389: in function `?'
Bongos_AB-1.1\actionBar\bar.lua:1517: in function `ForAllShown'
Bongos_AB-1.1\actionBar\actionBar.lua:289: in function `UpdateShowStates'
Bongos_AB-1.1\config.lua:209: in function `ShowEmptyButtons'
Bongos_Options\actionBar.lua:129: in function <Interface\AddOns\Bongos_Options\actionBar.lua:127>
I get quite a few similar ones probably from different configuration changes. The stacktrace varies but always ends up in a stack overflow after a Bongos Update or UpdateAction function.
Here's one that didn't quite match the pattern though:
[2008/05/19 13:47:41-4384-x120]: C stack overflow:
<in C code>: ?
<in C code>: ?
<in C code>: ?
<in C code>: ?
<in C code>: ?
<in C code>: ?
<in C code>: ?
<in C code>: ?
<in C code>: ?
<in C code>: ?
<in C code>: ?
<in C code>: ?
...:
<in C code>: in function `SetAttribute'
Interface\FrameXML\SecureStateHeader.lua:581: in function <Interface\FrameXML\SecureStateHeader.lua:536>:
Interface\FrameXML\SecureStateHeader.lua:774: in function `SecureStateHeader_Refresh':
Interface\FrameXML\SecureStateHeader.lua:816: in function `SecureStateHeader_OnAttributeChanged':
<string>:"*:OnAttributeChanged":1: in function <[string "*:OnAttributeChanged"]:1>
<in C code>: in function `SetAttribute'
Interface\FrameXML\SecureStateHeader.lua:906: in function `SecureStateHeader_OnAttributeChanged':
<string>:"*:OnAttributeChanged":1: in function <[string "*:OnAttributeChanged"]:1>
<in C code>: in function `SetAttribute'
Interface\FrameXML\SecureStateDriver.lua:98: in function <Interface\FrameXML\SecureStateDriver.lua:79>:
And another:
[2008/05/19 13:47:54-4384-x318]: C stack overflow:
<in C code>: ?
<in C code>: ?
<in C code>: ?
<in C code>: ?
<in C code>: ?
<in C code>: ?
<in C code>: ?
<in C code>: ?
<in C code>: ?
<in C code>: ?
<in C code>: ?
<in C code>: ?
...:
<in C code>: ?
<in C code>: ?
<in C code>: ?
<in C code>: ?
<in C code>: ?
<in C code>: ?
<in C code>: in function `SetNormalTexture'
Bongos_AB-1.1\actionBar\button.lua:133: in function `UpdateNormalTexture'
Bongos_AB-1.1\actionBar\button.lua:543: in function `Update'
Bongos_AB-1.1\actionBar\button.lua:291: in function <Interface\AddOns\Bongos_AB\actionBar\button.lua:275>
Not sure if this is the correct place to post this but since it only started once I installed ButtonFacade + Bongos3_ButtonFacade...
Do me a favor and disable ButtonFacade. If the errors still occur, it is a problem with Bongos. If they stop happening with BF disabled, let me know and I'll take a look.
Do me a favor and disable ButtonFacade. If the errors still occur, it is a problem with Bongos. If they stop happening with BF disabled, let me know and I'll take a look.
This was the first time I was using ButtonFacade. Up until today I have just been using Bongos without any skinning mod and I've never seen these errors before.
This is the error i get when I select autobar as the buttons i want to skin
...Ons\ButtonFacade\LibButtonFacade\LibButtonFacade.lua:271: attempt to index local 'Color' (a nil value)
Count: 2
Call Stack:
(tail call): ?
...Ons\ButtonFacade\LibButtonFacade\LibButtonFacade.lua:271: in function <...Ons\ButtonFacade\LibButtonFacade\LibButtonFacade.lua:270>
(tail call): ?
(tail call): ?
...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:241: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:190>
...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1075: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:924>
...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1287: in function `FeedGroup'
...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1208: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1187>
(tail call): ?
[C]: ?
[string "safecall Dispatcher[3]"]:9: in function <[string "safecall Dispatcher[3]"]:5>
(tail call): ?
Interface\AddOns\Ace3\AceGUI-3.0\AceGUI-3.0.lua:257: in function `Fire'
...s\Ace3\AceGUI-3.0\widgets\AceGUIWidget-TreeGroup.lua:409: in function `SetSelected'
...s\Ace3\AceGUI-3.0\widgets\AceGUIWidget-TreeGroup.lua:92: in function <...s\Ace3\AceGUI-3.0\widgets\AceGUIWidget-TreeGroup.lua:88>
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI played with the plugin Jazzyfox wrote for TrinketMenu (with some of StormFX's skins which are very cool) and it works very well. I'll likely keep it as a separate plugin.
-
View User Profile
-
View Posts
-
Send Message
Curse Premium:D
Edit: Also, whenever I login or reloadui, the global level says the current skin is Blizzard instead of whatever it has actually applied.
I noticed this too, and will be fixing it soon.
As has been stated previously, higher level groups will generally not save settings.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumRight. The data is saved on a per group/button basis (depending on how the add-on saves it, since it's actually the add-on the does the saving, not BF). The "global" option is there simply to make the selection for all the groups at once.
1) Thank goodness you are back Gello. I was starting to dread the day ItemRack broke and I would have to abandon it.
2) For some of us ButtonFacade is a huge improvement over cyCircled. cyCircled continuously broke AutoBar or caused uneccessary lag or any number of stupid things that wasted my time. Furthermore its bassAckwards nature meant its support was always flaky. ButtonFacade just works, and more than that it works appropriately without forcing itself onto me against my will. That is why within 2 or 3 weeks of being told about ButtonFacade cyCircled was kicked to the curb and ButtonFacade adopted as the only skinning option for AutoBar. The amount of code devoted to skinnng dropped to about an 1/8th of what it used to be to "support" cyCircled, and that is without counting the cyCircled module itself.
3) The code and data to support skinning if ButtonFacade is present is very minimal. I would highly recommend just plain supporting it up front.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI have a problem : i use ButtonFacade_Caith
i modify the color of "Normal Border " but after a log out - log in or /reloadui i have the default color "dark gray"
Did i miss something ?
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThe author of the bar mod you're using has not implemented saving color settings yet.
oki thank you :)
Forgot to mention, Revision 74422 has this bug fixed.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumGetting quite a few of these errors. Seem to be occurring when I turn off Show Empty Buttons in Bongos:
I get quite a few similar ones probably from different configuration changes. The stacktrace varies but always ends up in a stack overflow after a Bongos Update or UpdateAction function.
Here's one that didn't quite match the pattern though:
And another:
Do me a favor and disable ButtonFacade. If the errors still occur, it is a problem with Bongos. If they stop happening with BF disabled, let me know and I'll take a look.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThis was the first time I was using ButtonFacade. Up until today I have just been using Bongos without any skinning mod and I've never seen these errors before.
...Ons\ButtonFacade\LibButtonFacade\LibButtonFacade.lua:271: attempt to index local 'Color' (a nil value)
Count: 2
Call Stack:
(tail call): ?
...Ons\ButtonFacade\LibButtonFacade\LibButtonFacade.lua:271: in function <...Ons\ButtonFacade\LibButtonFacade\LibButtonFacade.lua:270>
(tail call): ?
(tail call): ?
...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:241: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:190>
...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1075: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:924>
...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1287: in function `FeedGroup'
...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1208: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1187>
(tail call): ?
[C]: ?
[string "safecall Dispatcher[3]"]:9: in function <[string "safecall Dispatcher[3]"]:5>
(tail call): ?
Interface\AddOns\Ace3\AceGUI-3.0\AceGUI-3.0.lua:257: in function `Fire'
...s\Ace3\AceGUI-3.0\widgets\AceGUIWidget-TreeGroup.lua:409: in function `SetSelected'
...s\Ace3\AceGUI-3.0\widgets\AceGUIWidget-TreeGroup.lua:92: in function <...s\Ace3\AceGUI-3.0\widgets\AceGUIWidget-TreeGroup.lua:88>
Do you have the latest version of AutoBar? That is post the version you are using...
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumError:
....Localozation\enUS:1: Cannot find a lib instance of "AceLocale-3,0"
I use the german client