Hi there!
To bring closure to this thread... :)
I managed to overcome all my layouting issues with a little direction
from Rene, who saved me from misunderstanding what's to be done with
GetHeightForWidth(). I also did SetExplicitMaxSize() on all those
BStringViews. If anyone wants to take a peek: [1]
On 28 April 2016 at 11:29, Ingo Weinhold <ingo_weinhold@xxxxxx> wrote:
On 04/26/2016 06:18 PM, Humdinger (Redacted sender humdingerb for DMARC)
wrote:
Also, there seems to be something wrong with the BTextView fInfo. With
it added to the BHelpTab view, I can vertically resize the window to
cut off the buttons below and a part of the BTextView:
https://lut.im/loe358An12/3e7wMzpzDTuDceND.png
You have to set the window flag B_AUTO_UPDATE_SIZE_LIMITS for the size
constraints computed by the layout system to be enforced on the window.
There's a catch in your case, though: You have enabled word wrapping on you
BTextView, so the view becomes a height-for-width view, meaning that its
min/max height constraints depend on its actual width (narrower text
requires more height, wider text less height). The layout system itself
supports this concept (via HasHeightForWidth()/GetHeightForWidth()), the app
server, however, does not. Since the view is not embedded in any parent that
eliminates the effects, the property is propagated up to the root view of
the window and due to the missing support in the app server (or even BWindow
API to notify it), only the constraints ignoring the height-for-width
properties will be enforced on the window. Those are laxer, so it will be
possible to resize the windows smaller or greater than it actually needs to
be.
