It is equipped with many advanced functions to support creating UIs suited to various purposes. UI Conductor supports not only the creation of UIs, but also tests, implementation, localization, and documentation.

Supports sending/receiving state messages between the UIs of embedded applications and those of UI Conductor. You can operate the UIs by linking events and actions triggered with state messages, and by sending to applications events such as button presses on the UI side.As of Version 1.9, events and actions on the UI side can be directly called.

For details of linkage with application states, click here.

UI Conductor can now store variables and control UIs linked with setting information held by UI parts. Any number of variables can be prepared by the user, which allows for the creation of behavior linked to UIs using variables, without directly changing properties of UI components from embedded applications. Additionally, changes in properties of UI components can be obtained via embedded applications as variables.

For details of linkage with application variables, click here.

Screen transitions can be performed by sending a state message for screen transition to the UI. By setting messages and variables, embedded applications can control screen transitions without explicitly specifying the screen to transition to.

For details of screen transitions via the view state, click here.

UIs created by UI Conductor can be operated on various OSs and platforms. The difference between platforms and OS is corrected by a porting layer provided by Candera, enabling the created UIs to run with Core SDK Runtime, which provides developers many options when it comes to OSs and platforms.

UI Conductor can use 3D contents as HMI. It supports OpenGL ES 3.0, and boasts a high level of performance and expression in 3D displays. UI Conductor version 1.9 has improved performance, smoothness, and rendering ability.

UI Conductor supports the import of FBXfiles, which themselves are supported as standard by programs such as 3ds Max or Maya for creating 3D model data. By simply dragging and dropping an FBX file into UI Conductor, the converter will import model data, materials, and shader textures and turn them into usable resources.

Combining material components and the standard shader can change textures and appearances of models. You can also use the customized shader to render beyond the scope of the standard shader.

You can place a light or camera anywhere within the 3D world of UI conductor to replicate the effects of different lighting and camera angles.

Animation can be expressed by placing a key frame and changing the values of component properties. There are many features including ease in/out and the animation of objects according to data for a given path. Ver. 1.9 links variables with animation frame positions to allow even more precise control of UI animations from embedded applications.

Data designed in Photoshop can be directly converted to project data for UI Conductor using Photoshop plug-ins provided by Candera. You can use this data as it is without needing to cut out UI parts and laying them out again.

UI material data including images, fonts, localized strings, and 3D models can all be registered to resource packages and managed as resources. Resources use real file names by referring to them, which makes it easy to perform replacements and updates as necessary.

Using UI Conductor, one can create UI parts for embedded equipment/automobiles, set animations, and manage events and actions, all through simply dragging and dropping with the mouse. Such ease of use enables planners, localizers, or developers and designers of embedded applications to utilize UI Conductor to work and check their progress without needing to use any hardware.

It is possible to preview and test the behavior of UIs on Windows/PC without needing to wait until it is embedded into the hardware, thus upping the quality of UIs by allowing for repeated and frequent development, testing, and improvement cycles.

It is possible to display multiple screens separately, or together in a single preview screen. which enables With this one can check linkages during HMI development using multiple displays, without needing to embed into hardware.

You can freely create Object-based UI parts with the necessary functionality for them, in addition to Components which have drawing, listing, and scrolling functions. Individual Components have Properties as setting information, so you can freely design and develop suitable UI parts by defining such Properties.

You can display objects in 2D/3D by adding Component Functions to Object Containers and adding actions such as animations by managing properties.

There are a number of standard components, which can be directly used for creating UI parts. Moreover, parts frequently used in UI expressions are provided as control components.

Making created UI parts into “common objects” allows one to copy and use them as “reference objects”, which have the same appearance, events, actions, or animation functionality.

You can use event components to make user operations, messages from embedded applications or any other change to be detected as events. Moreover, you can set behaviors of UIs according to event generation timing with action components.

All drawings, behaviors or other UI elements on UI Conductor are provided as plug-ins.

You can preview behavior by connecting to an external device. Create a “preview plug-in” and receive input from the external device. It will be reflected in the preview on UI Conductor.

UI Conductor has a system to create UIs in multiple languages. You can set the common UIs and those to be localized, which allows one to create UIs supporting multiple environments with the minimum amount of work required.

• Easy to display in various languages with UI Conductor Tact on Windows/PC and switch the screen to check changes
• The person in charge of localization can proceed with the work while checking UIs using UI Conductor Tact

Equipped with a Multilingual Editor to support multiple languages. The editor can list key strings held by UIs and texts in various languages, and edit them. The editor also has functions to output localized string tables as a CSV file and create resource files to display localized strings.

UI screens created can be output as a document in Microsoft® Excel® format. A list of parts being used or layout information can be output. The content and layout to be displayed can be freely edited by the user.

States and variables used in UIs created can be output in a format that can be handled as constants in C languages which facilitates use by developers. Also, a basic framework according to UIs created can be output to operate it on embedded equipment.

UI Conductor provides a plethora of APIs which are used to operate UIs created from embedded applications. Also, these APIs can be used to add functions not achieved by plug-ins.

To find target functions, UI Conductor has a window to search for them by using an object or component name as a key. This is especially useful for when there are many screens or many objects/components in a single screen.