CEGUI (Crazy Eddie's GUI) Forums

Hello,
I have written a ScriptModule which provides no functionality. It is just enough to compile. I am specifying it when initializing the System singleton along with the renderer. I don't know what effect this has on the System, but it is causing a crash during initialization now. The crash occurs during initialization of the System, however an exception is throw from CEGUIDefaultResourceProvider.cpp. Here is that code:


I was expecting my new usage of the ScriptModule to not be so intrusive. Is this a poor assumption? If I don't specify the ScriptModule, and the only constructor argument is the renderer, it runs fine. Here is how I initialize the System:


and here is my ?harmless? ScriptModule:


By the way, once I can get the System intialized without crashing, which of the virtual function(s) should I implement to handle (xml defined) Event tags, given a known 'registry' of application callbacks?

Thanks, -granx

Hi,

What's the exception that's getting thrown?

The method that gets called via the internal <Event> mapping system is:


So, this is the one where you want to put your dispatcher code.

What's the exception that's getting thrown?

The exception is: CEGUI::InvalidRequestException @ 0x0012ccec

... is the one where you want to put your dispatcher code.

Thanks!

granx wrote:

What's the exception that's getting thrown?

The exception is: CEGUI::InvalidRequestException @ 0x0012ccec

I realised that I missed that after posting; I was too busy laughing at myself to change it

The problem is it's trying to load a config file named "cegui.config", this is an XML file which specifies some options. I thought this was optional, though now I see that it's not when using a ScriptModule (yes, I know I wrote the damned thing, but I forgot about this).

Try putting the following in cegui.config and saving it (and also 'CEGUIConfig.xsd' from XMLRefSchema if you're using Xerces) somewhere the resource provider will find it...



Sorry about forgetting that. Really this should have been made optional, I don't recall if there was a reason it's not

CE,
Thanks again. That fixed it. Consider this thread closed.
p.s. don't forget to include that option in the next release please
-granx

I'll need to consider the optional config thing a while. The problem is that I implemented it via a default parameter, so other peoples code may be relying upon this; i.e. they have the same code as you do, except they require the config to be automatically bought in. Having said that, this is non-obvious behaviour, so I may well change it (it will not get done for 0.3.0 as that's almost certainly getting packaged up today).

Why must the ScriptModule be specified during construction of the System? Sorry, I was just curious. From my new experience with the ScriptModule, it seems that its sole purpose is to handle an Event, and thus, until a valid ScriptModule is provided, the System should be behaving as it does when the ScriptModule* member is left invalid. Which implies that you could specify a ScriptModule at any point during the life of an application. Therefore, I beleive a System::setScriptingModule(ScriptModule* s) function should be added to the API. What do you think?

It's possible to run start-up and shutdown scripts, specified in the cegui.config file. Because of this, it's required to pass the ScriptModule in at the earliest possible moment to enable the start-up script to be run. This arrangement enables an entire app to be implemented via script, except the initial creation of the Renderer, ScriptModule, and CEGUI::System objects (which is how the old Demo 8 was done).

I think I got around that by using a different overloaded constructor and passing NULL as the configuration file when I created System with a scripting module.