Posts: 143
Joined: Feb 2017
Reputation:
0
Quoting from the link: "Some windows allow you to jump directly to a sub-section of that window." - that means "build in windows only"?
As for the views, I have not got to them yet, but as far as I can tell from Estuary, you just include all the views into fe. MyVideoNav and just switch some property (?) to make controls of one of the views visible, right?
Posts: 7,805
Joined: Feb 2013
Reputation:
1,484
2017-04-08, 05:24
(This post was last modified: 2017-04-08, 05:25 by jurialmunkey.)
Yeah that is for all the built-in MyXXXX windows (plus AddonBrowser which for some reason doesn't follow the naming scheme...)
You are correct about just including them in the corresponding window.
Each view id (of the list/panel control) is defined in the <views> tag in the window definitions.
Button id "2" is a built-in button that cycles visibility for each view id (which is the same as the command Container.NextViewMode, but button id 2 has an automatically filled label that tells you what viewtype is currently selected). You can then use Control.IsVisible(ID) to define what other elements should be visible along with the corresponding list control (e.g. you might want a separate big poster or box with info/plot etc.).
Each viewtype container usually has its own <visible> tags to define the conditions in which it should or should not be available.
e.g. <visible>Container.Content(tvshows)</visible> so that it is only used for tvshows content and not movies or genres etc.
Posts: 7,805
Joined: Feb 2013
Reputation:
1,484
No ID defined for the list control. Plus your <views> tag is defining IDs that are clearly not available.
Need
<views>50</views>
and
<control type="list" id="50">
Button control ID 2 cycles which list/panel id is visible as defined in the <views> tag.
Posts: 3,660
Joined: Feb 2008
Reputation:
93
Jeroen
Team-Kodi Member
Posts: 3,660
So, what have you done to improve the docs?