--- In [email protected], "brucexs" <[EMAIL PROTECTED]> wrote:
>
> --- In [email protected], "Sheri" <sherip99@> wrote:
> >
> > I think I've solved it for my purposes. I'll generate my bar once at a
> > given button height, test the height of the closed combo box, and if
> > its not equal to the button height property then regenerate the bar
> > using the height of the closed combo and save that number for future
> > use. It will always compare the height used to the actual (closed)
> > combo height, so if the default font size ever changes, it will
> > auto-adjust. Works for me, hopefully will work for everyone.
> > 
> > Regards,
> > Sheri
> >
> 
> 
> Just to summarize my understanding of the situation:
> 1.  PowerPro always sets the size of the expanded combo box to 250 
> pixels.  The system may use less if there are not enough entries to 
> fill the droppped down list of that height.

25+206 is not 250. I can't account for the difference.

> 
> 2. PowerPro has no control over the height of the closed combo
> box. The system sets it based on the font. In particular, the
> button height does not effect this directly AFAIK.


The height of the closed combo box does not vary with the button or
bar settings (other than font settings). Font settings also affect how
many entries will fit in the 206 pixel window.
> 
> 3. I cannot explain the stange effects of your reports. The only
> other things that the system may be taking into account is the
> height of the overall tool bar that the combox box is embedded
> in. This is set based on the bar properties button height (or the
> individual button height if the bar properties height is zero).

I don't believe that to be the case. Lets say I make a bar with
multiple rows. On one row, I put a combo box button with a button
height of 25. Next to it, I put a normal button with the height of 80.
PowerPro generates empty space under the 25 height combo box. But the
drop list window is not getting forced into being contained in that
area. Its still 206. If I raise the font size so that it needs more
than 25 (and leave it in the button set at 25), the entire closed
combo is visible (or if open, the edit or selection part of it); part
of it fills into the generated area. And the drop window at 206 pixels
is still operable, it opens below the upper combo portion and extends
over that row's extension and other rows of buttons beneath it on the bar.

I think somehow what you're doing is setting the overall combo box
height to the button height, if that is taller than the (closed) combo
box. Otherwise its this figure that is at least close to 250. Maybe
206+25 is 250-25 + border pixels. (scratching head?)

In any event, by keeping the height of the button (which has *control
combobox) consistent with the height of the combobox, and then putting
a 1 pixel button next to the combobox button that is as tall as you
really wanted the combo button, you can make it operable.

And if you really wanted the dropdown contained inside the button
space, you can put the combo box into a button that is 100-200 pixels
tall. That makes it look kind of like "simple" style combo when its open.

Regards,
Sheri

Reply via email to