If you select multiple rows in a ListBox, then sort, the selection will not
be preserved properly.
http://www.realsoftware.com/feedback/viewreport.php?reportid=zgzqygiw
I bring this up on the list only because I consider it a dangerous bug. If
you have data (RAM or DB driven) in a ListBox, and you allow a user to
select and Delete said data, the user could inadvertently end up in a
situation where they delete data they did not intend to delete.
This does not appear to affect ListBoxes set to single selection. If I
recall correctly, ListBoxes bound to a database can't sort themselves, so
those would be safe to. Ironically, I have and use a ListBox subclass which
populates itself from a DB specifically so that it is not bound and can sort
by header clicks, but I did that back in the 5.5 days so I don't know if
that has changed in 200x.
I saw this tonight while testing an application and hit the ceiling. It has
been around for a while, but I just never saw it or had a client complain.
But it's one bug I do not like.
Daniel L. Taylor
Taylor Design
Computer Consulting & Software Development
[EMAIL PROTECTED]
www.taylor-design.com
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
