***************************************************************************
*
*  McKean Consulting
*  Robin W. McKean
*  1042 Braddock Circle
*  Woodstock GA  30188
*
*  BUG.TXT
*
*  Multi-Purpose List Box Control for Borland C++ 4.0
*
***************************************************************************

1.  When assigning a value to ListIndex, there is no Click or SelChange
event triggered as in a regular list box.  Also the starting value is 0, not
-1.

ANS.  In verions 4.20 and greater, setting ListIndex will generate a SelChange 
event.  Not, that in Multiple-Select list boxes, the starting index is 0, where 
the focus rect is, and not -1, like in a normal list box.


2.  When I SetFocus to a list configured with both grid lines on, the first
line doesn't redraw its line correctly.

ANS.  Make sure that your column lengths take up the entire list box, even if you are
not using the extra space at the end.  MList assumes that you are using the
entire width of the list box.  (Was that that ASSUME word???)

3.  When loading information using TextRegion and ListRegion, ListIndex is
reset to -1 after first assignation.  If multiple regions have to be loaded,
I have to keep the ListIndex property in a temporary variable throughout the
operation and reassign it to ListIndex in order to get back to the same
line.

ANS.  I really bit the bullet on multiple select list boxes.  This has been fixed.

4.  I'm getting GPF faults when sending messages directly to the list box via
SendMessage.

ANS.  I'm unable to duplicate this.  Anyone care to send me an example.

5.  MList always reports ListIndex = 0 when a search is conducted with Multi-
Select is set to true.

ANS.  This is a related Multiple-Select problem.  I appreciate both the input and
your patience.  It has been fixed.

6.  MList seems to have a problem finding things when Sorted is true.

Searches, whether sorted or not, always search from the current item in the direction
specified by FindDirection property.  It will not wrap around.

7.  Click event works differently from the standard list box which comes with VB

I haven't figured out this one.  Microsoft called their main notification event, Click,
which in all other controls responds to mouse events.  Yet, the one in the list box,
responds to all events which change the currently selected item, wheter that is 
ListIndex, a mouse, or a key press.  Humph.  I used the SelChange event to do the
same thing, because is is more indicative of what is happening to the list box.  If
someone asks me to, I will provide a switch to force the Click event to behave like
the SelChange event.

8.  ItemLength returns space in pixels when it is set with twips.

Oops!  I do convert it to Pixels, but I return it NOW in twips.  There is a small
conversion difference, so don't be suprised if you set ItemLength(0) = 1000 and
get back 997.

9.  The more columns I have, the more the clipping region diminished.

When setting the number of columns, MList will evenly divide the current area of the
list box into the number of columns you specify.  If you want to use the horizontal
scroll bar, then you must reset the ItemLength of the desired columns to extend past
the edge of the list box.

10.  Double clicking with the right mouse button acts as if I double clicked the
currently selected item with the left mouse button.

This has been corrected.