You have to position the part of what you want to see of the inside to be at position (0,0) in the parent container. And then you HAVE TO resize the container to the size of the thing you want to see. And the parent container position itself has to be adjusted where you want to see it.
There is no other way than that. But then you WILL see what you want to see and only that. It only does not look good if you let the parent become even larger than it needs to be and show more of the inside then you want to show. In your screenshots the parent container is far too small, you clip the inside, you see less than you want. You neither can expect this to automatically resize nor can you expect this to adapt per row because your parent container is a child of a grid cell. And there is only one real grid row, all the others are painted with the grid recordsource row of data.
So, not only containers are containers in the sense of a box defining position and size of a rectangle also pageframes are, grids are, grid columns are and grid cells are a container, the latter resulting from the width of a grid column and the grid row height.
But how many times do we need to tell you, that you CAN'T let something inside a container stick outside of its borders? That's impossible.
Do you really still need an explanation of why your form looks the way it looks? Your texts are cut off because that's where the right border of a container is. Just because you didn't give color to the container border, that doesn't mean more text can break out and show outside of the container rectangle. right of it.
In comparison to the self-adjusting resizing world of HTML divs and other HTML objects VFP containers don't use any dynamic behavior. Their position and size is as you set it.
If you have a container inside a container inside a grid column inside a grid inside a pageframe inside a form. That doesn't change the size of the innermost container. It only shows its inside structure as far, as that fits from its (0,0) to (width,height) rectangle. Everything not in that rectangle is clipped. The container itself is clipped by the column width, if the container in the cell in the column is wider than the column it neither makes the grid column wider nor does it stick into the next column. Same with the rows bottom line. And the grid containing this is where it is relative to the pageframe position under its tabs, and the pageframe is where it's positioned on the form.
Every container of control acting as a container defines a new (0,0) coordinate for left(top positions of inside objects. That what makes it hard to position something relative to form (0,0) left upper corner position, but it makes it easy to position everything relative to where a container is positioned and if that parent is moved, no position of inner objects has to change, it all follows the container, that's the main idea. Everything moves along, also the right and bottom borders, containers don't resize. Unless you use anchoring, which complicates everything, but only acts towards the next parent level, you don't anchor everything to the form level position, you anchor position and sizes to the borders of a container.
All in all, it's complicated enough, but it's extremely easy to predict and set up in comparison to how HTML divs behave.
Bye, Olaf.
Olaf Doschke Software Engineering
