Hello, I do not want to use an MDI app to create new documents of the same kind, like in text processors. Instead I want to be able to open different child windows from the menu. The menu handling is clear. When I go and create a new form with controls in the resources/dialog editor, how can I connect them to what I see in the client area of the child ? The classic kind of business software, you know. A user can open a customer window, then a payment window, a child for envoices, for banking, statics and so on. Normal dialog windows do not fill the client area, they are on top of all. That is not what I am going for. Thank You.
Hello. I got it now. To occupy an SDI/MDI with a formview resource template there is one detail in the project assistant. At the last page one can fill in from what the view derives. The preset is CView, but you must change it to CFormView. That was all. Well, I would have liked to make it an existing project, but this is ok, too. Thank You.
In my MFC application, I am doing a custom drawing in my dialog class OnPaint(). I have also created a few controls in dialog template. I have also resized and repositioned some of the controls in the dialog code. When I run my application, the controls are flickering.
Please suggest me how to avoid this?
CDC *pDC = GetDC(); //Get DC for Dialog's Client Area
pDCTmp->CreateCompatibleDC(pDC); //Create Compatible DC(pDCTmp) for Dialog's Client Area(pDC)
//pDCTmp is a member Variable
pBgBitmap->CreateCompatibleBitmap (pDC, 800, 640 ); //Create Compatible Bitmap(pBgBitmap) for Dialog's Client Area(pDC)
CPaintDC dc(this); // device context for painting
// TODO: Add your message handler code here
rect = rScreen; //rScreen is Client rect
pDCTmp->FillRect(rect,&CBrush(RGB(152, 185, 192))); //pDCTmp member variable is used to draw
//Custom drawings using the pDCTmp
A seperate thread function created already which calls a function UpdateAllViews() as shown below every half a second which in turn calls Invalidate the CFP Dialog. This is done to continuously update some real time numerical values on the dialog. When I remove this line
then there is no flickering on the dialog. But the values are not updated. How to avoid this flickering without affecting the value updation.
I'm a little confused by some of your code but generally I think you will
have to override WM_ERASEBKGND so that the background is not erased by the
default processing. Do not call the base class; just return TRUE.
1. Do you have to call Invalidate() from a thread? Could you use a timer in the dialog
and only update what is needed instead of invalidating the whole dialog?
2. Are your dialog controls embedded in a TabControl/TabPage? If so you will have to
create a custom TabControl and TabPage to override the OnEraseBackground() in those and
paint the background in a temp dc as well.
3. I'm not sure about this, but you may have to set the dialog style WS_CLIBCHILDREN to
include them in the dialogs clip region. Look at definition in msdn.
That means it doesn't paint the background before it sends you an WM_PAINT
If you want/need to transparent overlay the bitmap you have to use a transparent colour to stop flashing
CPaintDC dc(this); // device context for painting
// transfer the bitmap into paint DC using a transparent color
10, 10, bmp.bmWidth, bmp.bmHeight, // destination coordinates and sizes
&pDCTmp, // source DC .. your DC with bitmap
0, 0, bmp.bmWidth, bmp.bmHeight, // source coordinates and sizes
RGB(255, 0, 0)); // transparent color
I'm generating dialog templates programmatically for a win32 project. A thing I often want to do is size the dialog box such that the distance between the left edge of the client region and the left edge of the leftmost control is the same as that between the right edge of the rightmost control and the right edge of the client region. Since the size of the dialog box as specified in the template, I believe, includes the non-client area, the only way I know of to do this is to use AdjustWindowRect on a RECT representing the desired client region. Since this requires the handle of the window being adjusted, I can't do it until after the dialog has been created. So I was wondering...if I can't ensure equal margins until runtime, how is it possible that one can use the GUI editor Visual Studio provides to create dialogs with equal margins ahead of time? I want to be able to do that too.
You can select a set of controls in the editor and then use the toolbar tool that centres the group in the dialog. There are tools to centre horizontally or vertically, make equidistant, align together etc.
Resizing at runtime is what I'm currently doing, and it's an acceptable solution, but if possible I would like to specify the size of the dialog in the template, which is generated before runtime, such that it's correct relative to the controls it contains to begin with, without need of resizing. The fact that the dialog editor can do this suggests that it is indeed possible somehow.
I did something like this a long time ago where I defined a dialog within a code module without the
ui editor and I think you will have to implement the use of DLGTEMPLATE which is used to define the dialog and all of the associated controls.
Take a look at InitModalIndirect() in the Mfc library dlgcore.cpp and I believe
there was some needed functions in occmgr.cpp that will help to some extent.
If you haven't used this structure before, it will required a bit of work.
Oh yes, I'm still on V2005 so if you have the latest visual studio there may be some changes.
Hope this is what you are looking for.
A blank empty dialog template centred in it's parent at runtime and done the way speedbump is suggesting is coded below. It is pretty straight forward you just need to allocate global memory block as the template and you can fill the controls in at initialization
int DialogFromTemplate (HWND parent, int DialogWth, int DialogHt, char* DlgTitle, DLGPROC handler)
int nchar, ret;
int x, y;
GetClientRect(parent, &r); // Get parent client area
x = ((r.right+r.left)/2); // Calc x client centre position
y = ((r.bottom+r.top)/2); // Calc y client centre position
/* from the client centre the dialog left is half width and top half height less */
x -= DialogWth/2;
y -= DialogHt/2;
/* template size and position are in multiples of 2 .. yeah its weird */
x /= 2; // X client left position in template units
y /= 2; // Y client top position in template units
hgbl = GlobalAlloc(GMEM_ZEROINIT, 1024); // Allocate memory
if (!hgbl) return -1; // If allocate fail exit
lpdt = (LPDLGTEMPLATE)GlobalLock(hgbl); // Lock the allocated memory
lpdt->style = WS_POPUP | WS_CAPTION | WS_SYSMENU; // Window style
lpdt->cdit = 0; // Number of controls
lpdt->x = x; // X position
lpdt->y = y; // Y psoition
lpdt->cx = DialogWth/2; // Window width (template units)
lpdt->cy = DialogHt/2; // Window height (template units)
lpw = (LPWORD)(lpdt + 1); // Set pointer address
*lpw++ = 0; // No menu
*lpw++ = 0; // Predefined dialog box class (by default)
lpwsz = (LPWSTR)lpw; // Typecast pointer
nchar = 1 + MultiByteToWideChar(CP_ACP, 0, DlgTitle,
-1, lpwsz, 50); // Title of dialog
lpw += nchar; // Increment by size of name
*lpw++ = 0; // No creation data
GlobalUnlock(hgbl); // Release lock on the memory block
ret = (int)DialogBoxIndirectParam(GetModuleHandle(0),
(LPDLGTEMPLATE)hgbl, parent, Handler, 0); // Create the dialog from template
GlobalFree(hgbl); // Free the allocated memory
return ret; // Return result
Incorrect look at WM_INITDIALOG the message exists to do it. You simply move and resize the child windows before they become visible that is the whole point for the message to exist (read the message description). Everything is created but nothing has been drawn at that point. WM_INITDIALOG message - Windows applications | Microsoft Docs[^]
In vino veritas
modified 22-Feb-19 11:45am.
Last Visit: 31-Dec-99 19:00 Last Update: 21-Jan-21 11:21