C / C++ / MFC

Re: modeless dialog in the client area of MDI-application

20-Mar-07 3:22

Hi everybody,

I try to create a modeless dialog in the client area of a MDI application. It should display some data form the app class (not the document). When I create the dialog:

pmyDlg = new CmyDialog;
pmyDlg->Create(IDD_DIALOG_mydlg)
pmyDlg->ShowWindow(SW_SHOW)

it always appear on top of the application, not in the client area of the child frame. I tried things like pmyDlg->Create(IDD_DIALOG_mydlg, theApp.m_pMainWnd) to set a parent for this dialog but it was alway dragable over the whole desktop and was not restricted to the client area.

Can someone send me a hint?

Many thanks.

Cheers,
Frank.

toxcct20-Mar-07 3:29

toxcct

20-Mar-07 3:29

did you have a look at this[^] ?

[VisualCalc][Binary Guide][CommDialogs] | [Forums Guidelines]

Re: modeless dialog in the client area of MDI-application

Franken20-Mar-07 3:53

Re: modeless dialog in the client area of MDI-application

20-Mar-07 3:53

yes, but it doesn't help me because Nishant Sivakumar suggest to use the desktop window as a parent for the modeless dialog. When I do this, the modeless dialog is even more independent of my application.
What I want is a modeless dialog, which behaves like a MDIView but without the overhead of the document. It should be moveable only inside the client area of the application and not on the whole desktop.

Arman S.20-Mar-07 4:16

Arman S.

20-Mar-07 4:16

Subclass your childview[of MDI] and create a child[WS_CHILD] dialog on it.

--
======
Arman

Re: modeless dialog in the client area of MDI-application

Maximilien20-Mar-07 4:51

Maximilien

20-Mar-07 4:51

Franken wrote:
What I want is a modeless dialog, which behaves like a MDIView but without the overhead of the document.

yuck.

Franken wrote:
It should be moveable only inside the client area of the application and not on the whole desktop.

double yuck.

but I'm a good sport.

Can't you create the modeless dialog with the MainFrame as a WS_CHILD of the main frame ? or something similar ?

I think I remember that you can set of the dialog style to do this.

Maximilien Lincourt
Your Head A Splode - Strong Bad

Re: modeless dialog in the client area of MDI-application

David Crow20-Mar-07 5:15

David Crow

20-Mar-07 5:15

Maximilien wrote:
...the MainFrame as a WS_CHILD of the main frame ?

"Approved Workmen Are Not Ashamed" - 2 Timothy 2:15

"Judge not by the eye but by the heart." - Native American Proverb

Re: modeless dialog in the client area of MDI-application

Maximilien20-Mar-07 9:10

Maximilien

20-Mar-07 9:10

ok, that was bad! D'Oh! | :doh:

Maximilien Lincourt
Your Head A Splode - Strong Bad

Re: modeless dialog in the client area of MDI-application

Franken20-Mar-07 5:27

Re: modeless dialog in the client area of MDI-application

20-Mar-07 5:27

I also thought that it should be possible to set WS_CHILD style but haven't found a way to do this.

Mark Salsbery20-Mar-07 9:20

Mark Salsbery

20-Mar-07 9:20

Do you want the MDIFrame window to be the parent or do you want to place the dialog in a
MDIChild frame?

Either way, the dialog needs to be a child and you need to specify the parent in the Create()
call.

You can set the child style in the resource editor, properties, style.

Mark

"Great job, team. Head back to base for debriefing and cocktails."
(Spottswoode "Team America")

Re: modeless dialog in the client area of MDI-application

Franken20-Mar-07 15:13

Re: modeless dialog in the client area of MDI-application

20-Mar-07 15:13

I set the style to child in the dialog editor properties and did the following during the creation of the dialog:

CMainFrame* pFrame = (CMainFrame*)GetMainWnd();
CChildFrame* pChild = (CChildFrame*)pFrame->GetActiveFrame();

CmyDlg* pDlg = new CmyDlg;
pDlg->Create(IDD_DIALOG_myDlg, pChild->GetParent());
pDlg->ShowWindow(SW_SHOW);

This is almost what I wanted but it shows some weird behaviour. When a region of the dialog is covered by another child window this region shows still the part of the child window even if I drag the dialog to another place. It only restores the correct dialog, when I resize the dialog. Is there somewhere a flag like redraw or something?

Many thanks Smile | :)

,
Frank.

Mark Salsbery20-Mar-07 16:15

Mark Salsbery

20-Mar-07 16:15

hmm I'm not sure if there's different invalidation with MDI windows (which differ from other
windows because they're controlled by an "MDICLIENT" class window).

I have a feeling it's due to activation issues. Mixing a non-MDI child window in a MDI client
window isn't necessarily going to work properly.

I still think it's much easier to make the dialog a client window of a CMDIChildWnd frame. There
shouldn't be any issues then.

Mark

"Great job, team. Head back to base for debriefing and cocktails."
(Spottswoode "Team America")

Re: modeless dialog in the client area of MDI-application

Mark Salsbery20-Mar-07 16:20

Mark Salsbery

20-Mar-07 16:20

Here's some more info: Using the Multiple Document Interface[^]

As you can see in the Window Procedure sections, the MDI windows use different default window
procs so they can/will behave differently than normal parent/child windows.

Mark

"Great job, team. Head back to base for debriefing and cocktails."
(Spottswoode "Team America")

Re: modeless dialog in the client area of MDI-application

David Crow20-Mar-07 10:03

David Crow

20-Mar-07 10:03

You could do something like:

BOOL CModelessDlg::OnInitDialog() 
{
    CDialog::OnInitDialog();
	
    CRect rc;
    GetWindowRect(rc);
    m_lWidth = rc.Width();
    m_lHeight = rc.Height();
 
    AfxGetMainWnd()->GetWindowRect(m_rcParent);
    
    return TRUE;
}
 
void CModelessDlg::OnMoving(UINT fwSide, LPRECT pRect) 
{
    CDialog::OnMoving(fwSide, pRect);
	
    // keep the child's left edge inside the parent's right edge
    pRect->left = min(pRect->left, m_rcParent.right - m_lWidth);
    // keep the child's left edge inside the parent's left edge
    pRect->left = max(pRect->left, m_rcParent.left);
 
    // keep the child's top edge inside the parent's bottom edge
    pRect->top  = min(pRect->top, m_rcParent.bottom - m_lHeight);
    // keep the child's top edge inside the parent's top edge
    pRect->top  = max(pRect->top, m_rcParent.top);
 
    // keep the child's right edge inside the parent's right edge
    pRect->right = min(pRect->right, m_rcParent.right);
    // keep the child's right edge inside the parent's left edge
    pRect->right = max(pRect->right, m_rcParent.left + m_lWidth);
    
    // keep the child's bottom edge inside the parent's bottom edge
    pRect->bottom = min(pRect->bottom, m_rcParent.bottom);
    // keep the child's bottom edge inside the parent's top edge
    pRect->bottom = max(pRect->bottom, m_rcParent.top + m_lHeight);
}

It works regardless of whether WS_POPUP or WS_CHILD is used. A parent can be specified or not.

"Approved Workmen Are Not Ashamed" - 2 Timothy 2:15

"Judge not by the eye but by the heart." - Native American Proverb

Display Problem [modified]

baerten20-Mar-07 1:48

baerten

20-Mar-07 1:48

Hi,

after playing with some LockWindowUpdate / UnlockWindowUpdate and SetRedraw(FALSE) / SetRedraw()

i have a problem with a view, a grid on this view disappears after drawing.
I removed all LockWindowUpdates,Unlock,SetRedraws and the problem is still there.

I added a this->RedrawWindow(); at the end of the initialisation but this line
erases the hole view,the grid and all other components ( it will be redrawn if the MainForm will be minimized/restored)
It seems as the Invalidations are working inverted Unsure | :~

big thanks in advance

-- modified at 7:55 Tuesday 20th March, 2007

I removed the line where i add the row to the grid and all is ok.
I re-insert the line and the Grid becomes invisible(not drawn)

But i have nothing changed at the grid, at the moment i have so strange problems Confused | :confused:

The same with a class which i allocate in a thread and delete at the end of the function.
If i set 0 to a variable, the debugheap is corrupted at the destruction of the element.
if i dont set a value to the variable, i don't get an error...

Re: Display Problem

baerten20-Mar-07 3:04

baerten

20-Mar-07 3:04

I resolved the problem partially.

I put a Grid->RedrawWindow(NULL, NULL, RDW_INVALIDATE | RDW_UPDATENOW | RDW_ERASE | RDW_FRAME);
into the EraseBackground Handler.

But it's not the reason of the problem.

If i put the view directly into a frame( not into a TabWnd of another view ) it works also without errors.

Multiple CDC::SelectObject()

PatrykDabrowski20-Mar-07 1:34

20-Mar-07 1:34

Hello,

Is it safe to use:

CDC memDC;
memDC.CreateCompatibleDC(pDC);
CBitmap *m_pOld = memDC.SelectObject(&some_bitmap1);

memDC.SelectObject(&some_bitmap2);

memDC.SelectObject(&some_bitmap3);

memDC.SelectObject(&some_bitmap4);

....

memDC.SelectObject(m_pOld);
memDC.DeleteDC;

or I should use SelectObject(m_pOld)/DeleteDC() after each SelectObject(&some_bitmapX)??

CPallini20-Mar-07 1:39

CPallini

20-Mar-07 1:39

PatrykDabrowski wrote:
Is it safe to use:[...]

Yes.

PatrykDabrowski wrote:
or I should use SelectObject(m_pOld)/DeleteDC() after each SelectObject(&some_bitmapX)??

No.

If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.

PatrykDabrowski20-Mar-07 1:46

20-Mar-07 1:46

Thanks

pri_skit20-Mar-07 1:54

pri_skit

20-Mar-07 1:54

No it is not safe to use.It will cause memory leak in your application.
I think,II Option is better one.Use SelectObject(m_pOld)/DeleteDC() after each SelectObject(&some_bitmapX)??

priyank

PatrykDabrowski20-Mar-07 2:06

20-Mar-07 2:06

I have already tried both versions. None of them reports memory leaks in VS2003 in Debug mode. But maybe those resources are not monitored by VS... That's why I'm askng Smile | :)

Thanks!

Parthi_Appu20-Mar-07 2:24

Parthi_Appu

20-Mar-07 2:24

pri_skit wrote:
No it is not safe to use

Its safe.. its nothing to do with leaks (if we delete the selected objects)
or simply we can do like this,

CDC dc;//assign value
dc.SaveDC();
/*
 * Do select object,
 * or what ever you want.
 */
dc.RestoreDC( -1 );

No need to worry about the old objects..

Do your Duty and Don't expect the Result

PatrykDabrowski20-Mar-07 2:39