![]() ![]() That is, I was able to make the TListBox “aware” of the TInterfaceList directly. Under Delphi 6, using a virtual list box, I was able merge my TInterfaceList and the TListbox into one highly usable pseudo object. Then I would need to synchronize any movement and selection in the list box with the TInterfaceList. Under Delphi 5 this required that I step down through the TInterfaceList calling the required interface method at each step to add the strings to the TListBox. Well, with a virtual list box you can.ĭuring the past week I ran into a situation where I had a TInterfaceList and wanted to use the value returned from one of the Interface's functions as the text of the list item. Why should you be forced to duplicate this data over to the TStrings associated with the TListBox. ![]() Sure, you can assign any pointer you want to the object field of a string list but what if you already have a list container (like a Tlist) full of data. Have you ever been frustrated by the limitations of the TStrings' objects property or have had a need to create a custom display string in the list. In all the Delphi 6 “What’s new” articles I’ve read this addition has received no more than a passing mention. One of the new features in Delphi 6 is the addition of styles lbVirtual and lbVirtualOwnerDraw to the standard TListBox. What are the new virtual styles in the TListbox for, and whay are they important? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |