CEGUI (Crazy Eddie's GUI) Forums

I have managed to get a monolithic event handler working (I know CE doesn't like this but I wish to have the GUI pass events to an external program and short of subscribing to every event for every element, I couldn't find a way to do what I wanted).

Anwyay, that's working fine - that isn't the problem. I am now trying to do things the other way round as well. I have the Command Interpreter set up as per this thread. All of the events are being handled by the ScriptingModule implementation that I showed. The issue I have is if I want to pass a string of LUA in from an external program as a string (which I managed to do fine), I am not sure how to execute it, as I have already assigned my "own" script module to System using:Now of course the problem is that I can't just pass LUA to this scripting module's executeString() method as it doesn't do anything with the LUA or anything else (it just returns - see the code in the other thread). I would like to pass that string to a LuaScriptModule instead and have it execute that code. Can I have more than one ScriptModule assigned to System at the same time? Or perhaps I don't even have to use System::getSingleton().setScriptingModule() to change to a different module before passing the LUA in... but I thought I may have to?

I can see a few examples of people who have set up ONE ScriptModule and are then loading .lua FILES in and executing things from within lua, but I want to keep my existing ScriptModule and have a SECOND module that is able to parse/interpret/execute a fragment (e.g. string or char*) of lua code that I send to it. It seems like the executeString() method takes a string argument that will "Execute script code contained in the given CEGUI::String object", however I am not sure how to get this to work with a second type of (Lua)ScriptModule.

If I try to create a LuaScriptModule in a similar way as before, I can't seem to get it to do anything without my app crashing when it hits the following code:


And I don't get the exception printed out, if there is one thrown. I see in DbgView - "MyApp: Before executeString" and then the crash hapens. There doesn't seem to be anything to indicate why this might be in the CEGUI.log either.

Anyone got any ideas what stupid mistake I have made?

TIA

Here is my CEGUI.log:

OK, I found the mistake was that I was not using LuaScriptModule::create() to construct.

When I did that, I started getting an exception thrown that said

exception: CEGUI::ScriptException in file ..\..\..\..\cegui\src\ScriptingModules\LuaScriptModule\CEGUILua.cpp(682) : Unable to execute Lua script string: 'CEGUI.WindowManager:getSingleton():getWindow("MyApp/Quit"):setText("hello")'

So then I tried to use CEGUI::System::getSingleton().setScriptingModule( myluamodule ) to set the scripting module to my Lua one... and, although the other "ScriptingModule" is now not called (my implementation of the non-lua scriptmodule as per the other thread), it appears that the events still remain subscribed, and so events are still being passed to the "CommandInterpretor"!!

SO... This achieves what I wanted. I am not sure whether this is going to cause me construction/destruction issues by just swapping scripting modules at runtime without destroying the previous one, but it seems to work for me...

Is there any way of executing the string without first setting the Syste::ScriptModule to a different module first?

This is what I ended up doing:

I presume the reason why the system can only have a single ScriptModule set is because when the LayoutManager parses an <Event> tag it has no way of determining the ScriptModule to use. The CEGUI API could resolve this by adding a language attribute to <Event> and having all ScriptModules stored in a hashtable internally keyed on their name. However, this is not currently the case. If you really need this, you could try asking CE or Kulik to add this or add it yourself and contribute something back to CEGUI

As far as having to set the SystemScriptModule before executeString will work for that module, again I see no reason why this has to be the case, even though it currently appears to be. I assume this would be a worthy change to CEGUI, in addition to the change mentioned above.

Now, that does not mean you cannot work around the issue using the existing CEGUI code base. If you take a look at the code for setScriptingModule you can see that all this does is basically store an internal pointer to the module, and call destroyBindings and/or createBindings depending on the situation. From this, I will assume that in order to "enable" a scripting module all you need to do is call createBindings on the module. If we take a look at the LuaScriptModule we can see that createBindings is a public function. So, hypothetically, if you are only using executeString (and do not need to switch the SystemScriptModule to bind events from layout files), then you only need to call LuaScriptModule::createBindings in your initialization code and LuaScriptModule::executeString should work.

Ah that's great thanks, calling LuaScriptModule::createBindings first did the trick. Why doesn't this run as part of LuaScriptModule::create()? Surely this would remove the need to either manually call LuaScriptModule::createBindings OR setting the System ScriptingModule first (which also calls createBindings) before being able to use executeString()?

Anyway, that fixed my issue without having to change the SystemScriptModule. Thanks again