Reply to thread

Message: <blockquote data-quote="Dadeo" data-source="post: 517799" data-attributes="member: 27204">Finally got around to testing again, on Alpha 4. It's really coming along!  Have you implemented the properties.xml yet?  I still get a message in the lower left saying "properties.xml not found" although the file is there in the folder with the skin editor.Perhaps the editor already handles some of the following, but it is not evident to me:How do you access 'layered' controls/elements?  For example:<ol> <li data-xf-list-type="ol">Hidden/sliding Menus - which only display when the user presses a key as defined by a navigation control on the facade (e.g. onleft>2) </li> <li data-xf-list-type="ol">Several layouts defined in one xml - e.g. Artist/Album/Genre Views (mymusicgenres.xml ), Main/Details View (movingpictures.xml) or Series/Season/Episode Views (TVSeries.xml)</li> <li data-xf-list-type="ol">Different facades (i.e. List, Small Icons, Large Icons, Big Icons List, Filmstrip) - often controls vary based on the visibility conditions defined for each facade.  For example a textscrollup type control for Plot may be defined differently for each facade within the same xml. </li> </ol>Lftearme already raised this issue (re conditional visibility) in a previous post.  My preferred solution would be like Bleazle suggested - to enable layers with a checkbox to overlay whichever layer you wish to view.  For example, if I check/select Filmstrip Layer, I would see all the controls with 'facadeview.filmstrip' in a visibility control.  Or in TV Series, if I select Episode Layer, I would see all the controls with Control.IsVisible(1239).  If I check all visibility boxes I can compare elements in the different views and even copy and paste them between layers!As it is currently, how do I select elements that are 'behind' other elements?  You can see what I mean in the attached screenshot, which is mymusicgenres.xml from the default Blue3 Skin.  I am unable to even select many of those elements.Here's a few more suggestions:<ol> <li data-xf-list-type="ol">Show the skin resolution on the top bar (you can grab that from the top of references.xml)</li> <li data-xf-list-type="ol">For the top and side rulers it would be nice to be able to see what positions they refer to.  Or even just a 0 at top 576 at bottom (if 720x576) and a couple intermediary references like at 25%, 50% and 75% of height (e.g. 144, 288, 432)</li> <li data-xf-list-type="ol">Drop Down boxes ( as I previously suggested, but with more detail <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile    :)" loading="lazy" data-shortname=":)" />)<ul> <li data-xf-list-type="ul">Navigation tags - when you select the box to enter an ID for onleft/onright/onup/ondown, display a list of all Control IDs used in the current window (xml). This is the same idea as what you have done for selecting Hover images in BasicHome.</li> <li data-xf-list-type="ul">Hyperlinks - I don't see hyperlinks listed as a property yet,  but when you add it, when I select the box to enter a hyperlink I would like a list of all the current Window IDs that can be used</li> <li data-xf-list-type="ul">Control Types - these are currently greyed out, so you cannot change the control type of an element.  However, what I would like is to select the box for a control type and have a drop down box/list of all the control types that are supported for that control in that window, if possible.  At least, I would like a list of all types.</li> </ul></li> </ol>I think what you have done is already fantastic, so if you can't do all or any of the above, the editor is still very useful.  The most important for me is to have some way to access or view 'layered' elements.BTW +1 For Pascal's suggestion for drag and drop of hierarchy and properties, and even the skinning window.Thanks for all the great work on this. I will keep testing and giving more feedback!</blockquote>

Verification