WowAce

What steps will reproduce the problem?
1. checkout quartz3 svn + latest svn of all required libs.
2. start wow with only svn libs and quartz3 svn and buggrabber and bugsack.
3.

What is the expected output? What do you see instead?
i try to configure it and i can see all the sections but im promted with a bug and menus are not showing config content for quartz3
no castbars are shown.
What version of the product are you using?
latest rev on svn

Do you have an error log of what happened?

2009/08/01 12:56:31-11-x7]:
AceConfigDialog-3.0-34:1719: AceConfigRegistry-3.0:ValidateOptionsTable(): Quartz3.args.Swing.args.y.usage: unknown parameter
AceConfigRegistry-3.0-9:42: in function <...-3.0\AceConfigRegistry-3.0\AceConfigRegistry-3.0.lua:37>
AceConfigRegistry-3.0-9:201: in function <...-3.0\AceConfigRegistry-3.0\AceConfigRegistry-3.0.lua:182>
AceConfigRegistry-3.0-9:217: in function <...-3.0\AceConfigRegistry-3.0\AceConfigRegistry-3.0.lua:182>
AceConfigRegistry-3.0-9:217: in function <...-3.0\AceConfigRegistry-3.0\AceConfigRegistry-3.0.lua:182>
AceConfigRegistry-3.0-9:247: in function `ValidateOptionsTable'
AceConfigRegistry-3.0-9:298: in function `app'
AceConfigDialog-3.0-34:1719: in function `Open'
AceConfigDialog-3.0-34:1784: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1782>
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[2]":9: in function <[string "safecall Dispatcher[2]"]:5>
(tail call): ?:
AceGUI-3.0-25 (ace3):305: in function `Fire'
...AceGUI-3.0\widgets\AceGUIWidget-BlizOptionsGroup.lua:67: in function <...AceGUI-3.0\widgets\AceGUIWidget-BlizOptionsGroup.lua:66>:
<in C code>: in function `Show'
Interface\FrameXML\UIOptionsFrame.lua:28: in function `InterfaceOptionsList_DisplayPanel':
Interface\FrameXML\UIOptionsFrame.lua:46: in function `InterfaceOptionsListButton_OnClick':
<string>:"*:OnClick":2: in function <[string "*:OnClick"]:1>

  ---

Please provide any additional information below.

After moving from Quartz to Quartz3 a few days ago, I am seeing very similar behavior. Was this marked invalid because you can't reproduce it? Or because there is a workaround?

This was marked invalid because it was an error from august 2009, while it was in an very unusable state.

Aha! The version I was running was downloaded via WowMatrix a few days ago, but was older than the version posted here. I manually deleted the old one and trashed the prefs, then re-installed the latest code and all is well. Thanks!