I turned on tabbed view on my MDI frame and that all works as expected, until my QA folk pointed out that using the close 'X' on the tab doesn't trigger an event like closing the 'X' on the window. -- So unsaved changes can't be captured when closing the window.
I noticed you should be able to turn off the contextual menu and the close box on the tab with:
mditbb_1.ShowContextMenu = false
mditbb_1.ShowCloseButton = false
The context menu indeed, was not available, however the close 'X' on the tab is still there.
Since I won't be able to intercept the event, or prevent the event from occurring, I won't be able to enable this feature.
This is using PB 2022 R2 build 2819.
--- Yes, I know there's the Close event and CloseQuery event, and yes, we already use these to some extent... However, in parts of our application we're also specifically capturing the system event when the user clicks the "x" close box on the window. This generates a pbm_SystemCommand event where commandtype = 61536. Using the 'X' on the tab apparently doesn't trigger this event, so there's nothing to capture.
. We have two halves of our application: one that uses a modified pfc, and one that does not. The side that does not, uses closequery extensively, and that MDI frame we can turn tabbed view on. On the side that uses the pfc, clicking on the close box of the window triggers our pfc cancel event...
Regardless, this is all pedantic as the main issue isn't that tabbed view doesn't trigger an event, but that you can't turn off the close box on the tab, as the documentation advertises.
Yes, setting the following ... mditbb_1.ShowCloseButton = false does NOT work and should be submitted in a Support Ticket. It does not work in PB 2022 R3 either I am sad to say. :-(
Regards .. Chris