I have been trying to rip out the old and dying/dead ace2 and EBB breaks with an reference to AceLocale-2.2
Well, that's an easy one: it says that the AceLocale-2.2 library was not loaded when your code ran. The errors that follow are all connected to that one; either add back AceLocale-2.2, or change the localization to use AceLocale-3.0 or a non-library localization technique, and all of the errors should go away.
Well, that's an easy one: it says that the AceLocale-2.2 library was not loaded when your code ran. The errors that follow are all connected to that one; either add back AceLocale-2.2, or change the localization to use AceLocale-3.0 or a non-library localization technique, and all of the errors should go away.
Well isn't EBB supposed to be Ace3 nowdays? (Pretty sure i read somewhere that it is Ace3)
Then it shouldn't be breaking when i disable Ace2 should it?
Edit: Pulling the lib version its seems its somewhere in between, using a mix of 2/3 stuff. :(
Can you bring back the option of the 3 click thing where we could right click the buff and it brought the buff to the center and we could click to cancel or right click to hide the giant middle frame again?
Limiting buff cancel to out of combat only wasn't a problem until I noticed I would need to make a separate macro every time I wanted to cancel BoPs or hand of WSG flags. And if I needed to go through all that trouble, I might as well use the default buff frame.
Can you bring back the option of the 3 click thing where we could right click the buff and it brought the buff to the center and we could click to cancel or right click to hide the giant middle frame again?
Limiting buff cancel to out of combat only wasn't a problem until I noticed I would need to make a separate macro every time I wanted to cancel BoPs or hand of WSG flags. And if I needed to go through all that trouble, I might as well use the default buff frame.
Not sure why the incombat "3click" canceling was removed (didn't say anything about that in the changelog) but it might be related to the r163 changes to ooc canceling. Try using r161 or r162 and see if that works (i personally rather use one where i have to use 3click ooc then not being able to click of at all in combat)
Edit:
r162 has no in combat canceling
r161 is a broken file
r160 tosses an error, ooc 3click but no incombat dispelling. So i guess blizz did more changes in last patch to break it again.
1x ElkBuffBars-2.3.0-160\ElkBuffBars.lua:318: BuffFrame:SetPoint(): TemporaryEnchantFrame is dependent on this
AceAddon-2.0-91100 (Ace2):979: in function <Ace2\AceAddon-2.0\AceAddon-2.0.lua:973>
<in C code>: ?
AceEvent-2.0-91097 (Ace2):260: in function `TriggerEvent'
AceEvent-2.0-91097 (Ace2):910: in function <Ace2\AceEvent-2.0\AceEvent-2.0.lua:903>
---
There never was in-combat 3-click canceling so i don't really understand what you are trying to ask... :/ EBB didn't have in-combat canceling since 4.x (and it won't have until I've setup the SecureAuraHeader stuff...)
I was under the impression the reason it was not possible to right click off buffs is because it was impossible to make a macro for it however I just tested it and I a can make a macro to disable a buff. Can someone clarify why or if there is a simple fix now?
It's not possible to right-click off buffs because that action now requires a hardware event and can only be called from secure code.
Macros fit both of those criteria: they must be activated with a hardware event (key press or mouse click) and are secure. You can even type "/cancelaura Some Buff" in the chat frame; the Enter key press counts as a hardware event, and the Blizzard code which handles the "/cancelaura" command is secure.
Right-clicking a buff bar/icon is activated by a hardware event (mouse click) but it is not possible for an addon to create a buff display that is both secure and supports custom filtering/sorting. There are a number of workarounds, like the one EBB uses, but they are all just that -- workarounds. None of them really qualify as "simple", and none of them can work in combat.
Unless Blizzard decides to expand their secure aura templates to support custom filtering (beyond simplistic and useless "cast by me" vs "not cast by me" etc) and sorting, you will never be able to right-click EBB to remove a buff while in combat.
I know close to nothing about coding so forgive me if I come off ignorant, however Satrina buff frames can right click off buffs. Is it not possible to copy or mimic their code and apply it to EBB?
I know close to nothing about coding so forgive me if I come off ignorant, however Satrina buff frames can right click off buffs. Is it not possible to copy or mimic their code and apply it to EBB?
Generally speaking, no. I don't use SBF anymore, so I don't know what it's doing exactly, but there are two possibilities:
1. You can't click off buffs while in combat. This would mean it's using another form of the same workaround EBB is currently using.
2. You can click off buffs while in combat. This would mean it's using Blizzard's new secure aura template, which allows buff cancelling in combat. This would also mean, however, that it has lost all of its advanced filtering and sorting features.
There's no middle ground. Either an addon can use the secure templates and allow right-click buff cancelling in combat, or it can allow custom filtering and sorting. You can't have both.
Limitations of Interactive Frames
- You cannot use filters
- You cannot use frame visibility options
- You cannot set icons or bars to disable right click in the frame
- Names are by default set to activated, and you can't turn that off
- You cannot sort the buffs
So... exactly what I already said. The "solution" SBF is using is really just choosing Option #2 from my last post. EBB is currently in the Option #1 category. There is no magic code that can be copied to enable EBB to keep its current filtering and sorting features *and* give you right-click buff cancelling. It isn't possible. Period.
Unless you're willing to spend some time and effort learning how addons and the WoW API work, there's not really anything I can think of to tell you that will be any clearer than what I've already said.
There is no magic code that can be copied to enable EBB to keep its current filtering and sorting features *and* give you right-click buff cancelling.
There's no "magic code" that I could find either.
Raven's in-combat solution is an auxiliary bar with buttons that can be right-clicked to cancel a specific set of spells that must be defined while out of combat (it is actually a variant on how CancelMyBuffs works using buttons instead of a key bind). It is intended for players that have a small set of spells they regularly need to cancel in combat. While the auxiliary bar looks like one of Raven's icon groups, it is pretty much a separate addon.
I also prototyped a buff-cancelling panel with 40 small buttons (one for each player buff slot) that looked a bit like Decursive in a 40-person raid. With the prototype, when you right-clicked any of your regular bars, the associated small button would light up, and you could then click on the button to cancel a buff in combat. I thought it used way too much screen space for its purpose.
Either an addon can use the secure templates and allow right-click buff cancelling in combat, or it can allow custom filtering and sorting. You can't have both.
I wrote this post both to agree with Phanx completely :) and to respond to the odd view that addon authors either don't want to address this issue or are slow to adopt a solution that others have found. This view has been expressed in general forums and for specific addons. I don't accept this view. You can't simply add generic secure code into a full-featured buff mod.
Do you know if it's possible to create an overflow group? Like lets say I want a maximum of 10 bars high, then I want the rest to overflow into another group, somewhere else on my screen.
My settings are not saving in between sessions/reloads.
Make sure wow is allowed to write to the location where you have the saved variables folder.
This is not uncommon as an issue on vista/win7 computers where WoW has been installed in the default "programs" folder. The so-called security system won't allow wow to make changes to files in the "protected" programs folder unless ran as administrator.
Easiest fix is to move wow away from the programs folder. No need to reinstall, just create a folder for instance c/games/world of warcraft and move the contents of your wow folder there (and redo shortcuts).
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
1x ElkBuffBars-2.3.0-160\ElkBuffBars.lua:38: Cannot find a library instance of AceLocale-2.2. Broker_Group-2.0\libs\AceLibrary\AceLibrary.lua:490: in function `AceLibrary' ElkBuffBars-2.3.0-160\ElkBuffBars.lua:38: in main chunk Locals: self = <table> { GetLibraryVersion = <function> @ Broker_Group\libs\AceLibrary\AceLibrary.lua:670: GetInstance = <function> @ Broker_Group\libs\AceLibrary\AceLibrary.lua:479: IterateLibraries = <function> @ Broker_Group\libs\AceLibrary\AceLibrary.lua:723: Register = <function> @ Broker_Group\libs\AceLibrary\AceLibrary.lua:534: scannedlibs = <table> {} HasInstance = <function> @ Broker_Group\libs\AceLibrary\AceLibrary.lua:446: error = <function> @ Broker_Group\libs\AceLibrary\AceLibrary.lua:75: IsNewVersion = <function> @ Broker_Group\libs\AceLibrary\AceLibrary.lua:417: argCheck = <function> @ Broker_Group\libs\AceLibrary\AceLibrary.lua:129: pcall = <function> @ Broker_Group\libs\AceLibrary\AceLibrary.lua:167: libs = <table> {} frame = <unnamed> {} positions = <table> {} finalizedExternalLibs = <table> {} } major = "AceLocale-2.2" minor = nil data = nil ver = nil argCheck = <function> @ Broker_Group\libs\AceLibrary\AceLibrary.lua:129: TryToLoadStandalone = <function> @ Broker_Group\libs\AceLibrary\AceLibrary.lua:378: LibStub = <table> { NewLibrary = <function> @ Ace3\LibStub\LibStub.lua:11: minors = <table> {} minor = 2 IterateLibraries = <function> @ Ace3\LibStub\LibStub.lua:28: GetLibrary = <function> @ Ace3\LibStub\LibStub.lua:21: libs = <table> {} } _G = <table> { BuyButton11Highlight = BuyButton11Highlight {} ActionButton7FlyoutBorder = ActionButton7FlyoutBorder {} MultiCastActionButton6Cooldown = MultiCastActionButton6Cooldown {} MerchantItem9ItemButtonStock = MerchantItem9ItemButtonStock {} GetTrainerServiceTypeFilter = <function> defined =[C]:-1 UNIT_NAMES_COMBATLOG_TOOLTIP = "Color unit names." KBASE_NUM_FAKE_CATEGORIES = 1 SetTrainerServiceTypeFilter = <function> defined =[C]:-1 BuyEmAllFrameTopTex = BuyEmAllFrameTopTex {} AltoholicAccountSharingOptionsIconNever = AltoholicAccountSharingOptionsIconNever {} TutorialFrameLeft19 = TutorialFrameLeft19 {} MultiCastActionButton2Cooldown = MultiCastActionButton2Cooldown {} ERR_TRADE_EQUIPPED_BAG = "You can't trade equipped bags." PVP_RANK_6_1 = "Corporal" MultiBarLeftButton7 = MultiBarLeftButton7 {} AudioOptionsVoicePanelOutputDeviceDropDownButtonHighlightTexture = AudioOptionsVoicePanelOutputDeviceDropDownButtonHighlightTexture {} InterfaceOptionsDisplayPanelShowAggroPercentageText = InterfaceOptionsDisplayPanelShowAggroPercentageText {} VideoOptionsFrameDefaults = VideoOptionsFrameDefaults {} MerchantItem4AltCurrencyFrameItem1Text = MerchantItem4AltCurrencyFrameItem1Text {} BINDING_NAME_NAMEPLATES = "Show Enemy Name Plates" IsReferAFriendLinked = <function> defined =[C]:-1 MAIL_LETTER_TOOLTIP = "Click to make a permanent copy of this letter." AudioOptionsVoicePanelMicrophoneVolumeThumb = AudioOptionsVoicePanelMicrophoneVolumeThumb {} ERR_NOAMMO_S = "%s" CHAT_CONFIG_OTHER_COMBAT = <table> {} CONSOLIDATED_BUFFS_PER_ROW = 4 TutorialFrameRight19 = TutorialFrameRight19 {} MoneyFrame_OnEvent = <function> @ Interface\FrameXML\MoneyFrame.lua:199: BN_UNABLE_TO_RESOLVE_NAME = "Unable to whisper '%s'. Battle.net may be unavailable." CinematicFrameRaidBossEmoteFrame = CinematicFrameRaidBossEmoteFrame {} InterfaceOptionsCombatTextPanelFCTDropDown_OnClick = <function> @ Interface\FrameXML\InterfaceOptionsPanels.lua:1433: BuyButton6DetailName = BuyButton6DetailName {} LFGTeleport = <function> defined =[C]:-1 SpellButton6Cooldown = SpellButton6Cooldown {} ChannelMemberButton10Name = ChannelMemberButton10Name {} Graphics_QualityText = Graphics_QualityText {} TalentMicroButtonAlertShadowTopLeft = TalentMicroButtonAlertShadowTopLeft {} VOICEMACRO_4_Sc_1_FEMALE = "Help me attack!" MainMenuXPBarDiv8 = MainMenuXPBarDiv8 {} VideoOptionsPanel_C ---Followed by a bunch of
attempt to index global 'ElkBuffBars' (a nil value)
Any plans to move completely to Ace3 anytime soonish?
Well, that's an easy one: it says that the AceLocale-2.2 library was not loaded when your code ran. The errors that follow are all connected to that one; either add back AceLocale-2.2, or change the localization to use AceLocale-3.0 or a non-library localization technique, and all of the errors should go away.
Well isn't EBB supposed to be Ace3 nowdays? (Pretty sure i read somewhere that it is Ace3)
Then it shouldn't be breaking when i disable Ace2 should it?
Edit: Pulling the lib version its seems its somewhere in between, using a mix of 2/3 stuff. :(
If it's throwing errors when Ace2 isn't around, then it seems fairly obvious that the answer to that is "no". :p
Limiting buff cancel to out of combat only wasn't a problem until I noticed I would need to make a separate macro every time I wanted to cancel BoPs or hand of WSG flags. And if I needed to go through all that trouble, I might as well use the default buff frame.
Not sure why the incombat "3click" canceling was removed (didn't say anything about that in the changelog) but it might be related to the r163 changes to ooc canceling. Try using r161 or r162 and see if that works (i personally rather use one where i have to use 3click ooc then not being able to click of at all in combat)
Edit:
r162 has no in combat canceling
r161 is a broken file
r160 tosses an error, ooc 3click but no incombat dispelling. So i guess blizz did more changes in last patch to break it again.
-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorMacros fit both of those criteria: they must be activated with a hardware event (key press or mouse click) and are secure. You can even type "/cancelaura Some Buff" in the chat frame; the Enter key press counts as a hardware event, and the Blizzard code which handles the "/cancelaura" command is secure.
Right-clicking a buff bar/icon is activated by a hardware event (mouse click) but it is not possible for an addon to create a buff display that is both secure and supports custom filtering/sorting. There are a number of workarounds, like the one EBB uses, but they are all just that -- workarounds. None of them really qualify as "simple", and none of them can work in combat.
Unless Blizzard decides to expand their secure aura templates to support custom filtering (beyond simplistic and useless "cast by me" vs "not cast by me" etc) and sorting, you will never be able to right-click EBB to remove a buff while in combat.
Thanks for the response also.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumRead this ^^ again. :)
Generally speaking, no. I don't use SBF anymore, so I don't know what it's doing exactly, but there are two possibilities:
1. You can't click off buffs while in combat. This would mean it's using another form of the same workaround EBB is currently using.
2. You can click off buffs while in combat. This would mean it's using Blizzard's new secure aura template, which allows buff cancelling in combat. This would also mean, however, that it has lost all of its advanced filtering and sorting features.
There's no middle ground. Either an addon can use the secure templates and allow right-click buff cancelling in combat, or it can allow custom filtering and sorting. You can't have both.
-
View User Profile
-
View Posts
-
Send Message
Project Authorprobably this one http://www.wowinterface.com/downloads/info12524-SBF3.2Beta.html
So... exactly what I already said. The "solution" SBF is using is really just choosing Option #2 from my last post. EBB is currently in the Option #1 category. There is no magic code that can be copied to enable EBB to keep its current filtering and sorting features *and* give you right-click buff cancelling. It isn't possible. Period.
Unless you're willing to spend some time and effort learning how addons and the WoW API work, there's not really anything I can think of to tell you that will be any clearer than what I've already said.
-
View User Profile
-
View Posts
-
Send Message
Project AuthorAh. I see. A Beta version that is distinctly separate from the normal download.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThere's no "magic code" that I could find either.
Raven's in-combat solution is an auxiliary bar with buttons that can be right-clicked to cancel a specific set of spells that must be defined while out of combat (it is actually a variant on how CancelMyBuffs works using buttons instead of a key bind). It is intended for players that have a small set of spells they regularly need to cancel in combat. While the auxiliary bar looks like one of Raven's icon groups, it is pretty much a separate addon.
I also prototyped a buff-cancelling panel with 40 small buttons (one for each player buff slot) that looked a bit like Decursive in a 40-person raid. With the prototype, when you right-clicked any of your regular bars, the associated small button would light up, and you could then click on the button to cancel a buff in combat. I thought it used way too much screen space for its purpose.
I wrote this post both to agree with Phanx completely :) and to respond to the odd view that addon authors either don't want to address this issue or are slow to adopt a solution that others have found. This view has been expressed in general forums and for specific addons. I don't accept this view. You can't simply add generic secure code into a full-featured buff mod.
Do you know if it's possible to create an overflow group? Like lets say I want a maximum of 10 bars high, then I want the rest to overflow into another group, somewhere else on my screen.
Any idea?
Thank you so much.
MP
Make sure wow is allowed to write to the location where you have the saved variables folder.
This is not uncommon as an issue on vista/win7 computers where WoW has been installed in the default "programs" folder. The so-called security system won't allow wow to make changes to files in the "protected" programs folder unless ran as administrator.
Easiest fix is to move wow away from the programs folder. No need to reinstall, just create a folder for instance c/games/world of warcraft and move the contents of your wow folder there (and redo shortcuts).