LOL nice find!

Oh thanks pal, you da man. I went for the placeholder like solution as it was quicker for me in this case, but next time I run into this (which I'm sure is soon), I'm going to follow the article.

Does anyone know why on like 3 of 40 of the computers my company has, the controls placed on a dialog programmatically via MoveWindow are sized different than if they were just placed in the .RC file with the Resource Editor? I have an image to show what I mean. On the right hand side I have what a normal machine looks like. on the left hand side is a screwed up machine( you'll notice all the top controls which are placed in the resource editor are much larger, where the bottom controls which are placed with MoveWindow function end up in the correct place) http://www.john-moses.com/img/artviewer_bug.jpg[^] So I have a dialog that has several controls on it, most of which don't need to be resized, only 2 of the controls on the dialog need to be resized. All the controls on the dialog that don't need to be resized I just place in the .RC file with the Resource Editor, and don't bother making member variables for. For the 2 controls that need to resizing, I'll place in the Resource Editor, but in the OnSize function I'll call MoveWindow on the 2 control's member functions to resize them. This works just fine on like 98% of the computers are my company, but for like 3 people, for some reason this mix of Resource Editor/MoveWindow placed controls causes some kind of visual bug. Any Ideas what could cause this? I looked at the machines "Desktop Properties -> Display Properties -> Advanced", and all our fonts and sizes are the same. We all do have different processors and video cards, nothing we can do about that. We're all running Windows XP Pro eh?

Not like I think anyone is reading this, but I in case anyone else is, I found the solution, there was a very simple walkthrough: http://www.deez.info/sengelha/2006/06/09/nesting-dialogs-in-mfc/[^]

Hmmm, I'm getting a crash/assert when I try and do it myself in void AFXAPI AfxHookWindowCreate(CWnd* pWnd) on the line: ASSERT(pWnd->m_hWnd == NULL); Any ideas why? I googled for an answer to this problem, and although I found 10 pages of other people having the problem, I didn't see any answers :-( This is what I'm doing: (following the tutorial minus the part about using his giant class) - I created a parent dialog, put a placeholder resource on it where the child will go - created the child dialog resource with Style: Child, Border: None, Control: True - created a normal parent dialog as I always do - in the parent's DoDataExchange i used the DDX_Control function to tie the placeholder resource to my Child member object - in the parent's OnInitDialog i call .Create for the child dialog, there is only 2 versions of create, wich both take the Template ID/Name, and a CWnd*, so i passed the child resource's ID (IDD_CHILDDIALOG), and "this" any ideas? :confused:

So I'm making a dialog based app in MFC, and I'd like to make a child Dialog that is acts like a control and part of my parent dialog... Seems like a very easy task, but for some reason I must be doing something wrong... I see a tutorial here on CP explaining it (http://www.codeproject.com/KB/dialog/CRHChildDialog.aspx[^]), but I don't like that solution, I'd rather not have to include someone else's custom code in my project... Anyone know of any other tutorials? Sorry if this has been asked before; I searched and didn't find much.

Give each employee a phat bonus?

Gothic Christmas http://www.youtube.com/watch?v=aDa4GlInwaE[^]

Chuck Norris doesn't act. Characters act like Chuck Norris. OHHHHHHHH SNAP.

I plan on downing many black and tans.

Ah thanks... I had already tried googling for the error message and gone through plenty of pages, but I just went through them all again and a few more this morning, and finially found it.. Most of them were a slightly different bug, but incase someone else has the problem and ends up here: "To fix the problem, I made a minor change to the include paths in the IDE. Tools -> Options -> Projects and Solutions -> VC++ Directories Show directories for: Include files I Added a slash to my last path, so "P:\" became "P:\\". Ok the changes and the problem went away. :-) Hope this works for you. Andy"

In VS2005 running on WinXP Pro, I keep getting this error, "fatal error RC1107" any time I try to double click the resource file for my project in the Solution Explorer. It's not just one project, it's all of them. And even if I make a new project just from scratch, it still happens. So there has to be something wrong with my machine right? Here's a pic of my problem for those who care to see... Everywhere I went, they all said it has to do with project settings, and a bug in visual studio that was adding double quotes, but my Resources Command Line looks fine: /d "_DEBUG" /d "_AFXDLL" /l 0x409 /I "Debug" /fo"Debug/WadBuilder.res" Any ideas would be great :-) Sorry if this has already been addressed a thousand times before. I did a few hours of searching on the internet, and none of the other solutions I saw worked... Thanks in advance.