I think that merging individual updates into a joint project would be a great step for everyone to avoid conflicts or relying on an update without the other.
And in general happy with it new feature and fixes it will encourage the skinners to spend more time to improve their work.
Regards
i can share my version i have add many updates too for metrix
https://we.tl/t-X2FquP2P4ujyK4GH
i use only private never shared it
i have upload my source to git https://github.com/OwnerPlugin…gner/blob/net10/README.md
NOTE THE RULER AND GUIDELINES FOLLOWING THE MOUSE (RED DASHED)
- ADDED BUTTON TO ENABLE/DISABLE GUIDELINES
NOTE THE RULER AND GUIDELINES FOLLOWING THE MOUSE (RED DASHED)
- ADDED BUTTON TO ENABLE/DISABLE GUIDELINES
in to next version i have added.. Other element and compatibility with OpenAtv Skin
Update all locale language ;)
Great work and great efforts gentlemen
Again sharing my thoughts with you
1. Is it possible to add option to modify the ruler unit, mm, cm, inch, or switch it to pixels?
2. Is it possible to add text wrap option to eLable with the basic left, right, center?
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.
4. Is it possible to add option to make edit over network path beside the local files, this will save a lot of time to transfer files between the local pc and the box especially for small changes?
5. Is it possible to add radial gradient?
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
Regards,
It's really complicated to get the rulers to match the guidelines.
The zoom distracts from the coordinates.
I'd like to enable/disable only the rulers and make them fixed at the top, while I'd always leave the guidelines.
I noticed that the rulers cover a few pixels on the left of the screen.
It would be better to integrate it into the software GUI.
Too many calculations to do to do a little at a time.
-So I'll make these changes first. (If I'm not mistaken, the gradient is already inserted), it should take it. But just test: or send an example to insert it soon.
We're not asking for the moon ;) The program was created many years ago, and is only evolving to accept new skins. (But it's not certain that everything will work... no feedback so far.)
The alphabetical button is faulty; it breaks the skin.
code?
The alphabetical button is faulty; it breaks the skin.
i check it
Thanks, I'm waiting for your feedback
I've identified the exact cause of the issue. The alphabetical sorting button deletes the following tags from the top of the file:
<output id="0">
<resolution xres="1920" yres="1080" bpp="32" />
</output>
When I manually add these lines back to the corrupted skin.xml, the editor opens the skin without any problems. It seems the sorting algorithm treats the header tags as screens and fails to preserve them
It deletes these too
<borderset name="bsWindow">
<windowstyle type="skinned" id="0">
It deletes these too
<borderset name="bsWindow">
<windowstyle type="skinned" id="0">
try this
pasted-from-clipboard.png
issue :
Problem with ruler that allows you to buy a part of the skin in Paint
solvable.
Display Morecode?
The alphabetical button is faulty; it breaks the skin.
i check it
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.
Thank you, the problems have been resolved
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!
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!
Are these also functions that work within images? It would be helpful if you could provide some examples—specifically for testing purposes—both within an image and in the Designer.
Don’t have an account yet? Register yourself now and be a part of our community!
