Window Structure - Revision history

Enen92: Changes for v20

2022-01-30T10:12:31Z

Changes for v20

← Older revision		Revision as of 10:12, 30 January 2022
Line 50:		Line 50:
	: Specifies whether the window needs clearing prior to rendering, and if so which colour to use. Defaults to clearing to black. Set to 0 (or 0x00000000) to have no clearing at all. If your skin always renders opaque textures over the entire screen (eg using a backdrop image or multiple backdrop images) then setting the background color to 0 is the most optimal value and may improve performance significantly on slow GPUs.		: Specifies whether the window needs clearing prior to rendering, and if so which colour to use. Defaults to clearing to black. Set to 0 (or 0x00000000) to have no clearing at all. If your skin always renders opaque textures over the entire screen (eg using a backdrop image or multiple backdrop images) then setting the background color to 0 is the most optimal value and may improve performance significantly on slow GPUs.
	; visible		; visible
	: Specifies the conditions under which a dialog will be visible. Kodi evaluates this at render time, and shows or hides a dialog depending on the evaluation of this tag. [[Conditional_visibility\|See here for more details.]] '''Applies only to type="dialog" windows.'''		: Specifies the conditions under which a dialog will be visible. Kodi evaluates this at render time, and shows or hides a dialog depending on the evaluation of this tag. [[Conditional_visibility\|See here for more details.]] '''Applies only to type="dialog" windows.'''. By default if a dialog visibility depends on visible condition it will be set as Modeless. A modeless dialog won't be able to catch input as any keystroke/action will be sent to the underlying window. Since v20 you can override this behaviour by setting '''modality="modal"''' on the root element of the window/dialog XML definition.
	; animation		; animation
	: Specifies the animation effect to perform when opening or closing the window. [[Animating_your_skin\|See here for more details.]]		: Specifies the animation effect to perform when opening or closing the window. [[Animating_your_skin\|See here for more details.]]

Karellen at 20:59, 28 August 2020

2020-08-28T20:59:23Z

← Older revision		Revision as of 20:59, 28 August 2020
Line 40:		Line 40:

	; onload		; onload
	: Optional: the [[~~List of Built In Functions~~\|build-in function]] to execute when the window opens		: Optional: the [[List_of_built-in_functions\|build-in function]] to execute when the window opens
	; onunload		; onunload
	: Optional: the [[~~List of Built In Functions~~\|build-in function]] to execute when the window closes		: Optional: the [[List_of_built-in_functions\|build-in function]] to execute when the window closes
	; defaultcontrol		; defaultcontrol
	: This specifies the default control of the window. This is the id of the control that will receive focus when the window is first opened. Note that most Kodi windows save the current focus when you leave the window, and will return to the last focused item when you return to a window. This behaviour can be stopped by specifying the attribute always="true".		: This specifies the default control of the window. This is the id of the control that will receive focus when the window is first opened. Note that most Kodi windows save the current focus when you leave the window, and will return to the last focused item when you return to a window. This behaviour can be stopped by specifying the attribute always="true".
Line 50:		Line 50:
	: Specifies whether the window needs clearing prior to rendering, and if so which colour to use. Defaults to clearing to black. Set to 0 (or 0x00000000) to have no clearing at all. If your skin always renders opaque textures over the entire screen (eg using a backdrop image or multiple backdrop images) then setting the background color to 0 is the most optimal value and may improve performance significantly on slow GPUs.		: Specifies whether the window needs clearing prior to rendering, and if so which colour to use. Defaults to clearing to black. Set to 0 (or 0x00000000) to have no clearing at all. If your skin always renders opaque textures over the entire screen (eg using a backdrop image or multiple backdrop images) then setting the background color to 0 is the most optimal value and may improve performance significantly on slow GPUs.
	; visible		; visible
	: Specifies the conditions under which a dialog will be visible. Kodi evaluates this at render time, and shows or hides a dialog depending on the evaluation of this tag. [[~~Conditional Visibility~~\|See here for more details.]] '''Applies only to type="dialog" windows.'''		: Specifies the conditions under which a dialog will be visible. Kodi evaluates this at render time, and shows or hides a dialog depending on the evaluation of this tag. [[Conditional_visibility\|See here for more details.]] '''Applies only to type="dialog" windows.'''
	; animation		; animation
	: Specifies the animation effect to perform when opening or closing the window. [[~~Animating Your Skin~~\|See here for more details.]]		: Specifies the animation effect to perform when opening or closing the window. [[Animating_your_skin\|See here for more details.]]
	; zorder		; zorder
	: This specifies the “depth” that the window should be drawn at. Windows with higher zorder are drawn on top of windows with lower z-order. All dialogs by default have zorder 1, so if you have a particular dialog that you want underneath all others, give it a zorder of 0. (Note that the normal render order is: The base window, then the overlays (music + video), then dialogs. <zorder> only effects the rendering of the dialogs.		: This specifies the “depth” that the window should be drawn at. Windows with higher zorder are drawn on top of windows with lower z-order. All dialogs by default have zorder 1, so if you have a particular dialog that you want underneath all others, give it a zorder of 0. (Note that the normal render order is: The base window, then the overlays (music + video), then dialogs. <zorder> only effects the rendering of the dialogs.

Ronie: /* Adding Extra Windows */

2016-07-01T18:46:12Z

Adding Extra Windows

← Older revision		Revision as of 18:46, 1 July 2016
Line 82:		Line 82:
	All of the windows in the [[Window IDs\|window list]] are defined within the executable of Kodi itself, as most of them have a specific purpose. However, the skinner may add extra windows as and when they are needed or wanted. The only restriction to this is that only controls that do not require specific source code to operate can be used. This is not too much of a restriction though, as many skinners have found out.		All of the windows in the [[Window IDs\|window list]] are defined within the executable of Kodi itself, as most of them have a specific purpose. However, the skinner may add extra windows as and when they are needed or wanted. The only restriction to this is that only controls that do not require specific source code to operate can be used. This is not too much of a restriction though, as many skinners have found out.

	To add an extra window, all you need to do is design up the window's .xml file in the usual way, assign it an <id> ~~outside of the ones defined in~~ the [[Window IDs\|window list]], and then name the file customN.xml, where N is a number or name. You can have as many as you like, as long as they have unique <id>'s, and are named differently. Then just define the type of window you want, the coordinate system and so on, add the controls and setup the navigation. To activate your window, you can do it by adding a button control elsewhere in the skin, or you can get it to popup on a press of the controller or remote via keymap.xml and so on. Basically you just need to run ActivateWindow(id) from a suitable place.		To add an extra window, all you need to do is design up the window's .xml file in the usual way, assign it an <id> within the 1100–1199 range (see [[Window IDs\|window list]]), and then name the file customN.xml, where N is a number or name. You can have as many as you like, as long as they have unique <id>'s, and are named differently. Then just define the type of window you want, the coordinate system and so on, add the controls and setup the navigation. To activate your window, you can do it by adding a button control elsewhere in the skin, or you can get it to popup on a press of the controller or remote via keymap.xml and so on. Basically you just need to run ActivateWindow(id) from a suitable place.

	<section end="main content" />		<section end="main content" />

	[[Category:Skin development]]		[[Category:Skin development]]

Ronie: /* Window Header */

2016-04-09T12:13:01Z

Window Header

← Older revision		Revision as of 12:13, 9 April 2016
Line 62:		Line 62:
	: Sets the vertical “origin” position of the window. Defaults to 0 if not present.		: Sets the vertical “origin” position of the window. Defaults to 0 if not present.
	; origin		; origin
	: Sets a conditional origin for the window. The window will display at (x,y) whenever the origin condition is met. You can have as many origin tags as you like – they are evaluated in the order present in the file, and the first one for which the condition is met wins. If none of the origin conditions are met, we fall back to the <~~posx~~> and <~~posy~~> tags.		: Sets a conditional origin for the window. The window will display at (x,y) whenever the origin condition is met. You can have as many origin tags as you like – they are evaluated in the order present in the file, and the first one for which the condition is met wins. If none of the origin conditions are met, we fall back to the <left> and <top> tags.
	; previouswindow		; previouswindow
	: This can be used to specify a window to force Kodi to go to on press of the Back button. Normally Kodi keeps a “window stack” of previous windows to handle this. This tag allows you to override this behaviour. The value is the name of the window.		: This can be used to specify a window to force Kodi to go to on press of the Back button. Normally Kodi keeps a “window stack” of previous windows to handle this. This tag allows you to override this behaviour. The value is the name of the window.

Ronie: /* Window Header */

2016-04-09T12:12:12Z

Window Header

← Older revision		Revision as of 12:12, 9 April 2016
Line 24:		Line 24:
	<zorder>1</zorder>		<zorder>1</zorder>
	<coordinates>		<coordinates>
	<~~posx~~>40</~~posx~~>		<left>40</left>
	<~~posy~~>50</~~posy~~>		<top>50</top>
	<origin x="100" y="50">Window.IsActive(Home)</origin>		<origin x="100" y="50">Window.IsActive(Home)</origin>
	</coordinates>		</coordinates>
Line 57:		Line 57:
	; coordinates		; coordinates
	: This block is used to specify how Kodi should compute the coordinates of all controls.		: This block is used to specify how Kodi should compute the coordinates of all controls.
	; ~~posx~~		; left
	: Sets the horizontal “origin” position of the window. Defaults to 0 if not present.		: Sets the horizontal “origin” position of the window. Defaults to 0 if not present.
	; ~~posy~~		; top
	: Sets the vertical “origin” position of the window. Defaults to 0 if not present.		: Sets the vertical “origin” position of the window. Defaults to 0 if not present.
	; origin		; origin

Ronie: /* Window Header */

2015-11-12T20:25:41Z

Window Header

← Older revision		Revision as of 20:25, 12 November 2015
Line 17:		Line 17:
	<defaultcontrol always="false">2</defaultcontrol>		<defaultcontrol always="false">2</defaultcontrol>
	<menucontrol>9000</menucontrol>		<menucontrol>9000</menucontrol>
	~~<allowoverlay>yes</allowoverlay>~~
	<backgroundcolor>0xff00ff00</backgroundcolor>		<backgroundcolor>0xff00ff00</backgroundcolor>
	<views>50,51,509,510</views>		<views>50,51,509,510</views>
Line 50:		Line 49:
	; backgroundcolor		; backgroundcolor
	: Specifies whether the window needs clearing prior to rendering, and if so which colour to use. Defaults to clearing to black. Set to 0 (or 0x00000000) to have no clearing at all. If your skin always renders opaque textures over the entire screen (eg using a backdrop image or multiple backdrop images) then setting the background color to 0 is the most optimal value and may improve performance significantly on slow GPUs.		: Specifies whether the window needs clearing prior to rendering, and if so which colour to use. Defaults to clearing to black. Set to 0 (or 0x00000000) to have no clearing at all. If your skin always renders opaque textures over the entire screen (eg using a backdrop image or multiple backdrop images) then setting the background color to 0 is the most optimal value and may improve performance significantly on slow GPUs.
	~~; allowoverlay~~
	~~: Setting this tag to true, or yes, indicates that the music or video overlay may be shown when this window is active. If this tag is not present, the state of the previous (or parent) window is used.~~
	; visible		; visible
	: Specifies the conditions under which a dialog will be visible. Kodi evaluates this at render time, and shows or hides a dialog depending on the evaluation of this tag. [[Conditional Visibility\|See here for more details.]] '''Applies only to type="dialog" windows.'''		: Specifies the conditions under which a dialog will be visible. Kodi evaluates this at render time, and shows or hides a dialog depending on the evaluation of this tag. [[Conditional Visibility\|See here for more details.]] '''Applies only to type="dialog" windows.'''

Ronie at 21:38, 9 November 2015

2015-11-09T21:38:55Z

← Older revision		Revision as of 21:38, 9 November 2015
Line 16:		Line 16:
	<onunload>SetProperty(foo,bar)</onunload>		<onunload>SetProperty(foo,bar)</onunload>
	<defaultcontrol always="false">2</defaultcontrol>		<defaultcontrol always="false">2</defaultcontrol>
			<menucontrol>9000</menucontrol>
	<allowoverlay>yes</allowoverlay>		<allowoverlay>yes</allowoverlay>
	<backgroundcolor>0xff00ff00</backgroundcolor>		<backgroundcolor>0xff00ff00</backgroundcolor>
Line 45:		Line 46:
	; defaultcontrol		; defaultcontrol
	: This specifies the default control of the window. This is the id of the control that will receive focus when the window is first opened. Note that most Kodi windows save the current focus when you leave the window, and will return to the last focused item when you return to a window. This behaviour can be stopped by specifying the attribute always="true".		: This specifies the default control of the window. This is the id of the control that will receive focus when the window is first opened. Note that most Kodi windows save the current focus when you leave the window, and will return to the last focused item when you return to a window. This behaviour can be stopped by specifying the attribute always="true".
			; menucontrol
			: This specifies the control that will be focused when the users presses the 'menu' / 'm' button.
	; backgroundcolor		; backgroundcolor
	: Specifies whether the window needs clearing prior to rendering, and if so which colour to use. Defaults to clearing to black. Set to 0 (or 0x00000000) to have no clearing at all. If your skin always renders opaque textures over the entire screen (eg using a backdrop image or multiple backdrop images) then setting the background color to 0 is the most optimal value and may improve performance significantly on slow GPUs.		: Specifies whether the window needs clearing prior to rendering, and if so which colour to use. Defaults to clearing to black. Set to 0 (or 0x00000000) to have no clearing at all. If your skin always renders opaque textures over the entire screen (eg using a backdrop image or multiple backdrop images) then setting the background color to 0 is the most optimal value and may improve performance significantly on slow GPUs.

Ronie at 00:38, 23 January 2015

2015-01-23T00:38:47Z

← Older revision		Revision as of 00:38, 23 January 2015
Line 1:		Line 1:
	<section begin="main content" />		<section begin="main content" />
	==About the Window XML Files==		==About the Window XML Files==
	Each window in an ~~XBMC~~ skin is represented by a single .xml file. [[Window IDs\|See here for a list of the standard windows and links to their .xml files.]]<br /><br />		Each window in an Kodi skin is represented by a single .xml file. [[Window IDs\|See here for a list of the standard windows and links to their .xml files.]]<br /><br />

	The important thing to remember is that each window has a unique identifying name. This is how Kodi identifies the window from within the source code.		The important thing to remember is that each window has a unique identifying name. This is how Kodi identifies the window from within the source code.
Line 44:		Line 44:
	: Optional: the [[List of Built In Functions\|build-in function]] to execute when the window closes		: Optional: the [[List of Built In Functions\|build-in function]] to execute when the window closes
	; defaultcontrol		; defaultcontrol
	: This specifies the default control of the window. This is the id of the control that will receive focus when the window is first opened. Note that most ~~XBMC~~ windows save the current focus when you leave the window, and will return to the last focused item when you return to a window. This behaviour can be stopped by specifying the attribute always="true".		: This specifies the default control of the window. This is the id of the control that will receive focus when the window is first opened. Note that most Kodi windows save the current focus when you leave the window, and will return to the last focused item when you return to a window. This behaviour can be stopped by specifying the attribute always="true".
	; backgroundcolor		; backgroundcolor
	: Specifies whether the window needs clearing prior to rendering, and if so which colour to use. Defaults to clearing to black. Set to 0 (or 0x00000000) to have no clearing at all. If your skin always renders opaque textures over the entire screen (eg using a backdrop image or multiple backdrop images) then setting the background color to 0 is the most optimal value and may improve performance significantly on slow GPUs.		: Specifies whether the window needs clearing prior to rendering, and if so which colour to use. Defaults to clearing to black. Set to 0 (or 0x00000000) to have no clearing at all. If your skin always renders opaque textures over the entire screen (eg using a backdrop image or multiple backdrop images) then setting the background color to 0 is the most optimal value and may improve performance significantly on slow GPUs.
Line 50:		Line 50:
	: Setting this tag to true, or yes, indicates that the music or video overlay may be shown when this window is active. If this tag is not present, the state of the previous (or parent) window is used.		: Setting this tag to true, or yes, indicates that the music or video overlay may be shown when this window is active. If this tag is not present, the state of the previous (or parent) window is used.
	; visible		; visible
	: Specifies the conditions under which a dialog will be visible. ~~XBMC~~ evaluates this at render time, and shows or hides a dialog depending on the evaluation of this tag. [[Conditional Visibility\|See here for more details.]] '''Applies only to <type>dialog~~</type>~~.'''		: Specifies the conditions under which a dialog will be visible. Kodi evaluates this at render time, and shows or hides a dialog depending on the evaluation of this tag. [[Conditional Visibility\|See here for more details.]] '''Applies only to type="dialog" windows.'''
	; animation		; animation
	: Specifies the animation effect to perform when opening or closing the window. [[Animating Your Skin\|See here for more details.]]		: Specifies the animation effect to perform when opening or closing the window. [[Animating Your Skin\|See here for more details.]]
Line 56:		Line 56:
	: This specifies the “depth” that the window should be drawn at. Windows with higher zorder are drawn on top of windows with lower z-order. All dialogs by default have zorder 1, so if you have a particular dialog that you want underneath all others, give it a zorder of 0. (Note that the normal render order is: The base window, then the overlays (music + video), then dialogs. <zorder> only effects the rendering of the dialogs.		: This specifies the “depth” that the window should be drawn at. Windows with higher zorder are drawn on top of windows with lower z-order. All dialogs by default have zorder 1, so if you have a particular dialog that you want underneath all others, give it a zorder of 0. (Note that the normal render order is: The base window, then the overlays (music + video), then dialogs. <zorder> only effects the rendering of the dialogs.
	; coordinates		; coordinates
	: This block is used to specify how ~~XBMC~~ should compute the coordinates of all controls.		: This block is used to specify how Kodi should compute the coordinates of all controls.
	; posx		; posx
	: Sets the horizontal “origin” position of the window. Defaults to 0 if not present.		: Sets the horizontal “origin” position of the window. Defaults to 0 if not present.
Line 64:		Line 64:
	: Sets a conditional origin for the window. The window will display at (x,y) whenever the origin condition is met. You can have as many origin tags as you like – they are evaluated in the order present in the file, and the first one for which the condition is met wins. If none of the origin conditions are met, we fall back to the <posx> and <posy> tags.		: Sets a conditional origin for the window. The window will display at (x,y) whenever the origin condition is met. You can have as many origin tags as you like – they are evaluated in the order present in the file, and the first one for which the condition is met wins. If none of the origin conditions are met, we fall back to the <posx> and <posy> tags.
	; previouswindow		; previouswindow
	: This can be used to specify a window to force ~~XBMC~~ to go to on press of the Back button. Normally ~~XBMC~~ keeps a “window stack” of previous windows to handle this. This tag allows you to override this behaviour. The value is the name of the window.		: This can be used to specify a window to force Kodi to go to on press of the Back button. Normally Kodi keeps a “window stack” of previous windows to handle this. This tag allows you to override this behaviour. The value is the name of the window.
	; views		; views
	: This tag lets you use view id's beyond 50 to 59 it also lets you set the order in which they cycle with the change view button in the skin. Only useful in My<Foo>.xml windows.		: This tag lets you use view id's beyond 50 to 59 it also lets you set the order in which they cycle with the change view button in the skin. Only useful in My<Foo>.xml windows.
Line 72:		Line 72:
	=== The Different Types of Controls ===		=== The Different Types of Controls ===

	~~XBMC~~ supports many different types of controls.		Kodi supports many different types of controls.

	[[Controls\|Click here for the control types and what they all do.]]		[[Controls\|Click here for the control types and what they all do.]]
Line 80:		Line 80:
	=== Adding Extra Windows ===		=== Adding Extra Windows ===

	All of the windows in the [[Window IDs\|window list]] are defined within the ~~executeable~~ of ~~XBMC~~ itself, as most of them have a specific purpose. However, the skinner may add extra windows as and when they are needed or wanted. The only restriction to this is that only controls that do not require specific source code to operate can be used. This is not too much of a restriction though, as many skinners have found out.		All of the windows in the [[Window IDs\|window list]] are defined within the executable of Kodi itself, as most of them have a specific purpose. However, the skinner may add extra windows as and when they are needed or wanted. The only restriction to this is that only controls that do not require specific source code to operate can be used. This is not too much of a restriction though, as many skinners have found out.

	To add an extra window, all you need to do is design up the window's .xml file in the usual way, assign it an <id> outside of the ones defined in the [[Window IDs\|window list]], and then name the file customN.xml, where N is a number. You can have as many as you like, as long as they have unique <id>'s, and are named differently. Then just define the <type> of window you want, the coordinate system and so on, add the controls and setup the navigation. To activate your window, you can do it by adding a button control elsewhere in the skin, or you can get it to popup on a press of the controller or remote via keymap.xml and so on. Basically you just need to run ~~XBMC.~~ActivateWindow(id) from a suitable place.		To add an extra window, all you need to do is design up the window's .xml file in the usual way, assign it an <id> outside of the ones defined in the [[Window IDs\|window list]], and then name the file customN.xml, where N is a number or name. You can have as many as you like, as long as they have unique <id>'s, and are named differently. Then just define the type of window you want, the coordinate system and so on, add the controls and setup the navigation. To activate your window, you can do it by adding a button control elsewhere in the skin, or you can get it to popup on a press of the controller or remote via keymap.xml and so on. Basically you just need to run ActivateWindow(id) from a suitable place.

	<section end="main content" />		<section end="main content" />

	[[Category:Skin development]]		[[Category:Skin development]]

Ronie: merge duplicate info

2014-12-31T02:01:10Z

merge duplicate info

← Older revision		Revision as of 02:01, 31 December 2014
Line 2:		Line 2:
	==About the Window XML Files==		==About the Window XML Files==
	Each window in an XBMC skin is represented by a single .xml file. [[Window IDs\|See here for a list of the standard windows and links to their .xml files.]]<br /><br />		Each window in an XBMC skin is represented by a single .xml file. [[Window IDs\|See here for a list of the standard windows and links to their .xml files.]]<br /><br />

			The important thing to remember is that each window has a unique identifying name. This is how Kodi identifies the window from within the source code.
			The window names are all listed in the Appendix I: List of Windows.

	Each .xml file has the same basic structure – it starts with some heading information that pertains to the window as a whole, and then contains a <controls> block within which all the controls that describe the window are defined.		Each .xml file has the same basic structure – it starts with some heading information that pertains to the window as a whole, and then contains a <controls> block within which all the controls that describe the window are defined.
			Many of the controls within each window should have a unique id's, unless they're just used as images or labels where navigation is unimportant and Kodi does not need to be able to identify them uniquely.

	== Window Header ==		== Window Header ==

NedBot: Robot: Substituting template: Name

2014-06-05T20:10:54Z

Robot: Substituting template: Name

← Older revision		Revision as of 20:10, 5 June 2014
Line 1:		Line 1:
	<section begin="main content" />		<section begin="main content" />
	==About the Window XML Files==		==About the Window XML Files==
	Each window in an ~~{{name}}~~ skin is represented by a single .xml file. [[Window IDs\|See here for a list of the standard windows and links to their .xml files.]]<br /><br />		Each window in an XBMC skin is represented by a single .xml file. [[Window IDs\|See here for a list of the standard windows and links to their .xml files.]]<br /><br />
	Each .xml file has the same basic structure – it starts with some heading information that pertains to the window as a whole, and then contains a <controls> block within which all the controls that describe the window are defined.		Each .xml file has the same basic structure – it starts with some heading information that pertains to the window as a whole, and then contains a <controls> block within which all the controls that describe the window are defined.

Line 39:		Line 39:
	: Optional: the [[List of Built In Functions\|build-in function]] to execute when the window closes		: Optional: the [[List of Built In Functions\|build-in function]] to execute when the window closes
	; defaultcontrol		; defaultcontrol
	: This specifies the default control of the window. This is the id of the control that will receive focus when the window is first opened. Note that most ~~{{name}}~~ windows save the current focus when you leave the window, and will return to the last focused item when you return to a window. This behaviour can be stopped by specifying the attribute always="true".		: This specifies the default control of the window. This is the id of the control that will receive focus when the window is first opened. Note that most XBMC windows save the current focus when you leave the window, and will return to the last focused item when you return to a window. This behaviour can be stopped by specifying the attribute always="true".
	; backgroundcolor		; backgroundcolor
	: Specifies whether the window needs clearing prior to rendering, and if so which colour to use. Defaults to clearing to black. Set to 0 (or 0x00000000) to have no clearing at all. If your skin always renders opaque textures over the entire screen (eg using a backdrop image or multiple backdrop images) then setting the background color to 0 is the most optimal value and may improve performance significantly on slow GPUs.		: Specifies whether the window needs clearing prior to rendering, and if so which colour to use. Defaults to clearing to black. Set to 0 (or 0x00000000) to have no clearing at all. If your skin always renders opaque textures over the entire screen (eg using a backdrop image or multiple backdrop images) then setting the background color to 0 is the most optimal value and may improve performance significantly on slow GPUs.
Line 45:		Line 45:
	: Setting this tag to true, or yes, indicates that the music or video overlay may be shown when this window is active. If this tag is not present, the state of the previous (or parent) window is used.		: Setting this tag to true, or yes, indicates that the music or video overlay may be shown when this window is active. If this tag is not present, the state of the previous (or parent) window is used.
	; visible		; visible
	: Specifies the conditions under which a dialog will be visible. ~~{{name}}~~ evaluates this at render time, and shows or hides a dialog depending on the evaluation of this tag. [[Conditional Visibility\|See here for more details.]] '''Applies only to <type>dialog</type>.'''		: Specifies the conditions under which a dialog will be visible. XBMC evaluates this at render time, and shows or hides a dialog depending on the evaluation of this tag. [[Conditional Visibility\|See here for more details.]] '''Applies only to <type>dialog</type>.'''
	; animation		; animation
	: Specifies the animation effect to perform when opening or closing the window. [[Animating Your Skin\|See here for more details.]]		: Specifies the animation effect to perform when opening or closing the window. [[Animating Your Skin\|See here for more details.]]
Line 51:		Line 51:
	: This specifies the “depth” that the window should be drawn at. Windows with higher zorder are drawn on top of windows with lower z-order. All dialogs by default have zorder 1, so if you have a particular dialog that you want underneath all others, give it a zorder of 0. (Note that the normal render order is: The base window, then the overlays (music + video), then dialogs. <zorder> only effects the rendering of the dialogs.		: This specifies the “depth” that the window should be drawn at. Windows with higher zorder are drawn on top of windows with lower z-order. All dialogs by default have zorder 1, so if you have a particular dialog that you want underneath all others, give it a zorder of 0. (Note that the normal render order is: The base window, then the overlays (music + video), then dialogs. <zorder> only effects the rendering of the dialogs.
	; coordinates		; coordinates
	: This block is used to specify how ~~{{name}}~~ should compute the coordinates of all controls.		: This block is used to specify how XBMC should compute the coordinates of all controls.
	; posx		; posx
	: Sets the horizontal “origin” position of the window. Defaults to 0 if not present.		: Sets the horizontal “origin” position of the window. Defaults to 0 if not present.
Line 59:		Line 59:
	: Sets a conditional origin for the window. The window will display at (x,y) whenever the origin condition is met. You can have as many origin tags as you like – they are evaluated in the order present in the file, and the first one for which the condition is met wins. If none of the origin conditions are met, we fall back to the <posx> and <posy> tags.		: Sets a conditional origin for the window. The window will display at (x,y) whenever the origin condition is met. You can have as many origin tags as you like – they are evaluated in the order present in the file, and the first one for which the condition is met wins. If none of the origin conditions are met, we fall back to the <posx> and <posy> tags.
	; previouswindow		; previouswindow
	: This can be used to specify a window to force ~~{{name}}~~ to go to on press of the Back button. Normally ~~{{name}}~~ keeps a “window stack” of previous windows to handle this. This tag allows you to override this behaviour. The value is the name of the window.		: This can be used to specify a window to force XBMC to go to on press of the Back button. Normally XBMC keeps a “window stack” of previous windows to handle this. This tag allows you to override this behaviour. The value is the name of the window.
	; views		; views
	: This tag lets you use view id's beyond 50 to 59 it also lets you set the order in which they cycle with the change view button in the skin. Only useful in My<Foo>.xml windows.		: This tag lets you use view id's beyond 50 to 59 it also lets you set the order in which they cycle with the change view button in the skin. Only useful in My<Foo>.xml windows.
Line 75:		Line 75:
	=== Adding Extra Windows ===		=== Adding Extra Windows ===

	All of the windows in the [[Window IDs\|window list]] are defined within the executeable of ~~{{name}}~~ itself, as most of them have a specific purpose. However, the skinner may add extra windows as and when they are needed or wanted. The only restriction to this is that only controls that do not require specific source code to operate can be used. This is not too much of a restriction though, as many skinners have found out.		All of the windows in the [[Window IDs\|window list]] are defined within the executeable of XBMC itself, as most of them have a specific purpose. However, the skinner may add extra windows as and when they are needed or wanted. The only restriction to this is that only controls that do not require specific source code to operate can be used. This is not too much of a restriction though, as many skinners have found out.

	To add an extra window, all you need to do is design up the window's .xml file in the usual way, assign it an <id> outside of the ones defined in the [[Window IDs\|window list]], and then name the file customN.xml, where N is a number. You can have as many as you like, as long as they have unique <id>'s, and are named differently. Then just define the <type> of window you want, the coordinate system and so on, add the controls and setup the navigation. To activate your window, you can do it by adding a button control elsewhere in the skin, or you can get it to popup on a press of the controller or remote via keymap.xml and so on. Basically you just need to run XBMC.ActivateWindow(id) from a suitable place.		To add an extra window, all you need to do is design up the window's .xml file in the usual way, assign it an <id> outside of the ones defined in the [[Window IDs\|window list]], and then name the file customN.xml, where N is a number. You can have as many as you like, as long as they have unique <id>'s, and are named differently. Then just define the <type> of window you want, the coordinate system and so on, add the controls and setup the navigation. To activate your window, you can do it by adding a button control elsewhere in the skin, or you can get it to popup on a press of the controller or remote via keymap.xml and so on. Basically you just need to run XBMC.ActivateWindow(id) from a suitable place.