Hospitals and Malls: Interactive Directories

For hospital lobbies, shopping malls, showrooms and service kiosks. Build a persistent menu with a content region on the right. Tapping Floors, Services or Directions changes that content; a Home button restores the opening page.

This project displays prepared maps and information. It does not include automatic indoor positioning, live queues, registration or business-system data integration. Existing web systems can be added after the basic directory works.

1. Prepare a Home page and three information pages

Use clear images and recognizable filenames:

Example file	Content
00_home.png	Welcome page: Choose an option on the left
01_floors.png	Floor, department or store directory
02_services.png	Service desks, restrooms and accessible facilities
03_route.png	Entrance, parking or destination directions

Use maps and information confirmed by the venue. Simplify dense content into readable destinations and instructions. For a large collection, consider the media-search widget later instead of crowding one image.

2. Create a landscape directory

Create a landscape 16:9 program named Lobby - Interactive Directory. You may also adapt a personal copy of an interactive-tablet template such as 平板交互查询.

Sub-screen name	Horizontal range	Vertical range	Content
Directory title	0% → 100%	0% → 12%	One title text item
Button - Floors	0% → 26%	12% → 38%	One text item or button image
Button - Services	0% → 26%	38% → 64%	One text item or button image
Button - Directions	0% → 26%	64% → 90%	One text item or button image
Content	26% → 100%	12% → 90%	Four information images
Button - Home	0% → 26%	90% → 100%	Home text
Instructions	26% → 100%	90% → 100%	Short instructions

Each button is a separate sub-screen. Three button images in one slideshow would not remain visible together. The information pages, however, belong together in the single Content region.

3. Make the content wait for a choice

1. Add the four images to Content in the table's order, with Home first.
2. Name the media Home, Floors, Services and Directions so targets are easy to identify.
3. Use Contain to keep maps and text visible.
4. In Content's sub-screen settings, enable Fixed Play and No Gesture Slide, and keep random playback off.
5. Keep one text item or image in each button region; the buttons need no slideshow.

Fixed playback waits for a selection. Gesture blocking prevents accidental swipes to a different page. After a choice, the right side keeps that page until another selection or re-entry into the program.

4. Configure the first button

For Floors:

1. Select Button - Floors and open its blue pencil button.
2. Scroll to the click-action list and select Add Event.
3. Choose the built-in widget type, then the screen-jump widget.
4. In its target table, find the Content sub-screen and choose Floors from that row's media dropdown.
5. Return to the parent panel with this action retained. Leave other target rows unselected for now.

The action belongs to the button sub-screen. Its text labels the button; the Floors image stays in Content. Do not move the information image into the menu button.

5. Add the other buttons and Home

Repeat the same action setup:

Button sub-screen	Action	Target sub-screen	Target media
Button - Floors	Screen jump	Content	Floors
Button - Services	Screen jump	Content	Services
Button - Directions	Screen jump	Content	Directions
Button - Home	Screen jump	Content	Home

All buttons address the same region, choosing different media. Complete these four actions before adding submenus or external pages.

Configure Home explicitly

This example changes media inside the existing program rather than opening a separate page. Program Auto Back Time is not an inactivity-reset timer for this Content region. This project returns through the Home button. Design and test a separate interaction flow if an automatic return to Home is required.

6. Add remote support if needed

Finish touch actions first. For remote operation, enable Request Focus on the three menu buttons and Home, choose a clear focus color and start with the default border size of 3.

Titles, the Content region and decorative instructions usually need no focus. Users can then navigate among actionable buttons and press Confirm to run their actions.

See sub-screen settings for focus appearance and program settings for automatic hiding. Focus alone does not create an action.

7. Test in Preview and on a real device

Preview, save and cast to one touch-capable Player:

1. Home appears on initial entry.
2. Each menu button selects the correct right-side page while the left menu stays visible.
3. Home restores the opening page.
4. Waiting beyond the original image duration does not automatically advance the content.
5. Swiping the content does not change pages. With a remote, actionable buttons receive focus and Confirm runs them.

Editing clicks mostly select regions for editing; they are not playback tests. An ordinary non-touch TV requires the configured remote workflow. Software does not add touch hardware to a display.

Extend and maintain

Choose a new file in an existing information media item when maps change, then save. Deleting and recreating that media can leave buttons pointing at a removed target, so recheck the action table. Test existing buttons after adding content too.

For separate web pages, PDFs, child programs or external apps, continue with interactive programs. Prepared local images need no online query service; web pages and external APIs still require the Player to reach their network destinations.