Buttons

General:

A button executes a defined action as soon as it is clicked by the user in the genARate mobile app

It can either trigger external content (e.g. a web link, call, etc.) or apply actions to other AR elements (e.g. visibility of an image, start/stop a video, etc.)

In this way, buttons allow to include interactivity and logics into your AR scenario by using a simple workflow editor

How to:
  • Click on the Text icon inside the toolbar
  • A thumbnail appears inside the scenario editor
  • Click on the thumbnail inside the scenario editor to move/position the element via drag & drop and to access the Action workflow editor and settings
Settings & Button Editor:

Name:  Select a unique name for your button/tab

Textbox: Enter label of button/tab

Size: Set individual size of button (by width and height, aspect ratio is fixed)

Position: Set individual position of button (by x and y)

Opacity: Set transparency level of button (0 = fully transparent, 1= no transparency)

Rotation: Set rotation of button (by °)

Arrange: Define hierarchy in between different content elements

Fix to Screen: Disconnects button from trigger image and fixes it to screen so it will always be shown on same position, no matter how trigger image is moved

Hidden: Makes button invisible at start of AR experience (to e.g. let it appear by a Button interaction at a later time)

Unique ID: Internal ID of content element, mostly used for referencing inside HTML fragments

Background Image: Add image file as background of button

Background Color: Change background color of button (HEX/RGB/HSL)

Font: Set font of label text

Font size: Set size of label text

Font color: Set color of label text

Padding:

Action Workflow Editor

The workflow editor is split in two different sections:

Destination

  • First: select the content element (“Destination”), to which the action should be applied, by its name
  • This can either be the button itself or any other available element inside your AR scenario
  • You can select multiple destinations for each button

Action

  • Secondly: assign a list of available actions for each element you have selected in “Destination”
  • Define the selected action for the selected content element
  • Each content element can only handle one action
  • Note that the available actions may differ related to the content type of the selected element (not all actions are available for all content types!) 

Animations:

Explanation can be found here.

 

NOTE:

To simplify your work with buttons, first access the settings of the content elements inside your scenario and define a clear, unique and addressable name for each. This will help you afterwards with applying the button actions to each of the elements.

Tips & Tricks

To avoid confusion with setting up buttons and actions, always build the following logic in your mind:

“When the user clicks on [Button which is selected in scenario editor], the augmentation(s) [list of selected content elemenexecute the action(s) [defined actions per element]”

© 2018 Konica Minolta Business Solutions Europe GmbH

Close Menu
Close Panel