.png%3Falt%3Dmedia%26token%3Dbbbe5f82-239a-4459-9ec5-3b5961b4b466)
.png%3Falt%3Dmedia%26token%3Dbbbe5f82-239a-4459-9ec5-3b5961b4b466)
Controls
Controls allow you to customize how people interact with your maps. You can use them to overlay buttons, images, text and more! Interactive controls can be used to transform the current view's setting too, such as filter, focus, and clustering.
You can use the Basic Editor to add a few simple types of controls to your map. Click the settings icon 
to open the editor, then click Add custom control. Kumu will open up the controls builder, with a few options pre-selected:
controls builder ui
Use the dropdown menus in the controls builder to set up your control, then, when you're done, click the back arrow to return to the main screen, and click SAVE.
Want to remove unneeded controls? You can use the remove unneeded controls section of this guide to help troubleshoot.
To unlock the full set of flexible controls features, you can use the Advanced Editor. Here's an example of what controls look like in the Advanced Editor:
@controls {
top {
showcase {
by: "Element type";
}
}
}
In general, controls are defined with the
@controls block, grouped into regions, and customized using properties. You can add multiple controls to a region, and even override or move Kumu's built-in controls. Here's the general syntax that shows how multiple regions can be used, and how multiple controls can be added to the same region:@controls {
region {
control {
property: value;
property: value;
....
}
another-control {
property: value;
property: value;
...
}
}
another-region {
some-other-control {
...
}
}
}
Adding a custom control to your map starts by picking where you want to place the control. Controls can be assigned to one of six regions on the map:
toptop-lefttop-rightbottombottom-leftbottom-right
@controls {
top-left {
title {
value: "This map has a title!";
}
}
}
After you set the region, you can choose what type of control you are adding. Here are the available control types:
Controls are customized using properties, and each control understands a slightly different set of properties. In the example below,
by is a property of the showcase control that accepts a field name (wrapped in quotes).@controls {
bottom {
showcase {
by: "Element type";
}
}
}
For a full list of the properties that each control understands, read the individual control guides (linked above), or check out the controls reference.
Sometimes, controls need to work with complex lists of options. Since these would be overwhelming to define in a single line, the items are included as children of the control instead, and follow a similar syntax to the controls themselves.
In the example below, we call the
option blocks the "children" of the showcase control, and each child includes its own set of properties.@controls {
top-left {
showcase {
option {
label: "People";
selector: person;
}
option {
label: "Orgs";
selector: organization;
}
}
}
}
You can read through the individual control guides (linked above) to see which controls accept children and which properties their children understand.
By default, controls are each stored on their own line, and they each have their own set of properties. However, if you want to display a group of controls on one line (for example, along the top of your map), and assign a few common properties and values (for example,
font-size: 16) to all of them, you can use groups.To group controls, use the following
group syntax:@controls {
region {
group {
property: value;
control {
property: value;
property: value;
...
}
another-control {...}
an-additional-control {...}
}
}
}
The properties that get set underneath
group will apply to all controls nested inside the group. And before you ask—yes, it's possible to nest groups inside of other groups as well!When you're adding controls through the Basic Editor, you might sometimes add a duplicate control by accident, or add a control that says "No values found for [some field name]". To remove any of those unneeded controls, you can use the Advanced Editor.
Open up the Advanced Editor, and, unless you have added partial views, there will be a block of code right at the top starting with
@controls.// Line 1 of your Advanced Editor:
@controls {
...There will be other code inside this block
}
If you don't want any controls or "No values found for [some field name]" messages on your map, simply delete the entire
@controls block, then click "Save" at the bottom of the editor.If you have some controls in there that you would like to preserve, you'll first need to learn the basics of how to read
@controls code, so that you can tell which controls you want to delete and which you want to keep. You can learn more about reading @controls code in our full guide on controls. Of course you can always send us an email at [email protected] to help out!All of Kumu's built-in controls (search, zoom buttons, settings buttons, the legend) are handled by the same platform that custom controls are built on. That means you can move the built-in controls around, omit ones you don't need, or even reset the built-in controls and start from scratch.
Although you won't see it in your Advanced Editor, here's the default
@controls code working behind the scenes:@controls {
top-left {
search {}
}
top-right {
zoom-toolbar {}
settings-toolbar {}
focus-toolbar {}
}
bottom-left {
legend {}
}
}
You can omit individual controls by including the region in your
@controls block, without the control inside of it. For example, if you wanted to keep the search bar, but omit all other built-in controls, you could use:@controls {
top-right {}
bottom-left {}
}
Note that if you add controls to a region in your code, but don't explicitly include the default control, it will be hidden. For example, this code will hide the
zoom-toolbar, settings-toolbar, and focus-toolbar:@controls {
top-right {
title {
value: "Oops! I hid some useful controls.";
}
}
}
If you want to quickly start from scratch without any of Kumu's built-in controls, you can use
reset: true.@controls {
reset: true;
top {
title {
value: "Check out my custom controls";
}
}
bottom {
showcase {
by: "Element type";
}
}
}
Last modified 25d ago