Bruce,

I see PB2022 R3 GL came out today... any idea how long it will take to update the PFC?  No rush, just wondering if it will be weeks or months?

~~~Tracy

Hi all, 

Note that of the 4 issues summarized by Bruce:

Issue #1 and #2 are bugs. The engineer told me that they will be fixed in the R3 GA version.

Issue #3 and #4 are actually enhancement requests.  We now studying how to implement them.  

Best regards, Julie

I responded to your post in the PFC Github project, but responding here as well for completeness.  What I responded to there, and also passed onto Appeon was the following:

1. When tabbedview MDI is used and the tabs are maximized, when the frame size is changed the sheets do not resize (they do not receive a resize event). I believe given that they are maximized to fit the frame that they should be automatically resized when the frame is resized.
2. When tabbedview MDI is used and the tabs are not maximized, a resize even is not sent to the window when a sheet is maximized. It is when it’s resized manually or minimized, but not when it’s maximized. I believe this is a bug.
3. When tabbedview MDI is used and the tabs are maximized, the resize event and this.WorkSpaceHeight() both return a value that represents the entire MDI_1 client area. However, the tabbed view control (mditbb_1) is occupying part of that space. In order to determine what is the actual useful window area, the height of mdittb_1 has to be subtracted from the newsize/WorkSpaceHeight when the sheet is maximized.
4. In order to try to adjust the resize behavior of PFC I need to be able to determine dynamically whether tabbedview MDI is in use and whether it has been configured to maximize the sheets. However:
   a. Not only are the TabbedView and MaximizeAllTabbedSheets not setable at runtime, they aren’t readable either. There are no properties reported on the window type to correspond to them.
   b. I could try to determine if TabbedView is in use by trying to determine if mditbb_1 is valid at runtime. However that doesn’t appear as a property I can access from outside of the frame (it’s not a property on the window class). Note that mdi_1 is a property of the window class, so that technique does work for mdi_1, but not for mditbb_1.
   c. What I’ve found does work is looping through the control array of the frame and looking to see if one of the objects has a classname of mditbb_1. However that only tells me that TabbedMDI is in use, there still doesn’t seem to be any way that I can determine whether or not MaximizeAllTabbesSheets is set.

Hi, Tracy -

I believe the problem you are experiencing is due to (1) the way the PFC's window resize service is designed/coded and (2) the way you are using it.

If you examine the code in the resize service object (pfc_n_cst_resize), you'll see that there are two key instance variables:

long	il_parentprevwidth = -1
long	il_parentprevheight = -1

Their initial values of -1 indicate that no actual value has been set. Once the resize service is in active use (i.e., the window is being resized). these var's are updated every time the window's Resize event fires, which is quite frequently as the user drags a window's border. The new/current window width & height are compared against the previous Resize event's width & height to determine the amount of change (the delta's) in each.

Now, if you examine the code in the Resize event of the PFC's "master" ancestor window, pfc_w_master, you'll find the following code at the beginning:

// Notify the resize service that the window size has changed.
If IsValid (inv_resize) and This.windowstate <> minimized! Then
	inv_resize.Event pfc_Resize (sizetype, This.WorkSpaceWidth(), This.WorkSpaceHeight())
End If

Note that if the window is maximized, the resize service does not get notified of the change in the window's size. This is intentional. When you make the window open in a maximized state, the resize service never gets called. Once the window is restored to it's original/design size, then the resize service  can get involved, the instance var's get set, and the window resize service does its magic.

I suggest there are two ways to resolve your issue:

1. Don't open the window in a maximized state (this is the "if it hurts when you do that, DON'T do that" solution). You can use a tip that Chris suggests; Open the window invisible/hidden, then in the pfc_PostOpen event, set the window state to Maximized! and immediately make it visible.
2. Use the of_SetOrigSize(width, height) function of the resize service object as soon as you turn on the service, presumably in the window's pfc_PreOpen event. This function sets values for the two critical instance var's and changes their initial/default "no value has been set" values.

I admit that I have not tried either alternative, as I've never opened a PFC-based window in a maximized state... but I believe either of these alternatives should resolve the unusual behavior you are experiencing.

Best regards, John

For anyone wondering, "previous question": https://community.appeon.com/index.php/qna/q-a/pb2022-tabbed-view-not-showing-horizontal-scroll-bar