--- In [email protected], "brucexs" <[EMAIL PROTECTED]> wrote:
>
> --- In [email protected], "Sheri" <sherip99@> wrote:
> >
> > Hi Bruce,
> >
> > Maybe there is something you can do about this sometime. Below the
> > script is my output, which shows that on my PC, a combo box will be
>
> Sorry, Shery, I remember I played around with this a lot and could
> never get it to perform reliably. Its something in the Windows
> creates combo boxes and sets their size that I don't understand. I'm
> afraid I don't plan to try again.
>
>
> But here is the code I use in case anyone else can spot something.
>
> hei=tbi->button[i].height; //the specified height
> if (strcmpi(szName, "combobox")==0)
> {
> hei=max(hei, 250); // min drop down is 250?
> }
> tbi->button[i].hwndCtrl =
> CreateWindowEx(xopts,pName, "",
> (tbi->button[i].flags&BUTTONBAR_ANYHIDDEN?
> 0:WS_VISIBLE)|WS_CHILD |WS_TABSTOP|opts,
> tbi->button[i].left, tbi->button[i].top,tbi->button
> [i].width,hei ,
> hwndTB, i+1, vhInstance, NULL);
>
> Its some kind of interaction between the bar heidht and the combo
> button and possibly other controls on the bar, I suspect.
>
Hi again Bruce,
I can't comment on the code, but I do find the results consistent for
all the combo boxes on the Code Accelerator bar (which uses a variety
of controls and numerous other buttons, etc.) vs the one button/combo
box in the script that produced the output. Maybe it has more to do
with the default font or something. When I specify a combo box for a
dialog via the dialog plugin, 100 "dialog units" as combo height makes
for a combo box with a drop down window of 206 pixels.
What I would suggest (unless somebody has a better suggestion or its
still more complicated than it sounds) is either to hard code the
combo height or else to separate the combo height from the buttton
height and allow a height number to be entered as part of the *control
combobox spec.
Regards,
Sheri
