Can't add new buttons or bars

[GoogleCodeExporter]

I get an error whenever I click the button labeled 'new', be it for adding
a new bar or for a new button.  The button list dropdown in the
corresponding dialog does not populate.  That goes toward explaining the
behavior for the button, but not for the same behavior when trying to add a
new bar.

Attempt history:
Downloaded latest version from google code.
Error occurred (and configuration was reset; I had been using 2.03.00.32).  
Deleted files, including external folder for waterfall and for dewdrop. 
From this point forward, both of those are only present in the
autobar\libs\ path.
Redownloaded most recent version of autobar off SVN at wowace, r74673.3,
termed 2.04.01.52 beta in the toc file.  
Error still happened.
Used wowaceupdater with only 'default mode with externals' checked on left
hand side.  Error still present.  Used wowaceupdater with auto dependency
download and unpack enabled as well.  
Error still present.

Installed latest versions of bugsack and buggrabber, logged in with
different account, all addons disabled except autobar, bugsack, and
buggrabber.  Error still present, as follows:

Fresh login, only autobar, bugsack and buggrabber loaded, attempting to add
a new bar through the config menu, error occurs when pressing the 'new' button:
[2008/05/21 14:57:57-1-x1]: AutoBar-2.04.01.52
beta.74630\AutoBarClassBar.lua:903: attempt to index field 'barList' (a nil
value)
AutoBar-2.04.01.52 beta.74630\AutoBarClassBar.lua:924: in function `GetNewName'
AutoBar-2.04.01.52 beta.74630\AutoBarOptions.lua:1390: in function `func'
Waterfall-1.0-71942 (AutoBar):2871: in function
<...\AddOns\AutoBar\libs\Waterfall-1.0\Waterfall-1.0.lua:2858>

Alternatively, on a fresh login, while attempting to add a button to a bar
(the 'extras' bar, I think):
[2008/05/21 14:58:49-1-x1]: AutoBar-2.04.01.52
beta.74630\AutoBarClassButton.lua:1130: attempt to index field 'buttonList'
(a nil value)
AutoBar-2.04.01.52 beta.74630\AutoBarClassButton.lua:1151: in function
`GetNewName'
AutoBar-2.04.01.52 beta.74630\AutoBarOptions.lua:1480: in function `func'
Waterfall-1.0-71942 (AutoBar):2871: in function
<...\AddOns\AutoBar\libs\Waterfall-1.0\Waterfall-1.0.lua:2858>

Just looking at the filenames I find it surprising the error is always in
classbar, whether I'm trying to add a new bar, or add a button to any bar
(I explicitly tested extra, default, and class-specific, no difference).

Original issue reported on code.google.com by draper.b...@gmail.com on 21 May 2008 at 8:15

[GoogleCodeExporter]

Oh, for what it's worth, I can drag buttons around between the bars, I just 
can't add
a new one.  

And by 'configuration reset' I mean the contents of the bars and their 
positions.  My
old custom categories still exist in the config menu.  None of my prior custom
buttons do.  I'm trying to re-add them the same way I used to, but it's failing.

Original comment by draper.b...@gmail.com on 21 May 2008 at 8:16

[GoogleCodeExporter]

Have now also tried complete uninstall/reinstall of all mods handled by 
wowaceupdater
just to make sure it wasn't a problem with externals.  No change, still testing
running only autobar/autobarconfig/bugsack/buggrabber.

Original comment by draper.b...@gmail.com on 21 May 2008 at 8:25

[GoogleCodeExporter]

And for what it's worth, no problem doing new category, and no problem doing 
new item
in category (both 'new' and 'new macro' act as expected).

Original comment by draper.b...@gmail.com on 21 May 2008 at 8:27

[GoogleCodeExporter]

Attempting to do new button or bar in the cascading right-click menus produces 
same
error as in first post.

Original comment by draper.b...@gmail.com on 21 May 2008 at 8:31

[GoogleCodeExporter]

Mmm, well I am able to to add new bars as well as buttons.  It sounds like 
there is 
something wrong with your saved variables.  There are instructions for how to 
reset 
them in the FAQ as well as saving them off.  Do save them off first.  If they 
fix 
the issue I want to take a look at them

Original comment by dirk.bes...@gmail.com on 22 May 2008 at 1:34

• Changed state: NeedInfo

[GoogleCodeExporter]

Deleting them does fix the issue.

Attached are two different versions, from two accounts, distinguishable most 
easily
at the bottom - one mentions character Kateli (a warlock), the other, smaller 
one
mentions Kaiki (a warrior).

The problem happens with both these characters, and the most obvious culprit 
would be
the blank 'barlist' and 'buttonlist' under the character-specific settings at 
the
end.  At first I though I ruled that out - using the Kaiki savedvars, the 
problem
also happens with the other characters on that account (a rogue Arackus and a 
warrior
Onaya).  

Additionally, I tried simply deleting the entire
["chars"] = {
        ["Kaiki - Llane"] = {
            ["buttonDataList"] = {
            },
            ["barList"] = {
            },
            ["buttonList"] = {
            },
        },
    },
section, which did not solve the problem.  At that point I discovered that a new
instance of that section would end up added to the file after logging in with 
any
character.

So, something about the preexisting savedvars file is causing it to create those
empty lists, which sure seem to be the problem.  Whatever it is doesn't happen 
with a
fresh savedvars file.

Original comment by draper.b...@gmail.com on 22 May 2008 at 3:01

Attachments:

• AutoBar.lua
• AutoBar.lua

[GoogleCodeExporter]

Err, correction, last line - doesn't happen when it creates a fresh savedvars 
file
when none exists.

Original comment by draper.b...@gmail.com on 22 May 2008 at 3:02

[GoogleCodeExporter]

Here.  I found a backup I'd made of my savedvars.  Using this file also 
produces the
bug.  However, it totally lacks the blank barlist/buttonlist section, at least 
until
it's used by the current version of autobar.  Definitely makes it seem like 
something
isn't getting parsed correctly.

Original comment by draper.b...@gmail.com on 22 May 2008 at 3:15

Attachments:

• AutoBar.lua

[GoogleCodeExporter]

Aha awesome.  The first 2 files let me find and reproduce the bug.  Basically 
the 
error is if you have an older version then start using the new one but have not 
used 
it on all characters yet.  Each character / class needs to have barList and 
buttonList in it, even if empty.  However unvisited old characters are preset 
but 
have only the old bars in them.  This then leads to the bug.  If you log in on 
the 
paladin in this case it will "fix" the issue.  Also you can reset the saved 
vars for 
that server.  See the FAQ for how.  Meanwhile I will add code to delete 
character & 
class data that only have the old "bars" in them.  r75121

Original comment by dirk.bes...@gmail.com on 25 May 2008 at 6:59

• Changed state: FixWowAce