Sandbox/GUI/Getting Started
So, it looks like I can't exclude this page/section from the search engine as I had hoped. I wanted to put this in a sandbox so that it wouldn't be published without some proper review. I guess for now
DON'T TRUST ANYTHING YOU READ HERE
Contents
Introduction
This guide is designed to help you get a simple Wesnoth GUI, implemented in lua, up and running while describing the basic building blocks along the way.
Some would find creating a GUI in part or in full using WML simpler to follow, and those alternatives are available, for example LuaAPI/gui/example, but we're using lua here. If you find WML easier to follow, you can always convert the lua tables that define the GUIs to WML using wml.tostring, for example:
print(wml.tostring(dialogDefinition))
gui.show_lua_console()
In some examples, instead of defining the entire gui at once, we'll break out some parts into separate variables. If you try to view one in WML and get an error from wml.tostring() about expecting a WML table and not a table, try passing your variable(/table) inside a table:
print(wml.tostring({listboxItem}))
gui.show_lua_console()
Getting Started
For example purposes, we'll create a directory in our campaign directory called lua containing a file called gui_tutorial.lua, and add a command in the prestart event for a scenario which will create a right-click menu option to invoke our new GUI. Of course there are other methods to invoke lua from WML, but this one will get us started. After all, we really just want to get something up on the screen ASAP, right?
A most basic GUI
In our prestart event, we create a simple menu item, which executes a single line of lua which calls the lua function most_basic_gui() which is found in gui_tutorial.lua:
[set_menu_item]
id=most_basic_gui
description="Our first GUI"
[command]
[lua]
code=<<
wesnoth.require("~add-ons/<OUR_CAMPAIGN>/lua/gui_tutorial.lua").most_basic_gui()
>>
[/lua]
[/command]
[/set_menu_item]
And create gui_tutorial.lua:
| The WML equivalent of dialogDefinition | |
|---|---|
local function most_basic_gui()
local dialogDefinition = {
wml.tag.tooltip { id = "tooltip_large" }, -- required
wml.tag.helptip { id = "helptip_large" }, -- required
wml.tag.grid { -- our most basic gui
wml.tag.row { -- a grid must include at least one row
wml.tag.column { -- a row needs a column
wml.tag.image { -- we can put stuff in a column
label = "units/trolls/grunt.png"
}
}
}
}
}
gui.show_dialog(dialogDefinition)
end
return { most_basic_gui = most_basic_gui}
|
[tooltip]
id="tooltip_large"
[/tooltip]
[helptip]
id="helptip_large"
[/helptip]
[grid]
[row]
[column]
[image]
label="units/trolls/grunt.png"
[/image]
[/column]
[/row]
[/grid]
|
In the above file, we have just the single function to create our GUI, followed by a return command which makes our function most_basic_gui() available to the wesnoth.require() function as most_basic_gui().
Our function creates a table containing the definition of a "dialog", and then passes that to gui.show_dialog(). It should be noted that gui.show_dialog does not provide synchronization, so if your GUI makes changes to the game state, you'll need to jump through some hoops or you'll break replays and multiplayer, but that's not something we need to care about at this point, so just be aware that you may need to deal with it in the future.
Our dialog definition at this point includes three parts. The first two are a tooltip and a helptip, which are required and probably do something, but nothing we care about here, we just have to have them. The third part is a grid, which is basically a table, like in HTML or MySQL, with rows and columns. A grid always contains at least one row. A row contains at least one column. Inside a column is exactly one item, a cell which contains a widget, in this case we'll use an image (later we'll see what else we can put in a cell). Note that we don't actually define a cell in our code, it's just a term used to refer to the contents of a column.
Note: if you should try out the above, you'll have to hit escape or enter to close the gui.
Adding a little flavor
You may have noticed our GUI is missing a header and a way to close it when we're done admiring our work. Here we add a new first row to our grid, while demonstrating a couple formatting options: a border to put some distance between our grid cell and its neighbor, and the "use_markup = true" option to enable Pango support in our text.
Our third row adds an OK button at the bottom. You can associate actions with buttons to do all kinds of things, but here we just exploit the default behaviour to close the GUI.
Of course, we'll also have to modify our return to support the new function, and update our menu item(s) accordingly.
local function most_basic_gui2()
local dialogDefinition = {
wml.tag.tooltip { id = "tooltip_large" },
wml.tag.helptip { id = "helptip_large" },
wml.tag.grid {
wml.tag.row { -- A header
wml.tag.column {
border = "bottom",
border_size = 10,
wml.tag.label {
use_markup = true,
label = "<span size='large'>" .. _"Here there be " ..
"<span color='yellow'>" ..
_"MONSTERS!" .. "</span></span>"
}
}
},
wml.tag.row { -- The body of our GUI
wml.tag.column {
wml.tag.image {
label = "units/trolls/grunt.png"
}
}
},
wml.tag.row {
wml.tag.column { -- An "OK" button, with no action assigned for now,
-- but it will close the gui
wml.tag.button {
id = "ok",
label = _"OK"
},
}
}
}
}
gui.show_dialog(dialogDefinition)
end
return { most_basic_gui = most_basic_gui, most_basic_gui2 = most_basic_gui2 }
And a bit more
And now a minor, but important change. We want to add a new text field next to the image in the body of our GUI. Obviously, we want to add a new column, but this is more difficult than when we added new rows in the previous example. The problem is that all rows (at a given level) in a grid must contain the same number of columns. We can't have two columns in the row that constitutes the body of our GUI, but only one in the header and OK button. To solve this problem, we replace our image tag with a new grid, which can use as many columns as we like (as long as they are the same within each row of our new grid). The grid contains a row with two columns, but that is okay because the grid itself is placed in a single column, which matches our single column header and footer (ok button), keeping the rows balanced.
local function most_basic_gui3()
local dialogDefinition = {
wml.tag.tooltip { id = "tooltip_large" },
wml.tag.helptip { id = "helptip_large" },
wml.tag.grid {
wml.tag.row { -- A header
wml.tag.column {
border = "bottom",
border_size = 10,
wml.tag.label {
use_markup = true,
label = "<span size='large'>" .. _"Here there be " ..
"<span color='yellow'>" ..
_"MONSTERS!" .. "</span></span>"
}
}
},
wml.tag.row { -- The body of our GUI
wml.tag.column {
wml.tag.grid {
wml.tag.row {
wml.tag.column {
wml.tag.image {
label = "units/trolls/grunt.png"
}
},
wml.tag.column {
wml.tag.label {
label = "A troll"
}
}
}
}
}
},
wml.tag.row {
wml.tag.column { -- An "OK" button, with no action assigned for now,
-- but it will close the gui
wml.tag.button {
id = "ok",
label = _"OK"
},
}
}
}
}
gui.show_dialog(dialogDefinition)
end
Listbox
Now we'd like to add some more monsters. Obviously, we could just add more rows, but what if we won't know until runtime how many and which ones? We could break up the definition of our dialog and add new rows dynamically, it's just a table after all, but fortunately we have a widget which handles this for us, a listbox. A listbox is kind of like an array, a collection of similar objects where the number of items can vary. We will tell the GUI where we want the box, and what each entry in the box will look like, and then at runtime we can add entries to the box.
local function gui_with_listbox()
local monsters = {
{ image = "units/trolls/grunt.png", string = "A troll" },
{ image = "units/monsters/cuttlefish.png", string = "A cuttlefish" },
{ image = "units/monsters/yeti.png", string = "A yeti" }
}
local listbox_id = "monsters"
local listboxItem = wml.tag.grid {
wml.tag.row {
wml.tag.column {
wml.tag.image {
id = "monster_image"
}
},
wml.tag.column {
wml.tag.label {
id = "monster_label"
}
}
}
}
local listboxDefinition = wml.tag.listbox { id = listbox_id,
wml.tag.list_definition {
wml.tag.row {
wml.tag.column {
wml.tag.toggle_panel {
listboxItem
}
}
}
}
}
local dialogDefinition = {
wml.tag.tooltip { id = "tooltip_large" },
wml.tag.helptip { id = "helptip_large" },
wml.tag.grid {
wml.tag.row { -- A header
wml.tag.column {
border = "bottom",
border_size = 10,
wml.tag.label {
use_markup = true,
label = "<span size='large'>" .. _"Here there be " ..
"<span color='yellow'>" ..
_"MONSTERS!" .. "</span></span>"
}
}
},
wml.tag.row { -- The body of our GUI
wml.tag.column {
listboxDefinition
}
},
wml.tag.row {
wml.tag.column { -- An "OK" button, with no action assigned for now,
-- but it will close the gui
wml.tag.button {
id = "ok",
label = _"OK"
},
}
}
}
}
local function preshow(dialog) -- Prepare the GUI before display
local listbox = dialog[listbox_id]
for i, monster in ipairs(monsters) do
listbox[i].monster_image.label = monster.image
listbox[i].monster_label.label = monster.string
end
end
gui.show_dialog(dialogDefinition,preshow)
end
We begin by creating a simple table which represents the data which will be presented in our listbox. In most cases, we probably wouldn't create that monster table here, but we need it for our example.
The variable listbox_id gives us an identifier for our listbox so we can reference it when we need to. We don't really need to use a variable here, it's just convenient.
We define the structure for the elements in our listbox, stored in listboxItem. Note that we've replaced the actual data with identifiers (e.g. 'units/trolls/grunt.png' becomes 'id = "monster_image"), since each element may have different data.
We define the listbox itself, specifying the identifier, and the definition of our listbox element (which looks a lot like a grid). The cell inside the column contains a variable which is just the listbox element definition we created above; it's not necessary to do this, we could have used one big table, but it's easier to read this way (IMO).
We replace the hardcoded data in our GUI body with our new listbox definition, again using a variable to make it easier to read.
We create a function, often called preshow(), which will be called for us as part of the drawing the GUI (see the new optional argument in gui.show_dialog() -- there's also an optional postshow(), but we don't need it here). This is where we pull the data from our example table into the listbox. We create a listbox variable associated with the listbox, identified by the listbox_id we assigned earlier, inside the dialog which gui.show_dialog() passes to preshow(). Then we iterate through our data table, using each entry from that table to populate a listbox item.
Let's look at that last action a little more closely using an example.
listbox[i].monster_image.label = monster.image
Which we can read as "In listbox element i of our listbox, for the variable monster_image which we defined in our listboxItem, use the data from the corresponding index i in our example data table". If you were to step through all of the variable substitutions, you'd see that for i=1, our dialogDefinition is basically the same thing as it was in the earlier examples, just supplied from a table instead of hardcoded.
You will probably notice that our data does not line up nicely in the GUI. We will fix that later.
Tree View
Simple
You may have noticed that clicking on a listbox item in our listbox caused it to be highlighted with a box around the contents. This is because the items in a listbox are selectable. This will be useful when we want to add actions, but it looks a bit odd if we just want to present a list of data.
Also, most of the data had to be formatted the same for each item in the listbox. We could, perhaps, include custom markup in our labels, but the actual layout, like the number of columns per row, had to be the same for every item.
Another way to present a list of data is the tree view. Since a tree view supports multiple data types, we may need to create multiple definitions for the elements in our list. These are known as nodes. It will also be necessary to explicitly define which node to use for each element when we populate our tree view.
local function basic_tree_view()
local monsters = {
{ image = "units/trolls/grunt.png", label = "A troll", name = _"Bob", type = "Trolls" },
{ image = "units/trolls/whelp.png", label = "A troll whelp", name = "Junior", type = "Trolls" },
{ image = "units/trolls/shaman.png", label = "A troll shaman", name = _"Alice", type = "Trolls" },
{ image = "units/monsters/cuttlefish.png", label = "A cuttlefish", type = "Seamonsters" },
{ image = "units/monsters/yeti.png", label = "A yeti", type = "Coolers" }
}
local tree_view = wml.tag.tree_view {
id = "monsters_tv",
wml.tag.node {
id = "trolls_node",
wml.tag.node_definition {
wml.tag.row {
wml.tag.column {
wml.tag.label {
id = "monster_name",
linked_group = "monster_name"
}
},
wml.tag.column {
wml.tag.image {
id = "monster_image",
linked_group = "monster_image"
}
},
wml.tag.column {
wml.tag.label {
id = "monster_label",
linked_group = "monster_label"
}
}
}
}
},
wml.tag.node {
id = "nottrolls_node",
wml.tag.node_definition {
wml.tag.row {
wml.tag.column {
wml.tag.image {
id = "monster_image",
linked_group = "monster_image"
}
},
wml.tag.column {
wml.tag.label {
id = "monster_label",
linked_group = "monster_label"
}
}
}
}
}
}
local dialogDefinition = {
wml.tag.tooltip { id = "tooltip_large" },
wml.tag.helptip { id = "helptip_large" },
wml.tag.linked_group {
id = "monster_name",
fixed_width = true
},
wml.tag.linked_group {
id = "monster_image",
fixed_width = true
},
wml.tag.linked_group {
id = "monster_label",
fixed_width = true
},
wml.tag.grid {
wml.tag.row { -- A header
wml.tag.column {
border = "bottom",
border_size = 10,
wml.tag.label {
use_markup = true,
label = "<span size='large'>" .. _"Here there be " ..
"<span color='yellow'>" ..
_"MONSTERS!" .. "</span></span>"
}
}
},
wml.tag.row { -- The body of our GUI
wml.tag.column {
tree_view
}
},
wml.tag.row {
wml.tag.column { -- An "OK" button, with no action assigned for now,
-- but it will close the gui
wml.tag.button {
id = "ok",
label = _"OK"
},
}
}
}
}
local function preshow(dialog) -- Prepare the GUI before display
for i, monster in ipairs(monsters) do
if monster.type == "Trolls" then
dialog.monsters_tv:add_item_of_type("trolls_node")
dialog.monsters_tv[i].monster_name.label = monster.name
else
dialog.monsters_tv:add_item_of_type("nottrolls_node")
end
dialog.monsters_tv[i].monster_image.label = monster.image
dialog.monsters_tv[i].monster_label.label = monster.label
end
end
gui.show_dialog(dialogDefinition,preshow)
end
We have expanded our list of monsters to include three types of trolls. We have also given each troll a name. This is of course a rather simplistic example, we could have simply given each monster that is not a troll an empty name, but it as presented here our approach serves the purpose of demonstrating how we deal with multiple data types. Our new tree view contains a node for each type of data we will present. In preview, we explicitly define each element in our list using add_item_of_type(), and populate the item accordingly.
You may also note the addition of a few linked_group lines. We'll cover linked groups in more detail later, but as used here they instruct the GUI that each column using the same node type needs to be aligned with the others. For example, all of our trolls line up nicely.
Building a Tree
At this point, one may wonder about the name "tree view", since what he have seen doesn't look much like a tree. To make a tree-like structure, we'll demonstrate adding children to nodes. At the top level our (upside-down) tree will have two nodes, one for trolls and one for everything else. A button will allow us to expand the trolls node to expose its children, which are themselves nodes, though they only contain a label at this point.
local function basic_tree_view2()
local tree_view = wml.tag.tree_view {
id = "monsters_tv",
wml.tag.node {
id = "race_node",
wml.tag.node_definition {
wml.tag.row {
wml.tag.column {
wml.tag.toggle_button {
id = "race_button",
}
},
wml.tag.column {
wml.tag.label {
id = "race_label",
}
}
}
}
},
wml.tag.node {
id = "details_node",
wml.tag.node_definition {
wml.tag.row {
wml.tag.column {
wml.tag.label {
id = "monster_type",
}
}
}
}
}
}
local dialogDefinition = {
wml.tag.tooltip { id = "tooltip_large" },
wml.tag.helptip { id = "helptip_large" },
wml.tag.grid {
wml.tag.row { -- A header
wml.tag.column {
border = "bottom",
border_size = 10,
wml.tag.label {
use_markup = true,
label = "<span size='large'>" .. _"Show me the " ..
"<span color='yellow'>" ..
_"MONSTERS!" .. "</span></span>"
}
}
},
wml.tag.row { -- The body of our GUI
wml.tag.column {
tree_view
}
},
wml.tag.row {
wml.tag.column { -- An "OK" button
wml.tag.button {
id = "ok",
label = _"OK"
},
}
}
}
}
local function preshow(dialog) -- Prepare the GUI before display
dialog.monsters_tv:add_item_of_type("race_node")
dialog.monsters_tv[1].race_label.label = "Trolls"
dialog.monsters_tv[1].race_button.on_modified = function()dialog.monsters_tv[1].unfolded =
dialog.monsters_tv[1].race_button.selected end
dialog.monsters_tv[1]:add_item_of_type("details_node")
dialog.monsters_tv[1][1].monster_type.label = "Whelp"
dialog.monsters_tv[1]:add_item_of_type("details_node")
dialog.monsters_tv[1][2].monster_type.label = "Shaman"
dialog.monsters_tv[1]:add_item_of_type("details_node")
dialog.monsters_tv[1][3].monster_type.label = "Troll"
dialog.monsters_tv:add_item_of_type("race_node")
dialog.monsters_tv[2].race_label.label = "Other scary things"
dialog.monsters_tv[2].race_button.visible = "hidden"
end
gui.show_dialog(dialogDefinition,preshow)
end
We define two nodes in our tree, a race_node for the top level, and a details_node for the children of a race_node. The rest of the interesting bits are in preshow().
We add a node, label it "Trolls", and add a callback to the button such that when the button is checked (selected), the children of the node will be visible (the node is "unfolded", a boolean value which defaults to false). Then we add three nodes as children of this node.
Our second node, "Other scary things" will remain empty for now, so we'll set the visible attribute on its button to "hidden" (which is like false, but with hidden the widget still takes up space).
This example is rather ugly, both in the hardwired code and the appearance of the resulting GUI, but it addresses a couple important aspects of how tree views work and how we might use them. Let's clean it up a bit. We'll add an indentation_step_size to the tree view, along with a spacer and horizontal_alignment to our details node, to make the labels line up nicely, and change the button definition to replace the checkbox with something that looks like it belongs there.
local tree_view = wml.tag.tree_view {
id = "monsters_tv",
indentation_step_size = 20,
wml.tag.node {
id = "race_node",
wml.tag.node_definition {
wml.tag.row {
wml.tag.column {
wml.tag.toggle_button {
id = "race_button",
definition = "tree_view_node"
}
},
wml.tag.column {
horizontal_alignment = "left",
grow_factor = 1,
wml.tag.label {
id = "race_label",
}
}
}
}
},
wml.tag.node {
id = "details_node",
wml.tag.node_definition {
wml.tag.row {
wml.tag.column {
wml.tag.spacer { width = 40 }
},
wml.tag.column {
horizontal_alignment = "left",
grow_factor = 1,
wml.tag.label {
id = "monster_type",
}
}
}
}
}
}
Multi_page
Simple
Like a tree_view, a multi_page is a heterogeneous container which is dynamically populated, however, while a multi_page contains multiple elements (pages), only one page is displayed at any one time. Its purpose is perhaps best described by a couple of examples.
local function basic_multipage()
local monsters = {
{ image = "units/trolls/grunt.png", label = "A troll", name = _"Bob", type = "Trolls" },
{ image = "units/trolls/whelp.png", label = "A troll whelp", name = "Junior", type = "Trolls" },
{ image = "units/trolls/shaman.png", label = "A troll shaman", name = _"Alice", type = "Trolls" },
{ image = "units/monsters/cuttlefish.png", label = "A cuttlefish", type = "Seamonsters" },
{ image = "units/monsters/yeti.png", label = "A yeti", type = "Coolers" }
}
local multi_page = wml.tag.multi_page {
id = "monsters_mp",
wml.tag.page_definition {
id = "trolls_page",
wml.tag.row {
wml.tag.column {
wml.tag.label {
id = "monster_name"
}
},
wml.tag.column {
wml.tag.image {
id = "monster_image"
}
},
wml.tag.column {
wml.tag.label {
id = "monster_label"
}
}
}
},
wml.tag.page_definition {
id = "nottrolls_page",
wml.tag.row {
wml.tag.column {
wml.tag.image {
id = "monster_image",
linked_group = "monster_image"
}
},
wml.tag.column {
wml.tag.label {
id = "monster_label",
linked_group = "monster_label"
}
}
}
}
}
local dialogDefinition = {
wml.tag.tooltip { id = "tooltip_large" },
wml.tag.helptip { id = "helptip_large" },
wml.tag.grid {
wml.tag.row { -- A header
wml.tag.column {
border = "bottom",
border_size = 10,
wml.tag.label {
use_markup = true,
label = "<span size='large'>" .. _"Here there be " ..
"<span color='yellow'>" ..
_"MONSTERS!" .. "</span></span>"
}
}
},
wml.tag.row { -- The body of our GUI
wml.tag.column {
multi_page
}
},
wml.tag.row {
wml.tag.column { -- An "OK" button
wml.tag.button {
id = "ok",
label = _"OK"
},
}
}
}
}
local function preshow(dialog) -- Prepare the GUI before display
for i, monster in ipairs(monsters) do
if monster.type == "Trolls" then
dialog.monsters_mp:add_item_of_type("trolls_page")
dialog.monsters_mp[i].monster_name.label = monster.name
else
dialog.monsters_mp:add_item_of_type("nottrolls_page")
end
dialog.monsters_mp[i].monster_image.label = monster.image
dialog.monsters_mp[i].monster_label.label = monster.label
end
--dialog.monsters_mp.selected_index = 5
end
gui.show_dialog(dialogDefinition,preshow)
end
As you can see, the code for our basic multi_page GUI looks a lot like our basic tree_view GUI. The difference is what is displayed. While both the tree_view and the multi_page containers contain five items, with the multi_page, only the first one is displayed. More specifically, only the page associated with the selected_index attribute of the multi_page object, which defaults to 1, is displayed. If we were to uncomment the last line in preshow(), we would still see only one item, but it would be the fifth one we allocated. It's nice to know all our pages are in there somewhere, but this example is pretty useless. What we need is a way to select which page we want to see from within our GUI.
A More Useful Multi_page
To demonstrate the usefulness of a multi_page, and highlight its difference from a tree_view, we'll add a listbox to allow us to select the page to view. We'll also need to add a little action to our GUI.
local function more_useful_multi_page()
local monsters = {
{ image = "units/trolls/grunt.png", label = "A troll", name = _"Bob", race = "Trolls", tip = "Your uncle" },
{ image = "units/trolls/whelp.png", label = "A troll whelp", name = "Junior", race = "Trolls", tip = "Your nephew" },
{ image = "units/trolls/shaman.png", label = "A troll shaman", name = _"Alice", race = "Trolls", tip = "Your auntie" },
{ image = "units/monsters/cuttlefish.png", label = "A cuttlefish", race = "Seamonsters", tip = "Not a fish" },
{ image = "units/monsters/yeti.png", label = "A yeti", race = "Coolers", tip = "<span size='large' weight='bold'>ROAR!</span>" }
}
local listbox_id = "monsters"
local listboxItem = wml.tag.grid {
wml.tag.row {
wml.tag.column {
wml.tag.image {
id = "monster_image"
}
}
}
}
local listboxDefinition = wml.tag.listbox { id = listbox_id,
wml.tag.list_definition {
wml.tag.row {
wml.tag.column {
wml.tag.toggle_panel {
listboxItem
}
}
}
}
}
local multi_page = wml.tag.multi_page { id = "monsters_mp",
wml.tag.page_definition { id = "trolls_page",
wml.tag.row {
wml.tag.column {
wml.tag.label { id = "monster_name" }
},
},
wml.tag.row {
wml.tag.column {
wml.tag.image { id = "monster_image" }
},
},
wml.tag.row {
wml.tag.column {
wml.tag.label { id = "monster_label" }
}
}
},
wml.tag.page_definition { id = "nottrolls_page",
wml.tag.row {
wml.tag.column {
wml.tag.image { id = "monster_image" }
},
},
wml.tag.row {
wml.tag.column {
wml.tag.label { id = "monster_label" }
}
},
}
}
local dialogDefinition = {
wml.tag.tooltip { id = "tooltip_large" },
wml.tag.helptip { id = "helptip_large" },
wml.tag.grid {
wml.tag.row { -- A header
wml.tag.column {
border = "bottom",
border_size = 10,
wml.tag.label {
use_markup = true,
label = "<span size='large'>" .. _"Here there be " ..
"<span color='yellow'>" ..
_"MONSTERS!" .. "</span></span>"
}
}
},
wml.tag.row { -- The body of our GUI
wml.tag.column {
wml.tag.grid {
wml.tag.row {
wml.tag.column {
listboxDefinition
},
wml.tag.column {
wml.tag.spacer {
width = 30
}
},
wml.tag.column {
multi_page
},
}
}
}
},
wml.tag.row {
wml.tag.column { -- An "OK" button
wml.tag.button {
id = "ok",
label = _"OK"
},
}
}
}
}
local function preshow(dialog) -- Prepare the GUI before display
local listbox = dialog[listbox_id]
for i, monster in ipairs(monsters) do
listbox[i].monster_image.label = monster.image
listbox[i].monster_image.tooltip = monster.tip
if monster.type == "Trolls" then
dialog.monsters_mp:add_item_of_type("trolls_page")
dialog.monsters_mp[i].monster_name.label = monster.name
else
dialog.monsters_mp:add_item_of_type("nottrolls_page")
end
dialog.monsters_mp[i].monster_image.label = monster.image
dialog.monsters_mp[i].monster_image.tooltip = monster.tip
dialog.monsters_mp[i].monster_label.label = monster.label
end
local function switch_page()
dialog.monsters_mp.selected_index = listbox.selected_index
end
listbox.on_modified = switch_page
end
gui.show_dialog(dialogDefinition,preshow)
end
Most of this should look pretty familiar. We've simply taken the previous example and added a second column to our GUI using code from an earlier example to add a listbox. In addition, we altered the page layout slightly, and added a spacer column in the dialog definition to approve the appearance.
The interesting stuff is in preshow(). Again we've merged in some listbox code from an earlier example, but we've also created a new local function switch_page(), which simply sets the selected_index attribute of our multi_page to the same as that of our listbox, and then we've configured the listbox.on_modified callback to call switch_page(). Now when the user selects an item in the listbox (updating listbox.selected_index and triggering listbox.on_modified), dialog.monsters_mp.selected_index is updated accordingly and therefore the visible page changes to the one associated with the selected unit.
Also note in preshow() we've added a new child to our monster_image identifier for both the listbox and the multi_page, a tooltip. When the user hovers the mouse over the image of one of our monsters, they'll see a popup message which we've added to our monster table.
Actions Have Consequences
So far, our GUIs have only displayed some information on the screen, but at some point we're probably going to want to use a GUI to get input from the user.
Buttons
In this example, we'll create a couple buttons which provide the user a choice, and demonstrate how we get the results back where we can put them to use.
local function basic_return_value()
local dialogDefinition = {
wml.tag.tooltip { id = "tooltip_large" },
wml.tag.helptip { id = "helptip_large" },
wml.tag.linked_group {
id = "leader_lg",
fixed_height = true,
},
wml.tag.grid {
wml.tag.row { -- A header
wml.tag.column {
border = "bottom",
border_size = 10,
wml.tag.label {
use_markup = true,
label = "<span size='large'>" .. _"Which unit shall lead your army?" .. "</span>"
}
}
},
wml.tag.row { -- The body of our GUI
wml.tag.column {
wml.tag.grid {
wml.tag.row {
wml.tag.column {
wml.tag.grid {
wml.tag.row {
wml.tag.column {
wml.tag.label { label = "Alice" }
}
},
wml.tag.row {
wml.tag.column {
wml.tag.image {
linked_group = "leader_lg",
label = "units/elves-wood/sylph.png"
}
}
},
wml.tag.row {
wml.tag.column {
wml.tag.button {
label = "Select",
return_value = 1
}
}
},
}
},
wml.tag.column {
wml.tag.spacer { width = 20 }
},
wml.tag.column {
wml.tag.grid {
wml.tag.row {
wml.tag.column {
wml.tag.label { label = "Bob" }
}
},
wml.tag.row {
wml.tag.column {
wml.tag.image {
linked_group = "leader_lg",
label = "units/human-loyalists/marshal.png"
}
}
},
wml.tag.row {
wml.tag.column {
wml.tag.button {
label = "Select",
return_value = 2
}
}
}
}
}
}
}
}
}
}
}
local user_chose = gui.show_dialog(dialogDefinition)
local leader
if user_chose == -1 then -- User closed the dialog by hitting the Enter key
leader = nil
end
if user_chose == -2 then -- User closed the dialog by hitting the Escape key
leader = nil
end
if user_chose == 1 then
leader = "Alice"
end
if user_chose == 2 then
leader = "Bob"
end
local confirmed_leader_choice
if leader ~= nil then
local query = _"You want " .. leader .. _" as your leader?"
confirmed_leader_choice = gui.confirm(query)
end
if confirmed_leader_choice then
wesnoth.message("Great!")
else
wesnoth.message("Fine, lead them yourself!")
end
end
Here we've added a couple buttons, and assigned each of them a return value. When the user selects one of these buttons, the GUI is closed and the value of return_value is returned from gui.show_dialog(). We then use gui.confirm() which provides a very simple Yes/No popup and returns true or false, respectively. Other useful functions can be found on that page which provide handy alternatives to creating your own GUI for other simple user inputs.
The use of return_value is rather limited, as it only returns integers and can't be used with containers like listboxes. In more complex cases we'll need to turn to callback functions, like widget.on_modified() as we used in an earlier example. More examples of callbacks can be found at that link.
Slider and Textbox
Here we see a couple methods of getting more dynamic input from the user, a slider and a textbox presented in one silly example.
function scrollbar_and_textbox()
local dialogDefinition = {
wml.tag.tooltip { id = "tooltip_large" },
wml.tag.helptip { id = "helptip_large" },
wml.tag.grid {
wml.tag.row {
wml.tag.column {
wml.tag.label { label = _"How much gold will you pay for this old rusty sword?" }
}
},
wml.tag.row {
wml.tag.column {
wml.tag.slider {
id = "gold_sl",
minimum_value = 0,
maximum_value = wesnoth.sides[wesnoth.current.side].gold,
value = math.floor(wesnoth.sides[wesnoth.current.side].gold/2)
}
}
},
wml.tag.row {
wml.tag.column {
wml.tag.text_box {
id = "gold_tb",
label = tostring(math.floor(wesnoth.sides[wesnoth.current.side].gold/2))
}
}
},
wml.tag.row {
wml.tag.column {
wml.tag.button {
id = "ok",
label = _"OK"
}
}
}
}
}
local function preshow(dialog)
local function show_input()
wesnoth.interface.add_chat_message(_"You chose " .. dialog.gold_sl.value .. _" with the slider")
wesnoth.interface.add_chat_message(_"You entered " .. tostring(dialog.gold_tb.text) .. _" in the text_box")
end
dialog.ok.on_button_click = show_input
dialog.gold_sl.on_modified = function()dialog.gold_tb.text = tostring(dialog.gold_sl.value)end
end
gui.show_dialog(dialogDefinition,preshow)
end
We create a slider, with a range from 0 to the amount of gold possessed by the current side and an initial value in the middle, and a text box with the same initial value. We assign a function to our OK button which simply reports on the values provided by the user. For no reason whatsoever, we add a callback such that when the user adjusts the slider the value in the textbox is update to match the slider.
Note that the textbox returns text, even though it looks like we're expecting the user to input a natural number. Remember to validate those inputs.
Appearance
This section needs help
Borders
Alignment
By default, the GUI will usually center widgets in their cells, which is not always what we want. In this example, we use horizontal_alignment to move widgets around a little.
In more complex cases, it may be useful to add spacers to help force alignment, or use linked_groups to force consistent alignment for objects within a grid.
local function basic_alignment()
local dialogDefinition = {
wml.tag.tooltip { id = "tooltip_large" },
wml.tag.helptip { id = "helptip_large" },
wml.tag.grid {
wml.tag.row {
wml.tag.column {
wml.tag.label {
label = "Ralph"
}
},
wml.tag.column {
wml.tag.image {
label = "units/trolls/grunt.png" -- 72x72
}
}
},
wml.tag.row {
wml.tag.column {
horizontal_alignment = "right",
wml.tag.label {
label = "Sam"
}
},
wml.tag.column {
wml.tag.image {
label = "units/trolls/troll-hero-attack-se-4.png" -- 122x102
}
}
},
wml.tag.row {
wml.tag.column {
horizontal_alignment = "left",
wml.tag.label {
label = "Jr"
}
},
wml.tag.column {
horizontal_alignment = "right",
wml.tag.image {
label = "units/trolls/whelp.png" -- 72x72
}
}
},
}
}
gui.show_dialog(dialogDefinition)
end
The screenshots show the output of this example with and without the horizontal_alignment lines included above.
Growth
Definitions
Many widgets can be configured to have to a different appearance, for example in our tree_view example we changed the definition of a toggle_button from the default of a checkbox by setting definition = "tree_view_node". This option was found by looking at the id of a toggle_button_definition in .../data/gui/widget/toggle_button_tree_view_node.cfg:
- textdomain wesnoth-lib/data/gui/widget
- Definition of a toggle button to be used in a tree view as node fold/unfold indicator
[toggle_button_definition]
id = "tree_view_node"
description = "Fold/unfold status indicator of a tree view node."
There are many other definitions for buttons and other widget types in that directory. It would be nice to have a list (linked here), but for now you'll just have to look around.
We can even create our own custom definitions using gui.add_widget_definition (TODO: add example)
Panels
Canvases
Part of panels?
Placement
such as horizontal_placement = "left"
Appendix
Useful Links
LuaAPI/gui - Mostly about opening windows
LuaAPI/types/widget - Widget attributes and callbacks
Devdocs - GUI widgets
Credits
The basic framework that composes the initial examples was lifted from LotI. It's a great place to find well written examples, but some of it is complex enough to be a little overwhelming when getting started.
Many examples, particularly tree view and multipage, are heavily derived from the World Conquest multiplayer campaign.