Yeah.. i can't access via the LDB button either, i get the following error:
[2008/12/28 16:22:37-4230-x1]: AceConfigDialog-3.0-25:1654: AceConfigRegistry-3.0:ValidateOptionsTable(): AutoBar.args.buttons.args[AutoBarCustomButtonPet Food] - key name contained spaces (or control characters)
AceConfigRegistry-3.0-6:46: in function <...-3.0\AceConfigRegistry-3.0\AceConfigRegistry-3.0.lua:41>
AceConfigRegistry-3.0-6:168: in function <...-3.0\AceConfigRegistry-3.0\AceConfigRegistry-3.0.lua:162>
AceConfigRegistry-3.0-6:220: in function <...-3.0\AceConfigRegistry-3.0\AceConfigRegistry-3.0.lua:186>
AceConfigRegistry-3.0-6:221: in function <...-3.0\AceConfigRegistry-3.0\AceConfigRegistry-3.0.lua:186>
AceConfigRegistry-3.0-6:252: in function `ValidateOptionsTable'
AceConfigRegistry-3.0-6:298: in function `app'
AceConfigDialog-3.0-25:1654: in function `Open'
AutoBar-v3.00.03.12 beta.718\AutoBarOptions.lua:164: in function `func'
Dewdrop-2.0-90320 (Skinner):732: in function <...rface\AddOns\Skinner\libs\DewdropLib\Dewdrop-2.0.lua:671>
Looks like you have added a custom button, with a name of "Pet Food" - button names shouldnt have spaces in them.. best bet is to delete your SavedVars (or fix the problem in them manually, not for the faint of heart)
Toady.. the latest beta on wowace is kinda broken for embedded users, embeds.xml is missing load line for AceConsole-3.0 - and when added manually, said library doesn't load anyway.. Attempting further debugging now..
Toady.. the latest beta on wowace is kinda broken for embedded users, embeds.xml is missing load line for AceConsole-3.0 - and when added manually, said library doesn't load anyway.. Attempting further debugging now..
Looks like you have added a custom button, with a name of "Pet Food" - button names shouldnt have spaces in them.. best bet is to delete your SavedVars (or fix the problem in them manually, not for the faint of heart)
break19
I haven't added any new buttons for a long time, so is this restriction a recent one?
And you are absolutely right. Editing the saved vars file to amend all of the button names to remove spaces has fixed the issue. There were five!!
Ok, unfortunately I forgot to finish and enable code to upgrade names with spaces to names without spaces and instead checked in so I can continue coding while traveling. I will be home Monday where coding is easier. I may be able to test and check in some code later today but no promises. The restriction is a result of how I implemented things in Ace3.
Looks like I cut out the old Ace2 way of doing this and botched the Ace3 way. /atb and /autobar should both work again, and /atb config should be another way to bring up the config. Note that this is now using the reworked Ace3 config and may not be as it was previously.
Also, as a recap, the clicking way to get the config up is to use the minimap button or to use some kind of Data Broker mod like Fortress or SexyMap etc.
Ok, unfortunately I forgot to finish and enable code to upgrade names with spaces to names without spaces and instead checked in so I can continue coding while traveling. I will be home Monday where coding is easier. I may be able to test and check in some code later today but no promises. The restriction is a result of how I implemented things in Ace3.
It's np at all, Azethoth, I was just happy to be able to fix the issue without you having to do anything specific. Take your time, we all appreciate a great addon.
ok so it seems every time i log in on my horde toons autobar is blank till i kill something? ive redownloaded it, reinstalled it, deleted wtf files, the works far as i know of. On my ally auctioneer toon autobar shows up instantly.
I'm having trougblw with AutoBar as of v698 that's currently available through Wowmatrix. When I load up my main (only) character there's an error and no autobar. Unfortunately unlike procman9000 killing stuff doesn't bring it back.
Anyone have any idea what I should do to get it working again?
I'm getting an error with the beta from Curse.This starts when after a clean install I move the bar....and funny thing is, after I get it ...it persists through next log in.
[2009/01/02 09:49:44-96-x1]: AutoBar-v3.00.02.09 beta.696\Core.lua:1388: attempt to call method 'OpenMenu' (a nil value)
Waterfall-1.0-90125 (AutoBar):2876: in function <...\AddOns\AutoBar\libs\Waterfall-1.0\Waterfall-1.0.lua:2863>
v3.00.02.13 beta (r726)
-- Fix ButtonFacade options call to its new Blizzard Panel interface
-- Horn of Winter added to class buffs
-- AutoBar version info added to the AutoBar tab of options.
-- DK potion added.
-- Various quest items etc.
This fixes the problem Fred ran into with bringing up ButtonFacade options.
Thank you so much for fixing this!
Kind regards
X-buZZ
[2008/12/28 16:22:37-4230-x1]: AceConfigDialog-3.0-25:1654: AceConfigRegistry-3.0:ValidateOptionsTable(): AutoBar.args.buttons.args[AutoBarCustomButtonPet Food] - key name contained spaces (or control characters)
AceConfigRegistry-3.0-6:46: in function <...-3.0\AceConfigRegistry-3.0\AceConfigRegistry-3.0.lua:41>
AceConfigRegistry-3.0-6:168: in function <...-3.0\AceConfigRegistry-3.0\AceConfigRegistry-3.0.lua:162>
AceConfigRegistry-3.0-6:220: in function <...-3.0\AceConfigRegistry-3.0\AceConfigRegistry-3.0.lua:186>
AceConfigRegistry-3.0-6:221: in function <...-3.0\AceConfigRegistry-3.0\AceConfigRegistry-3.0.lua:186>
AceConfigRegistry-3.0-6:252: in function `ValidateOptionsTable'
AceConfigRegistry-3.0-6:298: in function `app'
AceConfigDialog-3.0-25:1654: in function `Open'
AutoBar-v3.00.03.12 beta.718\AutoBarOptions.lua:164: in function `func'
Dewdrop-2.0-90320 (Skinner):732: in function <...rface\AddOns\Skinner\libs\DewdropLib\Dewdrop-2.0.lua:671>
break19
My bad on that, I totally forgot about embeds.
I haven't added any new buttons for a long time, so is this restriction a recent one?
Ok, unfortunately I forgot to finish and enable code to upgrade names with spaces to names without spaces and instead checked in so I can continue coding while traveling. I will be home Monday where coding is easier. I may be able to test and check in some code later today but no promises. The restriction is a result of how I implemented things in Ace3.
nevcariel was kind enough to check in a fix while I was eating and drinking and being merry. I tagged a new beta version to pick that up.
Looks like I cut out the old Ace2 way of doing this and botched the Ace3 way. /atb and /autobar should both work again, and /atb config should be another way to bring up the config. Note that this is now using the reworked Ace3 config and may not be as it was previously.
Also, as a recap, the clicking way to get the config up is to use the minimap button or to use some kind of Data Broker mod like Fortress or SexyMap etc.
It's np at all, Azethoth, I was just happy to be able to fix the issue without you having to do anything specific. Take your time, we all appreciate a great addon.
Anyone have any idea what I should do to get it working again?
Here's the error:
Actually kill something or enter combat? Check your fadeout settings...
If that is not your issue then disable all other mods etc. as per the debug faq http://code.google.com/p/autobar/wiki/ErrorsBugs
Stop using that garbage. Either use the curse updater, or manually update to the alpha version here: http://www.wowace.com/projects/auto-bar/files/
Gonna give Wowmatrix the arse and switch over to Curse.
[2009/01/02 09:49:44-96-x1]: AutoBar-v3.00.02.09 beta.696\Core.lua:1388: attempt to call method 'OpenMenu' (a nil value)
Waterfall-1.0-90125 (AutoBar):2876: in function <...\AddOns\AutoBar\libs\Waterfall-1.0\Waterfall-1.0.lua:2863>
---
-- Fix ButtonFacade options call to its new Blizzard Panel interface
-- Horn of Winter added to class buffs
-- AutoBar version info added to the AutoBar tab of options.
-- DK potion added.
-- Various quest items etc.
This fixes the problem Fred ran into with bringing up ButtonFacade options.
Does Drag&Drop work? I've enabled the option for it on a bar and i try dragging a spell from my spell book onto the bar but nothing happens.
Edit: How do i remove the minimap icon