Hello,
PB 2022 build 1892, NO PFC, using Kevin Ridley's Resize services
1. Resizing of objects inside a window, works fine. Even DW's inside tab's are resized.
2. Now placing a splitbar [ u_st_splitbar from PFC ] in between upper DW and below Tabpage.
3. When I move the splitbar, I want all objects to resize perfectly. Here tabpage gets resized, but not dw control inside the tab.
I want that also to be resized. Any suggestions?
Happiness Always
BKR Sivaprakash
Hi.
This is how we implement this.
We do add userobject as tabpages. Our user object can use resize service (u_tabpg). Usually it's from pfc (but this can also work with Kevin's isolated service). We then set our tab_x.tabpage_x constructor event to register controls it contains as needed.
We don't register controls to the window!
As controls are registered in uo, and resize service knows what to do, they will resize whatever is the reason of user object size change. Even if this happens beacause of splitbar usage.
I attach some sample code to show how we implement it. In my sample there is no splitbar. You can do this check yourself. But it should work. In my pfc based projects it does work.
I included Kevin's resize object in this sample code.
I also have a window (which doesn't inherit from a base window). It has of_set_resize function declared on it (Kevin's version). Normally there should be a base window.
In this window I added a tab control.
I have a user object named uo_custom_tab. I added to it: a) in instance variables: n_resize_service inv_resize, b) resize event with appropriate code, c) of_set_resize to enable the service.
In my tab control I insert a tab page using Insert User Object... I use my uo_custom_tab.
On the window, I put the resize logic for each tabpage to the tab_x.tabpage_x constructor event, as previously mentioned.
The main disadvantage of this logic is that I cannot modify my tabpage appearance directly from the window. But I generally prefer that because my windows are lighter in the IDE, and I can always edit my tabpage from the control.
Of course to use this model the best thing to do is to have:
a) a base window (the one Kevin provided is fine)
b) a base userobject (from this one we can inherit to create our tabpages).
Why I do always prefer working with user objects? That way if I remove a tabpage from a control, the tabpage is still there as a user object! If you want for example to move a tabpage from a tab control to another one, this way you can easy achieve your objective (while copy paste would also work). Another thing is that you can easily do a change that will affect all your tabpages (by modifying an ancestor). Finally you can have userobject functions in tabpages...
Andreas.
Hi BK;
Since you contacted me directly about using the STD Framework last week. I just wanted to point out that the framework supplies you with a user resize event in the case of Tab Pages and CVUOs (Custom Visual User Objects). For example ...
Tabpage:
CVUO:
I solved the "complex problem of resizing over 20 years ago by adding the Resize events that were missing from certain object types. The problem you are trying to address with the PFC_Resize is that you have nested levels of Parent=>Child objects. For example, you can have ...
Window => Tab Control => Tab Page => CVUO => TC => TP ... etc and then at the end your two DataWindow Controls & a Split Bar. The challenge with the PFC_Resize is that you need to register all the "nested" controls starting at the Window level. In the above scenario, that becomes not only a daunting coding exercise but the PFC_Resize execution can become unhinged.
To solve this (as neither PB or the PFC account for this deficiency) - almost 20+ years ago in the STD framework, I added the missing resize events and then configured the potential parent(s) of these controls to pass down their respective resize values. Thus in the above example, the only resize logic you need is on the "oe_resize" event of the Tab Page that owns the two DC's and the split bar (3 objects in total). At this granular level, the resize logic is trivial and all the necessary values are handed to you in the "oe_resize" event.
If you continue on with my design logic, resizing is greatly simplified. In fact since I wrote the initial framework starting in 1993, I have had only 3 people have ask me about something like a PFC_Resize NVUO. Personally with this low level granularity and scrollbars (my persona; favourite) - I usually can't even imagine why you need something like a PFC_Resize. Just my $0.02. Food for thought.
Regards ... Chris
PS: I have no idea why PowerSoft, Sybase or SAP never added the missing resize events to all PB System Class visual objects (controls).
The following is based on screenshots you provided.
I see that the datawindow size in first tab is affected (a little). Is this tab_1.tabpage_1.dw_3 or tab_1.tabpage_2.dw_4? Or you datawindow gets hidden from tabpage?
In pfc I wouldn't register the datawindow to the window's resize service but to the tabpage resize service...
I guess the "isolated" service can be used that way but haven't tried.
Andreas.