#Xlist records code#

This would permit the databinding functionality of the control to continue as before, while having XListItems in separate OptGroups would have made that a real mess. Luckily, I regained my sanity before I did that, and decided merely to add an OptGroup property to the XListItems. I considered doing the same thing here making XListItems be the children of an OptGroup class, and having an OptGroupCollection class in the XList. In the XTable control, where I added support for, and tags, I decided to add a hierarchy between Table and TableRow, which I called TableRowGroup.

And since both ListBox and DropDownList really should support the tag, combining them saved me time and work.ДЇirst, though, I had to decide how I was going to do this. But when you're as lazy as I am, the prospect of having to modify both controls when it's the same modification just seemed pointless. It isn't actually that big a deal that ListBox and DropDownList are separate controls. As I said, you can find it as OpenList in the source code. That's about all I did to combine the two controls. If it can, it converts to the Type you want, and if it can't it returns Nothing. If TypeOf enumerable1 Is ICollection ThenД¬ollection1 = CType(enumerable1, ICollection)Д«ecause that's essentially what Trењњast does. I checked to see what the differences were between the two, and simply made those differences dependent upon an Enum I created. ListBox inherits from ListControl, and so does DropDownList. This is necessary, because ListItem is not inheritable, and you'll see later on how we need to make some modifications in that class.

#Xlist records code#

Because the difference between ListBox and DropDownList are minor.ДЄs I've done before, I used Lutz Roeder's Reflector to grab the code that makes up the ListBox control. I have to assume that since the last two don't use as the HTML element that gets rendered on the Page, they just decided to do all of them separately. The Microsoft ListControl is used as a basis for ListBox, DropDownList, CheckBoxList and RadioButtonList. To me, it looks like they started to implement it, but never got around to finishing it. Which begs the question of why they bother with an Attributes property in the ListItem class in the first place. You can add Attributes to ListItems, but:

ListBox (and DropDownList) share a bug that Microsoft calls ' by design'.

ListBox (as well as DropDownList) doesn't support the tag, which is part of the element's object model.

ListBox and DropDownList, despite being the same control in almost every way, are separate server controls.

I wanted to encapsulate my solution in a server control, but I figured that as long as I was going to do that, I might as well correct three of the more annoying aspects of Microsoft's ListBox server control: I fixed that in the JavaScript as well.ДЄnd then came the move to ASP.NET. Nothing made the selected item stay within the visible area of the. The first problem that came to light was that if you used your arrow keys to cursor down the list, you could disappear off the bottom of the. So I played around with putting the into a, and after fiddling with the JavaScript for a while, I had a solution. From the time I started playing with HTML, I was annoyed by the lack of a horizontal scrollbar on the element.