Skip to main content

Logic Block Triggers

This is the list of Triggers found in the Logic Block. Use the Triggers to complete an expression.

Player Width – The trigger is based on the width of the player.

Player Height – The trigger is based on the height of the player.

Fullscreen – The trigger is based on the player being in Fullscreen or not.

Mouse Over – When the mouse hovers over an element it will trigger an event.

Mouse Down – When the mouse clicks on or presses down on an element it will trigger an event. For a touch device, this event happens when the element is tapped or touched.

Mouse Over Parent – Add this trigger to an element that is a child of a parent. When the mouse hovers over the element’s parent, it will trigger an event. An example of use is to show/hide hotspot tooltips, where the text box for the tooltip is the child of the hotspot template.

Mouse Down Parent – Add this trigger to an element that is a child of a parent. When the mouse clicks or pressed down on the element’s parent, it will trigger an event.

Pan – The trigger is based on the angle of rotation for the pan movement (left/right).

Tilt – The trigger is based on the angle of rotation for the tilt movement (up/down).

FoV – The trigger is based on the angle of view (zoom).

Active – The trigger is based on the element being active or not. The Timer element uses a logic block and it can be used to hide elements in the skin. For example, adding an element as a child to the Timer will allow the timer to hide the element after it times out. Once the timer is no longer active, the element attached to it will hide.

Loading – The trigger is based on if the panorama is loading or not.

Loading Tiles – The trigger is based on the tiles being loaded.

Visited – This trigger is based on a node being visited (or viewed) or not. An example of use would be to apply this to a graphic that indicates to the user they have already visited a node in a tour.

Tags – If the panorama has tags, this trigger will be based on the defined tags.

View Mode – This trigger will be based on the current view mode: Continuous or Drag Mode. The view mode refers to how the panorama rotates when the user interacts with it.

View State – For Object2VR and triggering its current view state.

Poly Mode – This is based on the currently active polygon hotspot’s View Mode. You can use this to show/hide buttons whose actions are to show and hide the polygon hotspots. For example:

Trigger Comparison Value Operation
Poly Mode = Show Current
Visible: False

Is Mobile – Use this trigger to initiate the logic block based on the mobile device being used (iOS, Android and IE Mobile). One example of use would be to hide tooltips when a touch device is being used.

Trigger Comparison Value Operation
Mouse Over Parent = True AND
is Mobile = False
Visible: True

Auto Rotating – With this trigger, you can create an event if the panorama is currently auto-rotating (true) or not (false).

See also…

2017-02-07 08:19:46