UI Designer broken with 1.9

[solariz]

Hi,

this is my First post so I wan't to start with a big "Thank You" for bringing this superb development tool to us !


Now to the point. After the patch (1.9) the FrameXML folder was renamed to framexml.old after I removed this and installed the CustomInterfaceKit new the UI Designer is running again but I can't open any UI all the templates for buttons and so on are not recognized.

Also I can't start to generate a new Form all Templates are missing.

Any Idea what I have to do to fix this behaivior ?


Thank's alot !

[Nulkris]

First up, thanks for the support.

Anyway, I would suggest uninstalling what you have, then installing the latest nightly build (http://wowuides.wowinterface.com/nb/...1.0.200.4f.msi). Now you do not need the files from the custom interface kit, so go to your Interface directory and delete everything except the Addons directory. Run it and see if its any better (it works fine for me with that code).

[solariz]

Hi,
I'm now at home and tryed out but I'm sorry to report that this isn't working
What I have done:

1. Go to my WOW Folder and cleaned up the interface dir. only dir left is "Addons"
2. Uninstalled my current installed UI Designer version
3. Downloaded the version you posted
4. Installed this version
5. Launched
After the launch the Application laods now the XML's (status bar) this takes a time like i'm used to.
6. Loaded my Project (completly generated with UI Designer)
7. Double click on the Main Form (UI)
Now a Popup appears which ask's me which Skin I would like to use. [Screenshot]
8. I select "default" (Notice that the Toolbox is empty)
9. My form appears but totaly broken [Screenshot ]


;(

I Uploaded my AddOn you can [download ] it if you think it is the reason. But I think not because even If I startup a new project my Toolbox is empty so maybe it have to do something with a imcompatibility of the skins ?

Thanks again for Help.

[solariz]

Ok I got it. It is the checking of bliz xml files ui.xsd. If I turn this off everythings seems to be fine.

[Xee]

I had the same problem and your last suggestion of unchecking the Verify Blizzard XML files worked!