View source for Handling Events from Lua

Jump to: navigation, search

You do not have permission to edit this page, for the following reason:

The action you have requested is limited to users in the group: Users.

You can view and copy the source of this page:

Moving the handling of GUI events outside of your project code, and into Lua scripts can add a great deal of flexibilty to your interface. Simple GUI related stuff can be easily prototyped, and modified during testing.

Event handlers in Lua are just regular Lua functions that take one parameter. An CEGUI::EventArgs struct.
The functions you register as event handlers must already be registered with the system, so unless you load them all from your init-script, you will need to load some script files before doing any Lua handled events.

Here we go...


== Loading the script files ==
There are two ways of loading your script files. You can use the C++ interface or you can do it from Lua in your init-script.
The two approaches are very alike, as the Lua version uses a direct binding to the same C++ function.

 CEGUI::System::executeScriptFile(const CEGUI::String& filename, const CEGUI::String& resourceGroup = "");

Obviously this function takes two parameters, a filename and the resource group.
I think most people ignore the last parameter pretty much.

Calling this function with the Lua scripting module correctly attached to CEGUI, will execute the specified Lua script file.
This means that functions etc. declared within these files will be accessible to your program, except of course if they are declared ''local''.

So. From C++ you would do something like this:

 CEGUI::System::getSingleton().executeScriptFile("../datafiles/scripts/guiscript.lua");

If anything goes wrong an exception is thrown.

From Lua you could use this code:

 CEGUI.System:getSingleton():executeScriptFile("../datafiles/scripts/guiscript.lua")

any global code in these script files will also be executed so be sure to manage each execution if necessary (with a counter fx).


== Registering Events to Lua Functions ==
Now that we have our scripts loaded and all, we are ready to bind some events to our scripted handlers.

The function to use when binding scripted events is a little different from the regular C++ one.

 Event::Connection subscribeScriptedEvent(const String& name, const String& subscriber_name);

''name'' is the name of the event you want to subscribe. As usual. ''subscriber_name'' is a string holding the name of the Lua function to bind to the event.

After this call the Lua function specified will be registered as the event handler. And works exactly like the C++ version (except being Lua of course)

Here's a little snippet to bind a PushButton Clicked event to a Lua function:

 CEGUI::PushButton* pb = (CEGUI::PushButton*)CEGUI::WindowManager::getSingleton().createWindow("TaharezLook/Button","lua_powered_button");
 pb->setSize(CEGUI::Size(0.1f,0.1f));
 pb->setPosition(CEGUI::Point(0.1f,0.1f));
 pb->subscribeScriptedEvent("Clicked","luabtn_clicked");
 CEGUI::System::getSingleton().getGUISheet()->addChildWindow(pb);

This code would create a simple TaharezLook button, subscribe the Lua function ''luabtn_clicked'' to its ''Clicked'' event, and finally add it to the current GUI sheet.

Now let's take a look at that Lua event handler:

 function luabtn_clicked(e)
 {
   local we = CEGUI.toWindowEventArgs(e)
   we.window:setText("handled from Lua");
 }

Here we make sure the button text is ''handled from Lua'' when the button is clicked.
We use a utility function:

 CEGUI.toWindowEventArgs(e)

it's obvious what it does, and converters for the other EventArgs class are also available.


now you know how to do stuff with your GUI without writing C++ code.

--[[User:Lindquist|Lindquist]] 17:10, 6 May 2005 (BST)

Template used on this page:

Template:VersionBadge (view source)

Return to Handling Events from Lua.

Retrieved from "http://cegui.org.uk/wiki/Handling_Events_from_Lua"

View source for Handling Events from Lua

Navigation menu

Personal tools

Namespaces

Variants

Views

More

Search

Main

Community

Documentation

Tools