Re: Repost: How to suppress unwanted MDI behaviour

From:

"AliR $VC++ MVP$" <AliR@online.nospam>

Newsgroups:

microsoft.public.vc.mfc

Date:

Wed, 04 Apr 2007 15:17:46 GMT

Message-ID:

<ukPQh.5029$u03.4877@newssvr21.news.prodigy.net>

See if this is along the line of what you are trying to do.

http://www.learnstar.com/alir/onemaxview.zip

AliR.

"AliR (VC++ MVP)" <AliR@online.nospam> wrote in message
news:xBOQh.5022$u03.4701@newssvr21.news.prodigy.net...

Is this what you are doing?

BOOL CChildFrame::PreCreateWindow(CREATESTRUCT& cs)
{
cs.style &= ~WS_MAXIMIZEBOX;
// TODO: Modify the Window class or styles here by modifying the
CREATESTRUCT cs
if( !CMDIChildWnd::PreCreateWindow(cs) )
return FALSE;

return TRUE;
}

Because I did this an it worked just fine. The maximize button gets
disabled, and the view still has a caption.

AliR.

"JohnL" <JohnL@discussions.microsoft.com> wrote in message
news:837A3B0A-017F-4AFE-90B9-9AF2188E8EDA@microsoft.com...

Thanks again Tom and Alir,

This is an app that has been evolving since MFC 1.0 and we can't invest
too
much in reworking it. You are correct in the assumption that normally a
modless dialog would be the way to go - except that they can't be
minimized
and do not appear in the Windows menu and do not receive 'OnUpdate'.
The main view is a tactical display (dynamic update) and the user can
select
an object and invoke a form displaying the object's properties - with the
main display still visible beneath it - and the form can be moved if
obscuring an object of interest. There is not just 1 FormView class but
about
55 of them.
Anyhow I now have most of the behaviour we wanted. I had to leave the
maximize box enabled and in the FormFrame handle OnWindowPosChanging and
OnGetMinMaxInfo.

Thanks for your comments - it kept me searching

Regards,
John
--
C++/C# Developer
Part time SBS2003 Admin

"Tom Serface" wrote:

Hi Ali,

The more I thought about this last night the more I think OP is looking
or
the "view" to take up the whole screen in his app, then having the
formview
pop up over it and "not" have the other view's frame change as well. I
think OP will need to use a modeless dialog for this kind of thing (at
least
as a simple answer).

I think the goal is to keep the formview in a window that doesn't have a
lot
of fluff around it and use the scroll view as kind of the main window.

Tom

"AliR (VC++ MVP)" <AliR@online.nospam> wrote in message
news:e%tQh.24317$uo3.22156@newssvr14.news.prodigy.net...

I also fail to see what it should look like when both views are active?
Is
one overlapping the other? Do you want them tiled? Do you want each
to
take up half of the screen?

Have you looked at splitters.

The look like this:
http://www.codeproject.com/splitter/FlatSplitter/FlatSplitter1.gif