Hi, The new custom listbox control has some minor problems. 1. I'm not sure when a standard listbox is converted into a custom listbox - it seems to be arbitrary (or based on some hidden criteria). With some tools, the list boxes are replaced at run time, with others - not at all. Is there any way to turn this thing off ? force a parameter in my XML file never to be converted to this custom list box ? 2. The custom listboxes have "wrap-around" mis-feature - when the last item is selected and the user presses "down" or "page-down" - the selection jumps to the first item (and vice versa). Also, On firefox 3 (linux), holding the arrow key (up or down) does not move the selection. one needs to press multiple times. On Chrom 5 (linux) holding the arrow key does work as expected. 3. I assume the list boxes are implemented as HTML, because their content can be selected with the mouse (i.e. marking the text inside the drop-down list box for a 'copy&paste' kind of way). This wreaks havoc on the GUI, the drop-down stays on screen and hides the rest of the controls. One can open two drop-downs the same time, etc. 4. When entering a value in the auto-complete editbox, the drop-down list box shows only relevant items. Clicking outside the list closes the drop-down list. clicking on the blue arrow or on the editbox itself again shows the drop-down list, but with all the items (where I would assume it should show only items matching the existing value in the auto-complete edit-box). 5. Pressing the "ENTER" key while a drop-down list is open activates the next button, instead of selecting the item and closing the list. 6. One issue happens on the local server, which uses an old revision so you might have fixed those in the meantime. For one tool, the list of input datasets is shown with this new custom list box. The items are sorted in ascii order, not in human/version/natural order (see attachments 1 & 2). The order is 1,10,11 etc. instead of 1,2,3,4. The listbox also contains an "unsepcified(?)" item at the bottom (see attachment 3). Thanks to Felix (CC'd) for reporting these issues. -gordon
