include confusion
#31
The best thing might be to open a ticket on trac with the schema attached (and a link back to this forum thread).

Cheers,
Jonathan
Always read the XBMC online-manual, FAQ and search the forum before posting.
Do not e-mail XBMC-Team members directly asking for support. Read/follow the forum rules.
For troubleshooting and bug reporting please make sure you read this first.


Image
Reply
#32
ok. it's here:

http://trac.xbmc.org/ticket/9691

and contains (among other things) this:

<xs:element name="defaultcontrol">
<xs:complexType>
<xsConfusedimpleContent>
<xs:extension base="xsConfusedtring">
<xs:attribute type="xsConfusedtring" name="always" use="optional"/>
<xs:attribute type="xsConfusedtring" name="allways" use="optional"/>
</xs:extension>
</xsConfusedimpleContent>
</xs:complexType>
</xs:element>
Reply
#33
and for your question from the other thread ... i don't really see the actual window names (or ids, for that matter) in the schema - in most cases, they appear as 1:many relations in the document, and they're extensible (think custom windows). and also, it seems that <control id="1000"/> (for example) has different meanings, depending on the window it is in.
Reply

Logout Mark Read Team Forum Stats Members Help
include confusion0