kick start: P27 - P35: Jump between different screen using Transition Inside the Properties of image, Add Widget feature properties → touchShortReleased → function(v:touchId::int, v:x::int, v:y::int, v:fingerId::int) { firedelayed 0, ev:“turnon”() true }

• Widget: Any object in the view state? could be image, could be text (called “label”)
• State: means the “state” of the machine. Such as initial state, view state.
  • View: is also a widget, resident under view state.
    • image: is also a widget.
  • transition: watch for a trigger signal. Trigger signal could be send from a image, etc.

• Add image files to the $GUIDEPROJECTPATH/<project name>/resources directory
• Use image files the same way like shapes.

Only the OpenGL ES version 2.0 or higher and DirectX 11 renderers can display 3D graphics. The supported 3D graphic formats are COLLADA (.dae) and Filmbox (.fbx). For best results, use the Filmbox format.

It is possible to import 3D graphic files in EB GUIDE Studio. After you have imported a 3D graphic file in EB GUIDE Studio, in $GUIDEPROJECTPATH/<project name>/resources, you find a subdirectory. Meshes as defined in the 3D graphic file are imported as .ebmesh files. For details, see section 6.1.3, “Import of a 3D graphic file”.

Task: research if there is an easy way to convert .ebmesh (or .jt? can't remember) files to .fbx files.

Result

 ….  generally the best way to convert anything from nurbs (eg. jt file) to polygons is by importing the STEP file into Rhinoceros and save to a polygon format like FBX. That software gives the most control over the quality of the conversion, as well as preserving the NX body names….