I found an issue with TButtonComboBox in EBW2b6, it took a long time to find out that it was not an error in my code and how to reproduce it:

Put a TButtonComboBox an a Form.
Property Items at Design Time should be a TStrings of 17 items, simply numbers 1 to 17.
procedure TForm1.Button1Click(Sender: TObject);
begin
ButtonComboBox1.Text := '17';
end;

Pressing Button1 gives the Text 17 on the ButtonComboBox (= last item)
Now clicking on ComboBox results in Runtime Error List Index 17 out of bounds.
Clicking a second time opens the list and shows 3 extra items named Caption (see attachment)

With ButtonComboBox opened closing the main form leaves the ComboBox on the screen.

Addendum:
You have to press the Buttom first and change the text to the last item, then click the ComboBox.
If the ComboBox is clicked first, the issue can not be found, seems it is an incorrect initialisation.
Is there a workaround, simulating a click on start?

I found out that up to 5 items the issue will not appear,
6 items show one extra item, 7 items lead to 2 extra items.

The persistence of the open ComboBox after closing the main form is independent from the other bug, but I think this behaviour is not intended.

Doc,

<< I found an issue with TButtonComboBox in EBW2b6, it took a long time to
find out that it was not an error in my code and how to reproduce it: >>

Thanks, I'll make sure that these are fixed.

Tim Young
Elevate Software
www.elevatesoft.com

"Tim Young [Elevate Software]" wrote:
Thanks, I'll make sure that these are fixed.
_________________________________________

Thank you.
By the way, the TEditComboBox shows the same behavior of persisting on the screen when opened and the main form is being closed.
The TButtonComboBox is just what I needed for my program, but I wonder why it is called a ComboBox for it behaves like a ListBox and is not editable. Or is the TDialogEditComboBox the addition for editing the ButtonComboBox, I could not see what else it could be for (really need a sort of documentation).

Doc,

<< By the way, the TEditComboBox shows the same behavior of persisting on
the screen when opened and the main form is being closed. >>

Yep, already fixed.

<<The TButtonComboBox is just what I needed for my program, but I wonder why
it is called a ComboBox for it behaves like a ListBox and is not editable.
>>

Basically all of the controls that allow you to pop up another control for
editing/selection are called combo boxes.  It's just a naming scheme.

<< Or is the TDialogEditComboBox the addition for editing the
ButtonComboBox, I could not see what else it could be for (really need a
sort of documentation). >>

No, the TDialogEditComboBox is for showing a dialog for editing the contents
of the TDialogEditComboBox.

This may be a language barrier issue, but yes, I know that we need the
documentation completed.  As I've stated countless times, I'm working on it.
Notices have been plastered all over the preview since we released it that
the documentation isn't complete in the preview, and we made it very clear
before you purchased that this was the case.  If lack of documentation and
the presence of bugs is an issue for you, then you should have waited until
the final release to purchase the product.

Tim Young
Elevate Software
www.elevatesoft.com

I didn't want to criticize you.
I knew exactly what I would get when I purchased your program.
I just waited till EWB2 was out.
I'm just a hobby programmer and my programming work is just for fun.
I think EWB is worth every pence.
I like it very much.
I like doing some sort of beta testing with the preview version for you. I'm quite sure that some of the issues I reported would have made it into the final version if I hadn't found them

Doc,

No problem.  As I said, it may be a language/writing thing.  Sometimes, I
have a hard time telling if you're complaining or just stating a fact.  As
you can understand, it's a little frustrating to read about needing
documentation when I've been working furiously on documentation for a few
weeks.  There's just a lot of interruptions to the work to take care of
everyday support issues, etc, so progress is sometimes slower than I want it
to be.

<< I'm quite sure that some of the issues I reported would have made it into
the final version if I hadn't found them >>

Absolutely, which is why I always make it a point to say thank you when you
report something.

Tim Young
Elevate Software
www.elevatesoft.com