MtButton Configuration

• Id: To give additional context in the handler script, specify a string that will identify any notifications dispatched by this plug-in. This is often included as an argument for the event so a common script may handle events from a number of plug-ins.

• Set Shared Memory: If ON enables shared memory to be updated for the plug-in notifications.

  • Shared Memory Prefix: This sets a ‘prefix name’ to be prepended to the shared memory variables maintained by the plug-ins notifications. For plug-ins that maintain multiple fields each field name has the prefix prepended to it followed by a dot ‘.’ so as to mimic member access to an object, i.e: if the prefix is ‘Obj’ the fields ‘field1’ and ‘field2’ would be identified with the strings ‘Obj.field1’ and ‘Obj.field2’. The shared memory field ‘Obj’ is also maintained and is simply an integer that is modified every time any of its ‘subfields’ is updated.

  • Shared Memory Type: Click either Global, Scene, or Distributed. This selects the shared memory area to update.

• Set Data Pool: Shows ‘you wish’ plug-in notifications to set a Data Pool variable

  • Data Pool Variable: Shows the name of the Data Pool variable to have set.

• Active during screen wide telestration?: If the button to is to stay active when the screen-wide telestrator is on, set to On. The default is off, which means the button cannot be triggered when telestration is on.

• Trigger type:

  • On Touch: Sets the buttons to generate an ‘onTrigger’ event immediately when they are touched. No other events are generated in this mode.

  • On Release: Sets the buttons to generate an ‘onTrigger’ event when the last stroke present over a button is released. onStrokeEnter() and onStrokeLeave() events are generated as strokes enter and leave the button (see protocol below).

  • On Tap: Sets the buttons to generate an ‘onTrigger’ event when strokes recognized as ‘taps’ occur after a button is quickly pressed and released without movement or a finger is held down on a key on an object. onStrokeEnter() and onStrokeLeave() events are also generated in this mode.

  • Taps Only: Sets the buttons to emit an ‘onTap’ event when stokes recognized as a ‘taps’ occur. No other events are generated in this mode.

• Hit Coordinate Type: Click either Local, World or Screen. This selects the Coordinate system to use.

Events and Notifications

The MtButton generates an OnTap event when it is tapped in ‘Taps Only’ mode:

sub OnTap(HitContainer as String, Id as StringHit, Point as VertexTaps as Integer, plug-inContainer as String, FirstChildContainer as String)

end sub

• HitContainer as String: the name of the container that was ‘hit’

• Id as String: the user ID string entered in the notification interface

• HitPoint as Vertex: the Point where the object was tapped in local coordinates

• Taps as Integer: the number of taps ie: 2 == double tap

• plug-inContainer as String: name of the container the plug-in is attached to

• FirstChildContainer as String: direct (first level) child container of the plug-in, that is a (indirect or direct) parent of the tapped container. If the plug-in container itself is tapped, the plug-in container is returned.

The MtButton generates an OnTrigger event when it is triggered in any other mode than ‘Taps Only’:

sub OnTrigger(HitContainer as String, Id as String, HitPoint as Vertex, Taps as Integer, plug-inContainer as String, FirstChildContainer as String, StrokeId as Integer)

end sub

• HitContainer as String: the name of the leaf container that was ‘hit’

• Id as String: the user ID string entered in the notification interface

• HitPoint as Vertex: the Point where the object was tapped in local coordinates

• Taps as Integer: the number of taps if tapped, ie: 2 == double tap

• plug-inContainer as String: name of the container the plug-in is attached to

• FirstChildContainer as String: first child container below the plug-in the trigger occurred on or below

• StrokeId as Integer: Unique ID of stroke causing this event.

The MtButton generates an OnStrokeEnter event when it is triggered in any other mode than ‘Taps Only’:

sub OnStrokeEnter(Id as String, plug-inContainer as String, FirstChildContainer as String, StrokeId as Integer, StrokeCount as Integer, Active as Integer)

end sub

• Id as String: the user ID string entered in the notification interface

• plug-inContainer as String: name of the container the plug-in is attached to

• FirstChildContainer as String: first child container below the plug-in the stroke entered.

• StrokeId as Integer: Unique ID of stroke causing this event. Only valid from initial enter to final leave.

• StrokeCount as Integer: count of stroke on the button after entry. Will be ‘1’ when the first stroke enters

• Active as Integer: Will be 0 if stroke went down on button. ‘1’ if it was already down when entering.
  The MtButton generates an OnStrokeLeave event when it is triggered in any other mode than ‘Taps Only’:

sub OnLeave(Id as String, plug-inContainer as String, FirstChildContainer as String, StrokeId as Integer, StrokeCount as Integer, Active as Integer)

end sub

• Id as String: the user ID string entered in the notification interface

• plug-inContainer as String: name of the container the plug-in is attached to

• FirstChildContainer as String: first child container below the plug-in the stroke exited.

• StrokeId as Integer: Unique ID of stroke causing this event. Only valid from initial enter to final leave.

• StrokeCount as Integer: count of stroke on the button after exit. Will be ‘0’ when the last stroke exits

• Active as Integer: Will be 0 if stroke went up to cause leave. ‘1’ if still down and ‘rolled off’

The shared memory field names are:

• HitContainer: the name of the container that was ‘hit’

• Id: the user ID string entered in the notification interface

• HitPoint: the Point where the object was tapped in the selected coordinate type.

• Taps: the number of taps, ie: 2 = double tap

• plug-inContainer: name of the container the plug-in is attached to

• FirstChildContainer: first child container below the plug-in that tap occurred on or below

• StrokeId: unique ID of last trigger or tap.

The Data Pool structure updated is:

• MtButton:

  • string Id

  • string HitPoint

  • string HitContainer

  • string Taps

  • string plug-inContainer

  • string FirstChildContainer

  • string StrokeId

To Create a Simple Scene with the MtButton plug-in

1. Create a new Scene.

2. Add a new group Container.

3. Name the group Container ButtonScript.

4. Add the Script plug-in to the ButtonScript Container (Container plug-ins > Global).

5. Open the Script Editor and type this script:

   sub OnTap(HitContainer as String, Id as String, HitPoint as Vertex, Taps as Integer, plug-inContainer as String, FirstChildContainer as String)

   dim bt as Container

   dim text as String

   bt = FindSubContainer("ButtonText")

   text = "OnTap(\n HitContainer = " & HitContainer

   text &= "\n Id = " & Id

   text &= "\n HitPoint = " & HitPoint

   text &= "\n Taps = " & Taps

   text &= "\n plug-inContainer = " & plug-inContainer

   text &= "\n FirstChildContainer = " & FirstChildContainer & "\n)"

   bt.Geometry.Text = text

   end sub

6. Click Compile and Run.

7. Add three Sub-containers. Name them, in order:

   • Button1

   • Button2

   • ButtonText

8. Add a Circle Geometry to the Button1 and Button2 Containers.

9. Use the Circle Geometry Transformation editors to move the two circles so that both can be seen.

10. Right-click the Button1 and Button2 Containers, in turn, and select Add Material… from the context-menu. Open the Material Editor and define a color for both Containers.

11. Add the MtButton plug-in to the Button1 and Button2 Containers.

    

12. In the MtButton plug-in editor:

    • Type ‘myButton1’ in the Button1 Id field

    • Type ‘myButton2’ in the Button2 Id field

    • In Trigger Type field click On Tap for both containers

13. Add a Font to the ButtonText Container.

14. Open the Scene in On Air.

15. Click on each button, in turn, and see the text change with each selection.

16. Use the MtButton plug-in editor to modify the button’s actions, as required.