home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Development
General Development (no feature request here!)
Is there a need for a skin editor?
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Dadeo" data-source="post: 518910" data-attributes="member: 27204"><p>Your example makes sense, but consider text - often I wish to change between a label, fadelabel, textbox, or textboxscrollup while preserving position, font, text color and other properties. As you say, I can just remove the control and input a new one. Perhaps when I get used to using the Skin Editor this will be easy to do. </p><p></p><p>Not all xmls support all properties (though imo they should!), so that list of controls on the left, showing GUIproperties will not always be accurate for the window you are working in. </p><p></p><p>My suggestion was twofold:</p><p>1. That the list of Controls (GUiProperties) changes in each xml to show only the properties supported in that xml. </p><p>2. When you select a control type (which you cannot do at present), a drop down box lists the control types available/supported for that control. Obviously this applies mostly to text controls. For example, in some cases, MP/Plugin only supports a label type on a text control, in other cases it only supports a fadelabel. Some images can be centered/zoomed, etc, some can not. </p><p></p><p>You can add a control to the xml as much as you like, but if it is not supported, no data will display, or it will result in an error when you try to open the GUI window. However, this may be beyond the scope of a skin editor. Afaik there is no documentation anywhere about what properties are supported/unsupported in a window/xml. So I don't know how you would implement this. At present, most skinners just use trial and error, which is very time consuming, unless they have the ability to access and understand the MP code. I was just mentioning it, and asking if it was possible, because it is one of the huge problems in skinning.</p><p></p><p>When using Text controls, I would also love a drop down box under Control Text - Text that shows me available properties in that xml. </p><p></p><p>Another possible feature - when you select a Guiproperty from the list of controls - highlight all existing controls using that property. Not essential, but nice!</p><p></p><p>Don't mind all my suggestions. I don't know what is easy/possible for you to do or not, so I am just giving you feedback hoping it might be relevant. Since I am just getting to know the editor some of my points may not be relevant.</p><p></p><p>BTW there is a typo - "alignement' should be "alignment" in the Control Text Properties box and elsewhere.</p></blockquote><p></p>
[QUOTE="Dadeo, post: 518910, member: 27204"] Your example makes sense, but consider text - often I wish to change between a label, fadelabel, textbox, or textboxscrollup while preserving position, font, text color and other properties. As you say, I can just remove the control and input a new one. Perhaps when I get used to using the Skin Editor this will be easy to do. Not all xmls support all properties (though imo they should!), so that list of controls on the left, showing GUIproperties will not always be accurate for the window you are working in. My suggestion was twofold: 1. That the list of Controls (GUiProperties) changes in each xml to show only the properties supported in that xml. 2. When you select a control type (which you cannot do at present), a drop down box lists the control types available/supported for that control. Obviously this applies mostly to text controls. For example, in some cases, MP/Plugin only supports a label type on a text control, in other cases it only supports a fadelabel. Some images can be centered/zoomed, etc, some can not. You can add a control to the xml as much as you like, but if it is not supported, no data will display, or it will result in an error when you try to open the GUI window. However, this may be beyond the scope of a skin editor. Afaik there is no documentation anywhere about what properties are supported/unsupported in a window/xml. So I don't know how you would implement this. At present, most skinners just use trial and error, which is very time consuming, unless they have the ability to access and understand the MP code. I was just mentioning it, and asking if it was possible, because it is one of the huge problems in skinning. When using Text controls, I would also love a drop down box under Control Text - Text that shows me available properties in that xml. Another possible feature - when you select a Guiproperty from the list of controls - highlight all existing controls using that property. Not essential, but nice! Don't mind all my suggestions. I don't know what is easy/possible for you to do or not, so I am just giving you feedback hoping it might be relevant. Since I am just getting to know the editor some of my points may not be relevant. BTW there is a typo - "alignement' should be "alignment" in the Control Text Properties box and elsewhere. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Development
General Development (no feature request here!)
Is there a need for a skin editor?
Contact us
RSS
Top
Bottom