1. Is it possible to add option to modify the ruler unit, mm, cm, inch, or switch it to pixels?
DONE!
2. Is it possible to add text wrap option to eLable with the basic left, right, center?
The Wrap property works perfectly because it affects the pNoWrap field.
The logic is:
If noWrap == true → the text is forced to a single line, with the height adjusted.
If noWrap == false → the text can automatically wrap, using the full height of the label.
3. Is it possible to add folder as work space to xml files without the needs to add <skin> on top and bottom, this will help a lot to make edit for screen files prior add it to the main skin.xml file and will convert the system to offline editor to and screen xml file.
DONE!
pasted-from-clipboard.png
5. Is it possible to add radial gradient?
At present, the program does NOT support radial gradients – it only handles linear (horizontal/vertical) gradients through the backgroundGradient attribute.
Gradient parsing currently only recognizes strings like this:
"color1,color2,vertical" (2 colors + direction)
"color1,color2,color3,vertical" (3 colors + direction)
The direction can only be "vertical" or "horizontal" (case insensitive).
There is no handling of "radial", "from corner", "to center", or similar.
In the drawing, when a gradient is detected, a LinearGradientBrush is created – no RadialGradientBrush or PathGradientBrush.
it is not foreseen in the current program and would require non-trivial work.
6. Is it possible to add a custom template for widget, pxmap, eLable, progress... etc? This will help the skinners to standard their code instead of copy paste from screen to another
DONE!
pasted-from-clipboard.png
## User Guide for New Features in v4.2.3.4
### ****** ## MOD v4.2.3.4 – Lululla
**New Features**
- **Template system**:
- Added new "Template" menu to insert custom widgets/pixmaps/labels/sliders from XML files stored in a configurable `templates` folder.
- Includes example templates for quick start (label, pixmap, slider, progress).
- **Open Screen**:
- Open standalone screen XML files (without `<skin>` wrapper), edit them, and save back only the screen node – ideal for offline screen editing and version control.
- **Import Screen**:
- Import an external screen XML file into the currently open skin, merging it as a new screen.
- **Label text wrap**:
- Added "Wrap Text" property for `eLabel` (and widgets with `render="Label"`) to enable automatic line wrapping (XML attribute `wrap="1"`).
**Stability & Improvements**
- **Stability fixes**:
- Resolved multiple exceptions when opening single‑screen files (missing mandatory tags like `output`, `colors`, `fonts`, `windowstyle`).
- Properly handles null references in `cDataBase` and `sAttributeScreen` during wrapper generation.
- **Code improvements**:
- Enhanced XML wrapper generation for single‑screen editing.
- Unified gradient handling, general refactoring and cleanup.
Display More
### 1. Custom Templates (Menu "Template")
You can create your own widget templates and reuse them across different skins.
**How to use:**
1. Create a folder named `templates` in the same directory as `e2skinner2.exe` (or change the path in `Preferences`).
2. Inside `templates`, create one or more XML files. Each file must contain **only one** widget definition, for example:
```xml
<widget name="MyRedLabel" position="0,0" size="200,50" text="Hello" foregroundColor="red" backgroundColor="black" wrap="1" />
```
3. In OpenSkinDesigner, open a skin, select a screen or panel, then go to **Template → [your file name]**.
4. The widget will be inserted directly into the tree.
**Example templates**
are created automatically when the `templates` folder is empty.
---
### 2. Open Screen (Menu "File → Open Screen...")
You can edit a **standalone screen XML file** that does not contain the `<skin>` wrapper. This is useful for offline editing, version control, or sharing single screens.
**How to use:**
1. Create a file with only a `<screen>...</screen>` block (no `<skin>`, no extra tags).
2. In OpenSkinDesigner, go to **File → Open Screen...** and select your file.
3. The designer will treat it as a normal skin (with a temporary wrapper). You can add, move, delete widgets, change properties, etc.
4. When you save (Ctrl+S), the original file will be **overwritten with the screen only** (the wrapper is removed).
**Note:**
The original file must be writable. The temporary wrapper includes minimal required tags (`output`, `colors`, `fonts`, `windowstyle`) so that the program works correctly.
---
### 3. Import Screen (Menu "File → Import Screen...")
You can insert a screen from another XML file into the currently open skin. The imported screen becomes a new screen at the end of the skin tree.
**How to use:**
1. Open a skin normally (File → Open).
2. Go to **File → Import Screen...** and select an XML file containing a screen (same format as above).
3. The screen will be added to the root level of the current skin.
4. You can then edit, move, or delete it like any other screen.
5. Save the skin (Ctrl+S) to store the imported screen as part of the main `skin.xml`.
---
### 4. Text Wrap for eLabel (Property "Wrap Text")
Labels (eLabel or widgets with `render="Label"`) now support automatic line wrapping.
**How to use:**
- Select a label in the tree.
- In the property grid, find the category **Label - Label**.
- Enable **Wrap Text** (checkbox).
- The generated XML will contain `wrap="1"` (and remove `noWrap` if present).
- The preview will show the text wrapped if the label width is insufficient.
**Compatibility:**
Enigma2 natively supports `wrap="1"` via the `RT_WRAP` flag.
---
### Additional Notes
- All new strings (menu items, messages, tooltips) are translated into the existing language files. If your language file is missing some entries, add them following the pattern in `English.lng`.
- For developers: The `templates` folder path can be changed in **Preferences**.
- The **Open Screen** feature uses a temporary wrapper that includes minimal valid definitions for `output`, `colors`, `fonts`, `windowstyle`. It saves only the `<screen>` node back to the original file.
Enjoy!
