Why can’t some templates not be dropped into the Composer
Description:
EmWi refuses putting some templates into the composer.
Solution:
The reason why EmWi does not allow to drag and drop certain templates to the Composer is, because not all templates fit to the currently selected Composer page. First of all you need to understand the three main navigation levels in the Composer.
1.) Project level.
Only one project page can be opened in the composer of an EmWi project. The members of a project view can have only four types of bricks – unit s and three types of variant identifiers:
- Profiles
- Languages
- Styles
- Units
2.) Unit level
If the Composer shows the members of a unit, only the following bricks can be added to this composer page:
- Classes
- Resources (fonts or bitmaps)
- Constants
- Enumerations
- Sets
- Auto Objects
- Inline Code
3.) Class level
A class Composer page can cover the following types of members:
- Views (visible objects like Rectangle, Text, Gradient, etc.)
- Objects (instances of predefined or customized classes)
- Variables
- Properties
- Methods (normal methods, slot methods, OnGet- and OnSet-methods)
- Arrays
4. Others
Some special templates can only be used in the dedicated type. These are:
- EnumItem can only be part of an "Enum" or "Set" Composer page
- Macros can only be added to a "Profile" Composer page
All other drag and drop action beside above listed will be refused from EmWi.
See also:
Keywords:
Composer, template, gallery, drag and drop, object, brick, class
Last update on 2010-08-19 by Mario Stefanutti.