Stack Height & Menu Buttons

[Martin Baxter]

>Richard Gaskinwrote :
>>Martin Baxter wrote:
>
>> Errrr, Correction to my last post:
>> What I should have written was:
>>
>> As you can see, between startup and preopenstack, 21 pixels have been added
>> to the card height, and the stack's scroll set to 21. Then, between
>> preopenstack and openstack, 21 pixels have been taken off both the height
>> of the stack and the height of the card.
>>
>> (perhaps I'm secretly dirnking behind my own back ;-)
>
>Is a menu group installed in that stack?

Yes that's right Richard, I'm investigating what is going on with menu
groups and stack heights in mac. There's an often reported problem of 21
pixels too many being chopped off the bottom of a stack that uses this
feature. It's specific to stacks that have menu groups that are set to
display in the menubar on MacOS rather than in the window.

I know I can set the height to what I want in the openstack handler, but
this workaround is so ugly IMO that I'm not inclined to accept it without a
fight.

What I want to find out is either
1) A workaround that I find more acceptable.
2) an understanding of how to avoid this happening at all (it is inconsistent)

Having looked at what is done internally to stack and card heights when my
mac standalone starts up, (and also the source stack in the IDE when it
opens) I can see that if I try to mess with the stack height at any point
before openstack, I'm likely to run into trouble. That at least is clear.

I have a "working suspicion" (aka theory) that sometimes stacks are badly
resized when closed and saved from a dialog prompt, but have yet to get any
certain evidence of this happening. This is what I plan to investigate next.

Of course any further light anyone can shed on  this will be greatly
appreciated as I'd much rather be developing my application than running
diagnostic tests. ;-)

regards

Martin Baxter