![macros layouteditor macros layouteditor](http://layouteditor.net/screenshot/screen-shot-setup.png)
UI widgets are defined as V-code in v/UI.v. See the on-line reference pages for more detail.
![macros layouteditor macros layouteditor](https://docs.enthought.com/canopy/2.1/_images/macro_editor.png)
It is important to realize that objects will inherit all the sub-objects of the classes above them in the hierarchy. Note that some objects (UIoptionBox, UItoggle) use multiple inheritance.
![macros layouteditor macros layouteditor](http://layouteditor.net/screenshot/screen-shot-toolbars.png)
The User Interface Kit's object class hierarchy is shown in the figure on the following page. Abstract elements are not instantiated directly by the developer, but are used as base objects and classes for the basic interface objects. The application shell has a managed window, window manager decoration, a pull-down top level menu bar, and a context-sensitive help message display region.Īll interactive interface objects exist in a class hierarchy that permits considerable leverage of the base type objects. The application is "wired up" by attaching the data referenced in function objects to the data stored within a widget.Īll AVS/Express applications have an application shell ( UIapp or UIshell). Building a user interface to an application consists of creating a UI layout (UI hierarchy, position, dimension, color, etc.) by instancing UI objects and manipulating their subobjects. UI components (sliders, windows, etc.) are AVS/Express objects. The UI is manipulated using objects, modules and macros in the Network Editor. The User Interface ("UI") Kit provides widgets for building complete interfaces to AVS/Express applications. Creating an Integrated Application Interface.Creating a Stand-Alone Application Interface.The files that define the user interfaces for: the Data Visualization Kit modules is v/modules.v the AVS5 Compatibility Kit modules is v/ACUmods.v the Graphics Display Kit panels is v/view.v The V code that defines this application is in examples/ui_samp.v.
#MACROS LAYOUTEDITOR HOW TO#
Using example networks, this chapter illustrates how to create common components of an application's user interface from objects in the User Interface (UI) library.įor additional examples, including wrapping the user interface objects into a macro and connecting them to application parameter values, see the tutorials in the Visualization Techniques manual, and the User Interface "sampler" application in Examples.UIApp. This chapter includes a general introduction to the User Interface ("UI") Kit and demonstrates how to create common application user interface components using tutorial-style examples.