I’ve been trying to allow a tabpanel to grow vertically, and having the enclosed elements move. The growing of the tabpanel works with anchoring, but the enclosing elements won’t move.
My form design, form top to bottom, looks like this:
Label for tabpanel 1
Tabpanel 1 (anchor set to top and bottom; vertical grow works)
Label for tabpanel 2 (anchor set to top; printSliding set to move vertically)
Tabpanel 2 (anchor set to top; printSliding set to move vertically)
Tabpanel 1 grows vertically like I wanted to, but the second label and tabpanel won’t move downwards when tabpanel 1 grows. I’ve tried some different things, but shouldn’t the above setup work? Or, am I doing someting wrong?
In the mean time I also tried a different approach as a test. For the location and sizes of the elements I used a method. This all works OK, but the problem with this approach is that the elements are placed and sized correctly, but when the elements grow beyond the body height it won’t show a scrollbar (all the ‘overflow’ is hidden). So my additional/second question would be if there is a way to resize the body height dynamically?
What I’m basically trying to achieve is a form with multiple tabpanels which can grow according to its content.
Kaptan:
What I’m basically trying to achieve is a form with multiple tabpanels which can grow according to its content.
If you’re using version 4.1.x you might consider using the solutionModel to dynamically create this form.
Using the solutionModel gives you the ability to bind a dataset to a form instead of a foundset.
This way you could first query all the information from your different tabpanels and join this into one dataset.
Your form can then be a listview which just shows repeatingly the body according to the number of records…
The links below will give you more info on the topic of Solutionmodel
I was considering the solution model approach too. But, in my case every record would have it’s own contents in the tabpanel. In other words when browsing through the records, the sizes of the tabpanels can/will change. Wouldn’t the solution model approach be too slow / inefficient when applying on every single record change?
Kaptan:
Wouldn’t the solution model approach be too slow / inefficient when applying on every single record change?
The solutionModel is very fast. I’d say you won’t even notice a form being created.
We use a combination of existing forms with the solutionModel to create customized table headers in tableview.
We do this at startup for approx. 650 forms(!) this whole for…loop which contains more code than the actual creation of the headers, takes about 850mS…
A while ago Scott Buttler actually did an online demo where he simulated a tableview by creating a form on a tabpanel containing 1 record for each record he needed. In this case the actual recordlayout could be different for each record depending of the type of the record…
I’d suggest you give it a chance and I think you’ll be surprised!