Integration Designer Image Group Format Specification

Version 1.1 January 2010

It’s Under Control and Integration Designer are trademarks of Remote Technologies Incorporated (RTI). 5775 12th Ave Southeast Suite 180 Shakopee. Third party product and brand names are the trademarks of their respective owners.Copyright © 2010 Remote Technologies Inc. Remote Technologies. registered in the United States and other countries. Remote Technologies Inc. RTI makes no warranty or representation. accuracy or completeness of the information contained herein. with respect to the quality. express or implied. MN 55372 USA 952-253-3100 . All rights reserved. the Remote Technologies logo. While RTI believes the information contained in this document to be accurate.

2 8 8.2 XML ELEMENTS AND ATTRIBUTES XML ELEMENTS AND ATTRIBUTES NOTES EXAMPLE XML ELEMENTS AND ATTRIBUTES GRAPH OBJECT RENDERING EXAMPLE 1: BAR GRAPH EXAMPLE 2: SLIDER XML ELEMENTS AND ATTRIBUTES EXAMPLE XML ELEMENTS AND ATTRIBUTES EXAMPLE XML ELEMENTS AND ATTRIBUTES EXAMPLE BITMAP GROUPS 4 5 5 5 6 6 7 7 9 9 11 12 12 13 13 13 15 15 16 17 17 19 GRAPH OBJECTS IMAGE LISTS TOGGLE BUTTONS ITEM LISTS Integration Designer Image Group Format Specification 3 .1 6.3 5 5.1 8.1 5.2 5.1 7.4 6 6.3 5.Table of Contents 1 2 3 4 INTRODUCTION IMAGE FILE NAMING CONVENTIONS COMMON XML ELEMENTS 3.2 4.1 4.1 4.2 7 7.

The four images provide the graphic for the pressed and not pressed state when the boolean variable is both False and True.png.tif. .bmp.group file and one or more graphic files. • Toggle Buttons (Page 15) o Bitmap Library Symbol: o Toggle Buttons consist of four images. • Image Lists (Page 13) o Bitmap Library symbol: o Image Lists are used to provide a sequence of images. in any file format that Integration Designer accepts (. beyond simple Up and Down state images. as a gauge or bar graph object.gif). • Item Lists (Page 17) o Bitmap Library Symbol: o Item Lists are the two-way equivalent of the scrolling list. The data for an Item List comes from a list system variable instead of being programmed into the data file. 4 Integration Designer Image Group Format Specification .jpg. Each of these graphic object types consist of an XML-formatted . and are used to show feedback based on a boolean system variable. • Graphs (Page 9) o Bitmap Library symbol: o Graphs are used to represent integer system variables graphically. and . . where only one image is shown at a time.1 Introduction Integration Designer has support for several types of complex graphics. based on the value of an integer system variable. because the graphics for the list and the highlighted item can be specified separately. • Bitmap Groups (Page 6) o Bitmap Library symbol: o Bitmap groups allow a set of related bitmaps (like a cursor control set) to be dragged from the Bitmap Library and placed on the page as a single unit. Item lists also have more flexibility in design than one-way scrolling lists. .

1 group This is the root element of the XML file. The Bitmap Library will only show the ^#UP image. Integration Designer Image Group Format Specification 5 . with two identical filenames (except for the ^#UP or ^#DOWN suffix) to provide Integration Designer with the Normal and Active images for a button. Indicates that the image should be used as a background. The suffix goes at the very end of the filename portion. grouped image is shown in the bitmap library and not the individual components. Indicates that the image should be used as a background.1 XML Elements and Attributes 3. with the background mode set to Tiled.1. but will assign both of them when dragged from the library.group extension. Every XML file has the following structure. 3. It has no attributes. This suffix is used with the individual files in a bitmap group so that only the final.2 Image File Naming Conventions Individual graphic files can have several suffixes attached to their filenames to indicate their intended use to Integration Designer. Indicates that the image should not be displayed in the Bitmap Library tab. with the background mode set to Centered. right before the file type extension. The following suffixes are defined: ^#UP / ^#DOWN Used in pairs. regardless of the image type it describes. Every image group must contain this element. ^#BGCENTER ^#BGTILE ^#HIDE 3 Common XML elements Each image group is defined by an XML file with the .

4 Bitmap Groups The Bitmap Group type is used to group a number of graphics together into a single unit that is dragged from the bitmap library all at once.1.3 y This attribute specifies the y coordinate where the upper-left hand corner of this image will be placed 4.2 x This attribute specifies the x coordinate where the upper-left hand corner of this image will be placed 4. When the Bitmap Group is dropped onto the page in Integration Designer. the button created for this image will have its inactive property set in Integration Designer.1.1 Image There should be exactly one image element inside of the group element. the individual graphics are turned into a number of separate buttons that can each have a command or macro attached to them. The value of this attribute is a filename that points to an image file in the same directory as the .2.2 tile There should be one tile element for each image tile that is a part of the group.1. 4. and the down. x. Set this property for all parts of the group which are decorative and are not intended to be used for triggering commands. For example. The individual bitmaps in the group. and y attributes are required.5 inactive If this attribute is present and set to “yes”. in any file format that can be loaded by Integration Designer.2. This image is a composite image of all the image tiles.1. 4. The sole attribute. 4.group file.2.1.2. 6 Integration Designer Image Group Format Specification . and will not respond to presses.1. If this attribute is not specified. sample references the image that will be shown in the bitmap library browser in Integration Designer. 4. called tiles. the image will not change when the button is pressed. inactive. 4.4 down This attribute specifies the filename for the image that will appear when the button is pressed (active). and is not actually placed into the file by Integration Designer. The up.1 up This attribute specifies the filename for the image that will appear when the button is not pressed. can have several properties pre-set as the buttons are created.1.2.1 XML Elements and Attributes 4. the non-functional decorative elements of the group can be marked as Inactive as the buttons are created. and sound attributes are optional.

3 Coordinate System The X and Y coordinates for each image tile are added to the current x and y position of the mouse when the group is dropped in Integration Designer to determine the final position of the buttons created for each image tile. 4.png"> Integration Designer Image Group Format Specification 7 .g.2. so it is possible to build multiple . The sample image name must be unique for each group file. Note that it is not possible to specify both the ^#UP (or ^#DOWN) and ^#HIDE tags simultaneously. then the filenames should end in ^#HIDE. 4.group file.2. the button beep will be set to the system default sound.5 Image File Naming If it is desired for any of the individual image tiles to show up in the bitmap library apart from the group (so that they can be dragged individually).2.group files offering slight variations while re-using most of the image tiles.4.2. 4. 4.1.0" encoding="utf-8" ?> <group> <image sample="Cursor Control (blank) Sample^#HIDE. This will cause Integration Designer to not show these bitmaps separately in the Bitmap Library browser – they will only be available as part of the group. this will be the folder with the rest of the bitmaps and template files. the Button Beep Sound will be set to (no sound).4 Z-Ordering The Integration Designer buttons for each image tile are created in the order of the tile statements in the .6 Image References It is permissible to reference the same image tiles from more than one . so if the group specifies images that overlap. but this is never necessary because the UP and DOWN usages of the bitmaps are specified by being assigned to the up or down tile attribute.1 Folder Structure All of the image tiles should be placed in the same folder as the . 4. the filename is the bitmap title.2. they should follow normal Integration Designer bitmap file naming conventions. If this attribute is not present. e. like in the example above.2. If this group is a part of a bitmap library.2 Sample Image The sample image must be sized so that it is exactly the same size as the bounding box created by the sizes of the images and their X and Y positions in the group file. optionally followed by ^#UP or ^#DOWN for buttons that are part of a normal/active pair.group file.2 Notes 4. If the bitmaps should NOT be shown separately. the tiles should be listed in back-to-front order in the .3 1 2 3 Example <?xml version="1.group file. 4.2.group file.6 sound If this attribute is present and set to “none”. 4.

png" x="172" y="64" /> <tile up="bottom left^#HIDE.png" x="67" y="64" /> <tile up="right^#HIDE.png (67x109) bottom left^#HIDE.png" inactive="yes" x="172" y="0" /> <tile up="left^#HIDE.png" inactive="yes" x="172" y="173" /> </image> </group> top left^#HIDE.png" down="right active^#HIDE.png" down="down active^#HIDE.png" x="67" y="0" /> <tile up="top right^#HIDE.png (67x64) left^#HIDE.png (67x109) enter blank^#HIDE.png" x="0" y="64" /> <tile up="enter blank^#HIDE.4 5 6 7 8 9 10 11 12 13 14 <tile up="top left^#HIDE.png 8 Integration Designer Image Group Format Specification .png (105x66) down active^#HIDE.png" x="67" y="173" /> <tile up="bottom right^#HIDE.png (105x64) up active^#HIDE.png" inactive="yes" x="0" y="173" /> <tile up="down^#HIDE.png (105x109) right^#HIDE.png (105x64) top right^#HIDE.png (67x66) down^#HIDE.png" down="left active^#HIDE.png" down="up active^#HIDE.png (105x66) bottom right^#HIDE.png" inactive="yes" x="0" y="0" /> <tile up="up^#HIDE.png (67x109) right active^#HIDE.png (67x66) Cursor Control (blank) Sample^#HIDE.png (67x64) up^#HIDE.png (67x109) left active^#HIDE.

5.1.1. in any file format that can be loaded by Integration Designer. 5. but is not used for anything on the device itself.1.1 XML Elements and Attributes 5. The section element.1. They encompass both gauge-type controls.1 graph There should be exactly one graph element inside of the group element.1 sample This mandatory attribute references the image that will be shown in the bitmap library browser in Integration Designer. with all the pieces composed into a single image and rendered assuming the attached system variable is at roughly 50%. and the various components are placed on that one image. The four possible values are: lefttoright righttoleft toptobottom bottomtotop.1.1.5 orientation This mandatory attribute sets the direction that the fill or marker moves as the variable changes. 5.4 height This mandatory attribute sets the height of the created Graph object. 5.group file. described below. It is a single image file.1. It must be equal to or larger than the height of the image referenced by the sample attribute. where the value of the variable is represented by a marker object that moves along the control. It contains the following attributes: 5.2 image This mandatory attribute references an image which contains the individual components that make up the graph object.3 width This mandatory attribute sets the width of the created Graph object. in any file format that can be loaded by Integration Designer.group file. where the value of the variable is represented by a difference in the portion of a control that is filled in and slider-type controls.1.1. describes the position of the individual components. 5. or another value that would be common to users of this object. This image is retained for display purposes in Integration Designer when the object is dragged into a system file. This image should be a representative sample of the appearance of the graph in actual use. The value of this attribute is a filename that points to an image file in the same directory as the .5 Graph Objects Graph objects are used to display integer system variables graphically. Integration Designer Image Group Format Specification 9 .1. It must be equal to or larger than the width of the image referenced by the sample attribute. The value of this attribute is a filename that points to an image file in the same directory as the .1.

regardless of the value of the variable attached to the object. below.6 startoffset This optional attribute specifies the number of pixels that will be skipped at the beginning of the graph rendering.1.1.1.7 endoffset This optional attribute specifies the number of pixels that will be skipped at the end of the graph rendering. The orientation attribute on the graph element specifies whether the bar fills in from the left. This attribute is intended to allow a rounded edge to be placed on the end of the bar that will move with the bar as it fills in.2. • marker The marker attribute specifies the graphic that will be moved along the graph. place the rounded cap for the beginning of the bar in the background image.1. The default value is 0 if not specified. • background-active • bar-active • endcap-active • marker-active 10 Integration Designer Image Group Format Specification .5. or bottom. This will always be completely drawn.2 section Inside the graph element are one or more section elements that describe which portion of the image referenced by the graph element’s image attribute makes up each part of the graph object.1. • endcap The endcap attribute specifies the graphic that will be painted at the end of the bar. top. 5. • bar The bar attribute specifies the graphic that will be partially drawn. The variable value will be scaled using the minimum and maximum values for the graph configured in Integration Designer. Most Graph objects will only need to specify a few of these types. The possible section types are described in the type attribute. and that fraction of the bar will be rendered. depending on the value of the variable attached to the object.1. To achieve the same affect at the beginning of the bar. depending on the value of the variable attached to the object. • background The background attribute specifies the graphic that will be drawn at the back of the graph object. Each type can only be specified once for any individual Graph object.1 type The type attribute can have one of the following values. 5. The default value is 0 if not specified. 5. right.

but are used when the button is reversed.1.2. but can be adjusted if necessary.2.1. Each of these elements may be partially or fully transparent. end cap.1 Render Order Graph objects are constructed by rendering the individual components in the order shown in Figure 1. For each use of the object in Integration Designer.1.1.4 width This attribute specifies the width of this section on the image.5 height This attribute specifies the height of this section on the image.2. 5.2 Value Scaling The position of the bar. 5. the graph will be rendered at either the minimum or maximum value as appropriate. This is done automatically when the variable is attached to the graph (provided the driver specifies a range for the variable).2. and marker are determined by the value of the integer system variable attached to the Graph object. either by setting the Reversed button property or by touching the button. if the source image provides an alpha channel.2.The attributes ending in -active have the same function as the non-active versions.2 Graph Object Rendering 5. the minimum and maximum values of the variable need to be configured. 5.2. If the system variable takes on an out-ofrange value.2 x This attribute specifies the x coordinate of the upper-left corner of this section on the image. and only the types actually specified in the group file are rendered. 5. background bar endcap marker Figure 1 : Graph object render order 5.3 y This attribute specifies the y coordinate of the upper-left corner of this section on the image. Integration Designer Image Group Format Specification 11 . 5.

proportional to the value of an integer variable. the length of the bar is the only thing that changes with the variable.png 5.png 12 Integration Designer Image Group Format Specification .png file contains two sections: the top half of the image is the empty background.png slider_parts^#HIDE. This sample contains no marker.5.3 Example 1: Bar graph This example creates a bar graph where a portion of the graph is filled in.0" encoding="utf-8" ?> <group> <graph sample="slider_sample^#HIDE.png gauge_parts^#HIDE.png" image="gauge_parts^#HIDE. The slider_parts^#HIDE. and the bottom half is the completely filledin bar. The position of the marker is set by the value of the integer variable attached to the object.0" encoding="utf-8" ?> <group> <graph sample="gauge_sample^#HIDE.png" width="25" height="136" orientation="bottomtotop" startoffset="0" endoffset="0"> <section type="background" x="0" y="0" width="25" height="136" /> <section type="marker" x="25" y="0" width="25" height="45" /> </graph> </group> slider_sample^#HIDE. The bar grows from the left to the right as the variable value increases. The gauge_parts^#HIDE. 1 2 3 4 5 6 7 <?xml version="1.4 Example 2: Slider This example creates a slider where a movable marker travels along a fixed background image.png" image="slider_parts^#HIDE.png" width="130" height="13" orientation="lefttoright" startoffset="0" endoffset="0"> <section type="background" x="0" y="0" width="130" height="13" /> <section type="bar" x="0" y="13" width="130" height="13" /> </graph> </group> gauge_sample^#HIDE.png file contains two sections: the left portion is the background image. and the right portion is the movable marker. 1 2 3 4 5 6 7 <?xml version="1. This graph is set to indicate the minimum value by placing the marker at the bottom of the slider.

but it is permissible to include listimage elements with neither image specified to fill in gaps in the numbering sequence. In this example. that specifies the image that is displayed by Integration Designer.2 listimage Inside the imagelist element is a collection of one or more listimage elements.1 imagelist There should be exactly one imagelist element inside of the group element. as the relationship between the variable value and image is fixed in the . It is also possible to specify an up image without specifying a down image.group file.2 down This optional attribute specifies the image to be displayed if this listimage is selected and the button is active (either by pressing or the Reversed button property).1. This element contains a single attribute. The value of this attribute is a filename that points to an image file in the same directory as the . we insert an empty listimage element (on line 4 of the XML) to take that spot in the list.group file. 6. in any file format that can be loaded by Integration Designer. Each Image List provides a number of graphics. Normally. Image Lists will typically be closely tied to a particular driver.1. 6. with only a single one displayed at a time. The value of this attribute is a filename that points to an image file in the same directory as the . the second when the variable equals 1. Integration Designer Image Group Format Specification 13 .2. in any file format that can be loaded by Integration Designer. The value of this attribute is a filename that points to an image file in the same directory as the . 6.2.group file. This can be a custom-designed image. This list would then be designed for use with a driver that provided a variable that took on only values from 1 to 9. at least the up image would be specified. The first listimage is used when the variable equals 0. we also choose not to provide a custom sample graphic. and so on. Each element specifies an image that is used when the integer variable attached to the Image List object equals the position of this listimage element in the list. 6.1. Note that since there is no “0” card.1 up This optional attribute specifies the image to be displayed if this listimage is selected and the button is not active (either by pressing or the Reversed button property). The listimage element contains two optional attributes. depending on the value of the variable.1. in this case the image will not change when the button is pressed. 6.group file.6 Image Lists Image List objects are used to display integer system variables graphically.1 XML Elements and Attributes 6. instead just showing the Ace when the object is placed in Integration Designer. sample. in any file format that can be loaded by Integration Designer. or just another reference to one of the images referenced in a listimage element.2 Example This example uses images of a deck of playing cards to display the numbers 1-9. up and down.

png" /> <listimage up="Seven^#HIDE. so this particular image list would provide no feedback when touched.png"> <listimage /> <listimage up="Ace^#HIDE.png" /> <listimage up="Five^#HIDE.0" encoding="utf-8" ?> <group> <imagelist sample="Ace^#HIDE.png Seven^#HIDE.png Five^#HIDE.png" /> <listimage up="Two^#HIDE.png" /> <listimage up="Four^#HIDE.png 14 Integration Designer Image Group Format Specification .png" /> <listimage up="Nine^#HIDE.png" /> </imagelist> </group> Ace^#HIDE.png" /> <listimage up="Six^#HIDE.png Three^#HIDE.png" /> <listimage up="Three^#HIDE.None of the graphics specify a down attribute.png" /> <listimage up="Eight^#HIDE. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 <?xml version="1.png Two^#HIDE.png Eight^#HIDE.png Nine^#HIDE.png Six^#HIDE.png Four^#HIDE.

Integration Designer Image Group Format Specification 15 . Toggle Buttons avoid this problem by not overloading the meaning of the up and down states to indicate both the state of the variable and the current pressed status of the button.7 Toggle Buttons Toggle Button objects are used to display the state of a boolean system variable. because most variables that change as the result of a button press do not so instantaneously. It is also possible to specify an up image without specifying a down image.1 togglebutton There should be exactly one togglebutton element inside of the group element. However. but require some feedback from a device before changing.2. The implementation of Toggle Buttons is similar to Image Lists. The first element specifies an image that is used when the boolean variable attached to the Toggle Button object is false.group file.group file. in any file format that can be loaded by Integration Designer.1. and a separate set for when the variable is true. 7. 7. A similar effect can be achieved by setting the “Reversed” system variable of a button to a boolean and letting it toggle between up and down. The value of this attribute is a filename that points to an image file in the same directory as the . an up and down state for display when the attached variable is false. this does not provide the ability to have a separate highlighted state when pressing the button and so will usually result in an unattractive flashing from the Down state as the button is pressed. The value of this attribute is a filename that points to an image file in the same directory as the . then the Up state when the button is released. sample. 7.2 listimage Inside the togglebutton element is a collection of two listimage elements. in this case the image will not change when the button is pressed. The toggle button consists of four images. the first one for the false condition and the second one for the true condition. The value of this attribute is a filename that points to an image file in the same directory as the . except that only two listimage elements are provided.2.2 down This optional attribute specifies the image to be displayed if this listimage is selected and the button is active (either by pressing or the Reversed button property). and the second element is used when the variable is true. in any file format that can be loaded by Integration Designer.1. in any file format that can be loaded by Integration Designer.1.1 XML Elements and Attributes 7. then the Down state again when the variable changes. or just another reference to one of the images referenced in a listimage element.1.group file.1 up This optional attribute specifies the image to be displayed if this listimage is selected and the button is not active (either by pressing or the Reversed button property). that specifies the image that is displayed by Integration Designer. This element contains a single attribute. This can be a custom-designed image. 7.

png On Up^#HIDE.2 Example This example creates a button that looks like a slide switch that can be switched between the On and Off states. The actual change from On to Off only happens when a driver reports back via a boolean system variable that the command triggered by pressing the button has been carried out.png 16 Integration Designer Image Group Format Specification . 1 2 3 4 5 6 7 <?xml version="1.0" encoding="utf-8" ?> <group> <togglebutton sample="Off Up^#HIDE.png" /> </togglebutton> </group> Off Up^#HIDE.png Off Down^#HIDE.png On Down^#HIDE.png" down="On Down^#HIDE.png" /> <listimage up="On Up^#HIDE.png" down="Off Down^#HIDE.7.png"> <listimage up="Off Up^#HIDE.

Item Lists are similar to the existing one-way scrolling list functionality. which the control drivers provide in special list variables. This image is retained for display purposes in Integration Designer when the object is dragged into a system file. in any file format that can be loaded by Integration Designer. A typical example of this is artist / album / song lists from music server drivers. corners.1.3 rowheight This mandatory attribute sets the height of an individual row in the item list. only a few of which are typically visible at a time.1. This object will typically be layered on top of a static background graphic that provides titles. 8.1. describes the position of the individual components.1.1 sample This mandatory attribute references the image that will be shown in the bitmap library browser in Integration Designer. Integration Designer Image Group Format Specification 17 . and the various components are placed on that one image. but have more flexibility in their display since the three states that each item can take on can be provided as a graphic in the Item List element.1.1 XML Elements and Attributes 8. in any file format that can be loaded by Integration Designer. described below.group file.4 usehighlight This optional attribute sets the default value of the “Use Highlighting” option in Integration Designer. The value of this attribute is a filename that points to an image file in the same directory as the . but is not used for anything on the device itself. The display devices manage scrolling through the list to allow the user to select any item. It contains the following attributes: 8.1. although lists can be used to present any type of data. It is a single image file. It can be changed by the user in the Item List property page.group file. The item list object only specifies the graphics for a single list item.1. using either the touchscreen or the built-in scroll controls available on some models.1. in pixels.2 image This mandatory attribute references an image which contains the individual components that make up the item list object. 8.1 itemlist There should be exactly one itemlist element inside of the group element. and is repeated vertically for each visible item in the list. 8. and borders. A list consists of a large number of text strings. The section element. This image is should be a representative sample of the appearance of the item list in actual use.1. 8.8 Item Lists Item Lists are used to display lists of information. The value of this attribute is a filename that points to an image file in the same directory as the .

8 marginright This optional attribute specifies the number of pixels that the text is indented from the right edge of the section graphic.1. below.2.1. • selected Specifies the appearance of list items that are currently highlighted by the highlight bar (used for devices that have a non-touchscreen scroll control. Each type can only be specified once for any individual Item List object.1.8. or activated by using the Select Item action. This section is not used if the “Use Highlight” option is disabled for the list. 8.5 height This mandatory attribute specifies the height of this section on the image. 18 Integration Designer Image Group Format Specification .2. it defaults to 0. If not specified.1. such as the T2-C and T3-V).2. 8.2 x This mandatory attribute specifies the x coordinate of the upper-left corner of this section on the image. it defaults to 0.1. • pressed Specifies the appearance of list items that have been touched on the touchscreen.1. it defaults to 0. If not specified. 8.1.4 width This mandatory attribute specifies the width of this section on the image.2 section Inside the itemlist element are one or more section elements that describe which portion of the image referenced by the itemlist element’s image attribute makes up each part of the item list object.1. 8.1 type The mandatory type attribute can have one of the following values.1.7 margintop This optional attribute specifies the number of pixels that the text is indented from the top edge of the section graphic.2. • normal Specifies the appearance of list items that are not highlighted and not pressed.2. 8. If not specified.2.2. 8. 8.6 marginleft This optional attribute specifies the number of pixels that the text is indented from the left edge of the section graphic. The possible section types are described in the type attribute.3 y This mandatory attribute specifies the y coordinate of the upper-left corner of this section on the image.2. 8.

Also note that it does not distinguish between “selected” and “pressed” states.png" image="qvga_list^#HIDE.png Integration Designer Image Group Format Specification 19 .0" encoding="utf-8" ?> <group> <itemlist sample="qvga_list^#HIDE. so the width and height of that portion are set to 0.8. so both are set to the same image. 8. If not specified.9 marginbottom This optional attribute specifies the number of pixels that the text is indented from the bottom edge of the section graphic. Note that this list has no special “normal” state.2 Example This example is for a quarter-VGA sized scrolling list. 1 2 3 4 5 6 7 8 <?xml version="1.png" usehighlight="true" rowheight="25"> <section type="normal" x="0" y="0" width="0" height="0" marginleft="5" marginright="5"/> <section type="selected" x="0" y="0" width="190" height="24" marginleft="5" marginright="5"/> <section type="pressed" x="0" y="0" width="190" height="24" marginleft="5" marginright="5"/> </itemlist> </group> qvga_list^#HIDE. it defaults to 0.2.1.

Sign up to vote on this title
UsefulNot useful