VLF-ONE Vertical Scrolling
Posted: Thu Mar 16, 2017 4:17 am
This is related to this post http://vlforum.lansa.com.au/viewtopic.php?f=3&t=1204 but focused on VLF-ONE.
In short, I am really struggling with getting the correct combination of Row(Content, Proportion, Pixel) and Size (ContentHeight, ContentWidthAndHeight) to get the handler to render correctly. Its kinda frustrating as I am spending more time struggling with LayoutItems then writing the actual code for the command.
If the "nested panels" are all ContentHeightFitWidth what should the Row and Column Units and Size be of parent item to get the command to render and scroll properly?
For example, I have a 3x1 Main Layout for a Command Handler in VLF-ONE.
At (1,1) I have some audit information and is fixed at 30 pixels. At (3,1) I have a save button and is fixed at 30 pixels.
The middle row is what causes me problems, it contains a "container panel" at (2,1) that contains all of my other nested panels.
I put it in a container panel because I swap layouts according to design changes, but the audit and save button is always in the same spot.
The container panel has a 3x4 Layout. All of the panels in the container panel are set to ContentHeightFitToWidth and the container panel itself is set to ContentHeightFitToWidth.
My problem is with the middle row.
If I specify "Content" for the middle row, the last row (save button) goes up to the top and has a height of 10.
If I specify "Proportion", the designer looks ok, but when rendered the last row floats over the container panel.
It seems the only way I can get it to display properly is to use exact pixels.
The "size" of the Main Layout is another variable that I don't understand If I set it to none and and the rows are pixels it seems to do okay. If I set to the ContentHeight any the bottom row (3,1) floats over the container panel. If I set to to ContentWidthAndHeight the whole thing collapses into an 80 pixel column.
Using exact pixels does not seem to be the "LANSA" thing to do. I am trying to figure out what the "best practice" is and it seems like using pixels is the only way to get consistent results. Perhaps that's just how it is and I need to deal with it. That's ok as long as I know.
In short, I am really struggling with getting the correct combination of Row(Content, Proportion, Pixel) and Size (ContentHeight, ContentWidthAndHeight) to get the handler to render correctly. Its kinda frustrating as I am spending more time struggling with LayoutItems then writing the actual code for the command.
If the "nested panels" are all ContentHeightFitWidth what should the Row and Column Units and Size be of parent item to get the command to render and scroll properly?
For example, I have a 3x1 Main Layout for a Command Handler in VLF-ONE.
At (1,1) I have some audit information and is fixed at 30 pixels. At (3,1) I have a save button and is fixed at 30 pixels.
The middle row is what causes me problems, it contains a "container panel" at (2,1) that contains all of my other nested panels.
I put it in a container panel because I swap layouts according to design changes, but the audit and save button is always in the same spot.
The container panel has a 3x4 Layout. All of the panels in the container panel are set to ContentHeightFitToWidth and the container panel itself is set to ContentHeightFitToWidth.
My problem is with the middle row.
If I specify "Content" for the middle row, the last row (save button) goes up to the top and has a height of 10.
- content.png (19.15 KiB) Viewed 6240 times
- proportion.png (20.53 KiB) Viewed 6240 times
- pixels.png (18.96 KiB) Viewed 6240 times
Using exact pixels does not seem to be the "LANSA" thing to do. I am trying to figure out what the "best practice" is and it seems like using pixels is the only way to get consistent results. Perhaps that's just how it is and I need to deal with it. That's ok as long as I know.