DefaultResourceProvider::load

[granx]

Hi,
I just built the CELayoutEditor against with all the latest dependencie releases and CVS checkouts. I have an 'error' dialog box that opens imeediately upon running the editor. It says:
DefaultResourceProvider::load - ../datafiles/imagesets/Imageset.xsd does not exist.

I had it in another directory earlier, and it said:
DefaultResourceProvider::load - ../datafiles/layouts/GUILayout.xsd does not exist.

But that was before I moved it to cegui_mk2\Samples\CELayoutEditor.

So, where is the recommended placement of this project when building and running, and how can I fix my current error?

I would be happy to add documentation to the wiki, unless it already exists and I overlooked it. Will someone help me to get started?

Thanks, -John

[granx]

Ok...
I saw that the .exe was created in CELayoutEditor\bin\Debug , so I decided to try launching from that location, rather than using the VC++ debugger from the CELayoutEditor\vc++6 folder.

This has fixed that problem.

Now when I launch the Release build, it does not allow me to find any files when I use the Editor's "Open Layout" dialog. I can easily browse directories, but the pattern being searched is .xml, and all my sample files have extensions of .tga, .imageset, .xsd, and .scheme.

However, included in the Debug build folder is a demolayout.xml. The browser finds this, and attempts to load it. As soon as this happens, an error dialog appears and reports:
GUILayout_xmlHandler::startElement - layout loading has been aborted since no WindowFactory is available for 'WindowsLook/FrameWindow' objects.

So, I click 'OK' and return to examining the source code.

Does this mean the .xml file is not well formed? If so, is there any documentation for the layout? Or is this defined in the .scheme files? I'll check there now...

Until later -

[granx]

Yep...
It appears that this .xml file was trying to use an experimental case where more than one 'Look' was being used. I don't know if that was the problem, or if there was no .scheme describing the other look. Either way, the .xml layout file was not being parsed and was causing the file to be treated as invalid.

So, I removed that tag, and voila! I am designing GUIs!!! I caused the program to crash when I tried to save my own layout, but hey, I am getting a feel for how this library and application work, and I like it.

Thanks for the nice tool guys, and tell me how I can help to improve it.

[scriptkid]

Hello Granx,

sorry you had to solve all those problems on your own! I haven't logged on for some days.

You come up with an interesting problem indeed. I will try to add a post-build step which copies the .exe to the correct folder.

And the sample layout indeed used both "looks", which should be available in your bin folder as well.

I can advise to download the installer, or -if you want to stick with the sources- install it and copy the dll's and stuff to make sure you're in sync with what the sources were linked too.

Finally, the xml pattern when opening layouts is correct, since the editor only edits the layout files. Not your schemes or images.

Good luck!