Re: Can I maximize only one view on a document?

[Ken Schreier]

Thanks for the help Allen,


I tried your suggestion and it did exactly as you said - however I had tried to take short cuts in the desciption of my problem and things 'still ain't right'...


I hope you (or anyone) has the patience for me to descibe it in more detail:


The main view (SplitView) of the single doc is implemented as a splitter window that has four panes, and some unique requirements: It has to remain maximized at all times, and I have disabled various standard operations like closing the app, changing to any other app, or otherwise doing anything other than using this program.


The 2nd view (TextView) is a CScrollView derived class that will pop up when things in the program happen, and then just display text (like debug info), but right now I have a menu selection to cause this view to come up. The problem is that the 1st instance of TextView comes up MAXIMIZED even though I override OnInitialUpdate and do a MoveWindow (to 1/4 size) on the parent frame. Then as soon as I do a couple ctrl-tab's to change the focus window, the size changes to the 1/4 size specified in the MoveWindow call - like it remembers that. (Subsequent instances of TextView come up correctly - 1/4 size.)


One problem: When I added your code, the 1st instance comes up correctly - but there is a lot of 'window hashing' - I can visibly see it go from full screen to 1/4 size at least 2 times - really looks bad. How to prevent this is the problem....


Another clue: When I remove SplitView, and make TextView my intial view, it comes up correctly with or with out adding your suggestion.


2nd problem will be the one you identified in your response - after switching windows whatever was maximized doesn't stay maximized...


Well, there is my novel - any help will be greatly appreciated. This is my 1st venture into mfc - the jury is still out~!


[email protected]

[Dave Lorde]

> One problem: When I added your code, the 1st instance comes up correctly -
> but there is a lot of 'window hashing' - I can visibly see it go from full
> screen to 1/4 size at least 2 times - really looks bad. How to prevent this
> is the problem....

Have you tried wrapping the resize calls between LockWindowUpdate / UnlockWindowUpdate (or SetRedraw(FALSE) / SetRedraw(TRUE)) ?

Dave