The Movicon.NExT graphics engine is based on the modern WPF technology and, therefore, the graphical elements are managed according to this technology.

XAML definition:

XAML is a declarative Extensible Application Markup Language (pronounced "zammel")
applied to the .NET Framework programming model. XAML simplifies the creation of
user interfaces for .NET Framework applications. User interface elements can be created
and made visible in the declarative XAML markup therefore separating interface
definition from the runtime logic using the code-behind file united with the markup
using partial class definitions. XAML represents a direct way of creating object instances
in a specific set of supported types defined in the assembly. XAML is different from the
major part of other markup languages that are generally interpreted languages without
direct links to supported system types. XAML enables work flow by operating in specific
parts of the user interface and the application's logic being substantially different tools.

Importing XAML symbol graphics:

Movicon.NExT enables users to import symbols or part of the product design to external
editors. This gives users the chance to use third party editors (such as Microsoft Blend)
and to enable them to use their graphical work to obtain symbols with remarkable
graphical impact that can be used in Movicon screens or for creating custom symbol
By using the "
Import XAML" command available from the "Insert" group ribbon, users
can select the desired graphics file and import it within their project to create a new
Movicon symbol.

When you import 3D symbols please take into account the

If you wish to manage the animation of each individual element,
for example, to associate an InnerScreen in cases in where there
are elements embedded at different levels in the imported XAML,
the symbol to be imported will need to have the

When the symbol is imported and contains textures, you will be
asked whether the image file should be imported to the project's
Images folder. If you confirm with 'NO', the image's original
absolute path will be saved in the screen's xaml.settings file. In
any case, an absolute path will be saved in the screen's
xaml.settings file which will mean that if you rename or move the
project in different path, it will be no longer possible to find the

Was this article helpful?
1 out of 1 found this helpful



Please sign in to leave a comment.