I still think something is going on here... the static size on the
text area is irrelevant (and in my real property sheets, doesn't even
exist). The actual property sheet is a canvas full of quite a few
controls.
You say that minHeight and minWidth are used with percentage sizes.
That's exactly wh
minHeight and minWidth are usually used in conjunction with
percentage-based height and width. When the content becomes too
small to view, the min values kick in. This isn't a bug. It just
depends on how you set-up your view. If you set the minHeight/Width
of the canvas to an explicit value
Thanks for that info. This sounds like a bug then.
Why would setting the minHeight/Width on a child of a container cause
the scrollbars for that container not to show properly?
The minHeight and minWidth is necessary to prevent the canvas (or
actually I have a whole component) from sizing too sma
It was actualy working. But, you couldn't see the scroll bars
because the canvas had a minHeight and minWidth that placed the
scrollbars out of view. The sample code below is one way the you
can get the desired results. clipContent and scroll policies work
together. If the clipContent prope
Tim,
Thanks for the suggestion. I have tried setting the scrollPolicy to
OFF on all containers except the one I want to scroll, but it is still
making the "propertySheetContainer" big enough to hold the property
sheet instead of respecting the percentage size I set, and creating
the scrollbar. (th
This is something that we are all dealing with. Unfortunatly, you
have to explicitly set the scrollPolicy and clipContent properties
for every container in the displayList; including application and
canvas. It would be nice if you could set a global
verticalScrollPolicy and horizontalScrollPo
6 matches
Mail list logo
