Screensaver
A screensaver appears when nobody has used the app for a set time. Visitors tap the screen to clear it and return to the app. An app can have one screensaver or several.
- Screensaver contents: the simplest screensaver shows an animated background such as Awesome or Shader effect. A screensaver can also show an Image viewer, Image movie, Video viewer, Video carousel or Text viewer, the Champagne, Particles or Sparkles effects, the IR Sensor View, Animated content, or an App switcher.
- Several screensavers: by default, a screensaver fills the whole screen. You can give it a custom size and location instead, for example to show different screensavers on different parts of the wall.
- Screen lock: a screensaver can also lock the screen. While the screen is locked, the screensaver cannot be dismissed and blocks all input to the app underneath. See Lock the screen.

The animated content is an image viewer that fades in and out at random places on the screen. Visitors tap anywhere to hide the screensaver.
Add a screensaver to your app
- Click Structures and select the structure.
- On the Overlay layer row, open the … menu and choose Add Widget, then choose Screensaver.
- Select the screensaver in the structure tree and set its attributes:
- Size and Location: leave Size at
0 0for a screensaver that fills the whole screen. For a smaller screensaver, set its size in pixels and its Location (top-left corner). - App idle timeout: how long, in seconds, the app must go unused before the screensaver appears. The default is 600 (10 minutes). Set it to
0if the screensaver should never appear by itself, for example when it is only used to lock the screen. - Crop screensaver content (Advanced): applies only to a screensaver with a custom size. By default, content that overflows the screensaver's area is cropped. Turn it off to let content overflow.
- Size and Location: leave Size at
- If the app has several screensavers, give each one a clear name: open its … menu and choose Rename.
Changes save automatically.
Add content to the screensaver
- In the structure tree, expand the screensaver and find its Screensaver contents row.
- Open the row's … menu and choose Add Widget, then choose the content. You can add several widgets, for example an animated background with images on top.
- Select each widget and set its attributes. For an image viewer, drag the image from the Media Library panel onto it.
Note
An animated background fills the screensaver's area by itself. An image or video does not: to make one fill the screen, set its Size and Location to cover the wall.

Lock the screen
A screensaver with a Lock behavior can lock the screen with a PIN or a Codice card. While the screen is locked, the screensaver stays up and blocks all input to the app until someone unlocks it.
Locking only happens when the screensaver is started with a Screensaver trigger. A screensaver that appears because the app was idle does not lock the screen, even if it has a lock behavior.
Add a lock behavior
- Select the screensaver in the structure tree.
- In its attributes, open the Lock behavior drop-down list and choose + Create new.... Enter a name, for example Staff lock, and confirm. To reuse a lock you already have, choose it from the list instead.
- Select the new Screen lock in the structure tree and set:
- Unlocking method: PIN entered at lock time (the default), Codice presented at lock time, or User choice of Codice or PIN entered at lock time. The person locking the screen chooses the PIN or presents the Codice card, and the same PIN or card unlocks it.
- PIN source: where the unlock PIN comes from.
- Set at lock time (legacy) (the default): the person locking the screen types a 4-digit PIN, as set by Unlocking method.
- Custom PIN: a fixed PIN that you enter in Custom PIN, 4 to 8 digits. The screen locks straight away with this PIN, and the unlocking method is always PIN.
- Named PIN Group: a PIN managed on the PIN Groups page. That page is marked Coming soon in this release, so use Custom PIN for a fixed PIN.


Add a screensaver trigger
A Screensaver trigger starts the screensaver on demand. You can add it anywhere content can be launched: a menu, a content hotspot or Codice content.
Note
If the app has several screensavers, a screensaver trigger starts all of them.
For example, to add a screensaver trigger to a content hotspot:
- Add a Content hotspot to the Main layer and set its Hotspot location and Hotspot size. To help visitors find it, add an image to its Hotspot visualization widgets. A new hotspot is transparent, so while you set it up, give it a Background color to find it on the wall. See Content Hotspots.
- On the hotspot's Widgets launched from hotspot around tap location row, open the … menu and choose Add Widget, then choose Screensaver trigger.
Lock and unlock the screen
To lock the screen, tap the hotspot. The screensaver starts. What happens next depends on the PIN source:
- Set at lock time: a Lock the screen dialog appears.
- PIN: type a 4-digit PIN on the number pad, tap Lock, the dialog then reads Confirm the PIN. Type the same PIN again and tap Lock again. If the two entries do not match, the dialog goes back to Set a PIN. Before MT Showcase 26.11.1 the second entry also read Set a PIN.
- Codice: place your Codice card on the dialog, check that the code shown is correct, and tap Lock.
- Custom PIN: the screen locks straight away with the preset PIN, and the Unlock the screen dialog opens at once. Type the preset PIN to unlock.


To unlock the screen, tap anywhere on the screensaver to show the Unlock the screen dialog. Type the PIN or place the Codice card on the dialog, then tap Unlock. With a Codice lock, you can also just place the card on the screen without tapping first.

If you type the wrong PIN, the dialog shows Incorrect PIN under the PIN field and stays open so that you can try again. A PIN Lock dialog does the same. The message appears from Showcase 26.11.1; earlier versions cleared the field without saying why.


Before Showcase 26.11.1
A screen locked with a PIN could not be unlocked: the Unlock button stayed dimmed, and the only way out was to restart MT Showcase. With Set at lock time, the Lock button had the same fault. A PIN Lock dialog (see below) opened underneath the widgets of the Main layer and did not react to touch. Update to 26.11.1 or later before you use a PIN.
Require a PIN before something opens
A PIN Lock asks for a PIN before a widget does its job. Use it to keep staff-only content or controls away from visitors.

Protect a widget or hotspot:
- In the structure tree, find the widget's Behavior operators row, open the … menu and choose Add Widget, then choose PIN Lock.
- Select the PIN Lock and set:
- When to challenge: On parent action (tap) (the default) asks for the PIN when a visitor taps the widget, for example a hotspot or button. On parent appearance hides the widget and asks for the PIN as soon as it opens, whatever opened it.
- PIN source: Custom PIN, then enter the PIN (4 to 8 digits). Named PIN Group uses a PIN from the PIN Groups page, which is marked Coming soon in this release.
A Content hotspot has a Behavior operators setting too, shown as a drop-down list with an Edit button once an operator is chosen. Add a PIN Lock to the hotspot itself and set When to challenge to On parent action (tap): tapping the hotspot asks for the PIN, and the content opens after the right PIN.
From Showcase 26.11.2 a Counter has a Behavior operators setting too, so it can carry a PIN Lock in the same way: with On parent action (tap), the counter asks for the PIN when it is tapped and opens its content after the right PIN.
On an Exit Showcase widget (the Exit button) and an App switcher, a PIN Lock with On parent action (tap) asks for the PIN when the visitor confirms (OK on the exit confirmation, Launch on the app switcher confirmation). The exit or the switch happens only after the right PIN. From Showcase 26.11.2 the confirmation card is hidden while the PIN is asked for, and it comes back if the visitor cancels the PIN dialog.
If Show confirmation is off on the widget, there is no confirmation to answer. From Showcase 26.11.1 the PIN is asked as soon as the button is tapped, and nothing else is shown until the PIN is right. If the visitor cancels the PIN dialog, the exit or the switch is cancelled too. Before 26.11.1 the widget's own confirmation box was drawn behind the PIN dialog and stayed on the wall after the visitor cancelled.
With Show confirmation off and On parent action (tap), the PIN dialog opens centred on the point where the button was tapped, whether that is a hotspot or a menu item. Before 26.11.1 it opened in the top-left corner of the wall. If the visitor taps the launcher again while the dialog is open, the dialog closes together with the button. This applies to every widget with a PIN Lock, in both When to challenge modes.
With On parent appearance, an Exit button or App switcher without confirmation waits for the right PIN before it exits or switches app. Before 26.11.1 it exited or switched while the PIN dialog was still open.
Fixed in 26.11.1: menu items skipped the PIN
Before MT Showcase 26.11.1, an Exit button or App switcher with Show confirmation off and On parent action (tap) asked for the PIN when opened from a hotspot but not when it was an item opened from a menu: the player exited or switched app at once. The PIN is now asked however the widget is opened. A widget opened from a menu with On parent appearance also used to behave as On parent action (tap), so one that is never tapped opened without a PIN. It now asks as it appears. If your wall relies on a PIN Lock on such a widget, update to 26.11.1 or later.
Before Showcase 26.11.1
A Content hotspot had no Behavior operators row, so you could not add a PIN Lock to the hotspot itself. To protect what a hotspot opened, you added the PIN Lock to the widget that the hotspot launched and set When to challenge to On parent appearance. An Exit button with a PIN Lock exited without asking for the PIN.


When a PIN Lock cannot be checked (from Showcase 26.11.1):
A PIN Lock that cannot check a PIN keeps its widget locked. This happens when the lock uses a Named PIN Group that has been deleted, or when the lock's settings do not reach the player.
- With On parent action (tap), the tap does nothing.
- With On parent appearance, the widget is not shown.
- On the Menu access gate, a hold opens no menu.
The player log names the widget in each case. Before 26.11.1 the widget opened with no PIN.
The same holds for a widget whose PIN Lock has been deleted. The widget stays hidden, is closed after 5 seconds, and the player log names the widget and the missing lock. Because the player cannot tell what a deleted behavior operator was, this applies to any deleted operator in the widget's Behavior operators setting. In the editor the setting then reads Missing widget with its number, in the warning color. Choose Remove from slot to clear it, and the widget shows again.
A PIN group that a Screen lock or a PIN Lock uses cannot be deleted. The server refuses and lists the locks that use the group. Editing a PIN group asks for a New PIN: type one to change the PIN, or leave the field empty to keep the current PIN. The editor never shows the current PIN. The PIN Groups page is still marked Coming soon.

If the PIN group is deleted or its PIN is changed while the PIN dialog is open, the dialog uses the new state when the visitor submits: a deleted group closes the dialog and the widget stays locked, and a changed PIN means only the new PIN is accepted.
PIN Locks, conditions and Logic groups (from Showcase 26.11.1):
- A tap-locked Content hotspot that is triggered by a Logic group (for example OR or LATCH with Trigger children on group HIGH) asks for its PIN. The dialog opens at the hotspot and the content opens only after the right PIN. If the group goes LOW while the dialog is open, the dialog closes. Before 26.11.1 the group opened the locked content with no PIN.
- Each locked member of a group asks for its own PIN. PIN dialogs do not open on top of each other: a dialog that would cover one already on the wall waits, and opens when that one has closed. Dialogs far enough apart not to touch open together.
- A widget's own Condition signal cannot open a locked widget. The PIN is asked whatever the condition says.
- A locked hotspot in Toggle or Timed mode opens after the right PIN. Before 26.11.1 it never opened. A locked hotspot in Hold mode asks for the PIN as soon as it is pressed. A hold cannot continue while the visitor types, so after the right PIN the hotspot opens and stays open. Press it again and enter the PIN again to close it, as with a locked Toggle hotspot.
Deleting a PIN Lock that is in use:
A PIN Lock kept in the Widget Library and used by widgets cannot be deleted, and neither can a widget that holds such a lock. The editor shows which apps use it, for example: Cannot delete "Staff lock" — used in Lobby wall. Remove it from those first. Clear the lock from each widget's Behavior operators row, then delete it.
Protect the app's menus:
The structure's Menu access gate holds an optional PIN Lock for the tap-and-hold gesture that opens menus from the Menu layer. On the Menu access gate row, open the … menu and choose Add Widget, then choose PIN Lock and set its PIN as above. Visitors must then enter the PIN before a menu opens. Leave the gate empty to let anyone open menus. From Showcase 26.11.1 the lock also holds while the app is starting: a hold made before the app has finished loading opens no menu without the PIN. In fact, a hold made while the app is still starting opens no menu at all until the app has loaded. Hold again once the app is up. If the PIN Lock in the Menu access gate is deleted while the slot still points to it, no menu opens (from Showcase 26.11.2) until you clear the Menu access gate slot in the editor or bind a PIN Lock that exists.