MultiImage Control: Difference between revisions

From Official Kodi Wiki
Jump to navigation Jump to search
>Gamester17
No edit summary
>Jmarshall
Line 23: Line 23:
For the <texture> tags, and for all <texture> tags in other controls, there is a small set of rules that you should follow if at all possible:
For the <texture> tags, and for all <texture> tags in other controls, there is a small set of rules that you should follow if at all possible:
====Size====
====Size====
Images should be as close as possible to the nearest highest power of 2 in width and height. The reason for this is XBMC uses swizzled textures which are quicker to render and quicker to load once they're compressed into the Textures.xpr file. Note that the image does not need to be square, and will not be scaled into a power of 2 size. Rather, any pixels outside of a power of two size will simply be dead space (wasted memory). For example, an image of size 513x513 pixels will use 4 times the memory as one of size 512x512. The XBMCTex program that does the image injection into Textures.xpr will warn you of this, but it pays to know it before you start.
Images can be any size you like if background loading them from outside the Textures.xpr file, though using anything larger than the size of the control you're rendering is a waste of processor and memory. If they're in Textures.xpr, then they're usually contained within textures that are a multiple of 64 pixels wide.
 
For optimal memory consumption, then, a multiple of 64 pixels wide should be used.
 
For non-xbox platforms, this is a moot point.


====Formats====
====Formats====

Revision as of 05:10, 12 July 2009

The MultiImage control is used for displaying a slideshow of images from a folder in XBMC. You can choose the position and size of the slideshow, as well as timing information.

Example

<xml> <control type="multiimage" id="1">

     <description>My first slideshow control</description>
     <posx>80</posx>
     <posy>60</posy>
     <width>250</width>
     <height>200</height>
     <visible>true</visible>
     <imagepath>myimagepath</imagepath>
     <info></info>
     <timeperimage>5000</timeperimage>
     <fadetime>2000</fadetime>
     <pauseatend>10000</pauseatend>
     <randomize>true</randomize>
     <loop>no</loop>
     <aspectratio>stretch</aspectratio>

</control> </xml>

Image Size and Type Restrictions

For the <texture> tags, and for all <texture> tags in other controls, there is a small set of rules that you should follow if at all possible:

Size

Images can be any size you like if background loading them from outside the Textures.xpr file, though using anything larger than the size of the control you're rendering is a waste of processor and memory. If they're in Textures.xpr, then they're usually contained within textures that are a multiple of 64 pixels wide.

For optimal memory consumption, then, a multiple of 64 pixels wide should be used.

For non-xbox platforms, this is a moot point.

Formats

If you wish to use full 8 bit transparency, then use PNG. If you only need a single transparent colour, then you can specify this in the <colorkey> tag, so any image will be fine. It is suggested that you use PNG and JPG as much as possible. Note that once the images are injected into Textures.xpr, they are not stored as JPG or PNG – rather they are stored in a xbox native format for faster loading. The size of the images (in kb) is therefore not as important as the size of the images in pixels – so feel free to store them in a lossless (eg PNG) manner if you wish.

The only exception to this is if you require an animated texture. In this case, we only support animated GIF. There are also SOME animated gifs that may not work. Use ImageReady CS and make sure you set the gif-anim to “restore to background” and they should work fine.

Available Tags and Attributes

In addition to the default control tags, the following tags are available. Note that each tag is lower case only. This is important, as xml tags are case-sensitive.

imagepath Specifies the path containing the images to use for the slideshow. XBMC will first look inside the compressed Textures.xpr file for images, and then will look in the actual folder. The path is relative to the media/ folder if it is not specified completely. It must be a local path (ie on the local harddisk) for speed purposes.
info Specifies the information that this image control is presenting. XBMC will select the texture to use based on this tag. See here for more information.
timeperimage Time in milliseconds that an image is shown for.
fadetime Time in milliseconds to fade between images.
pauseatend Time in milliseconds to pause (in addition to <timeperimage>) on the last image at the end of a complete cycle through the images. Only useful if <loop> is set to yes.
loop If set to no, the last image will display indefinitely. Setting it to yes will loop around once they reach the last image. Defaults to yes.
aspectratio This specifies how the image will be drawn inside the box defined by <width> and <height>. When set to “keep” the images aspect ratio will be kept, and the image will be resized to fit inside the <width>,<height> box (with transparent bars if the ratios are not the same). When set to “stretch”, the image will be stretched to <width> by <height> pixels (it's aspect ratio will therefore be lost). When set to “scale” then the box will be resized so that it completely fills the <width>,<height> box and any portions of the image outside the box will be cropped off.