C / C++ / MFC

Re: Sending message from one window to another

23-Jan-06 19:52

Use the SendMessage[^] API function

::SendMessage( hWnd /* Your Window Handle */, WM_YOURMESSAGE, 0, 0 );

Gavin Taylor
w: http://www.gavspace.com

S Douglas24-Jan-06 21:07

S Douglas

24-Jan-06 21:07

Irina Tseitlin wrote:
I have application in MFC and i want to send message from one window(dialog) to another window(dialog) in this

Read this article about message management.

Message Management[^]

is this tricky

anup nambiar23-Jan-06 19:22

anup nambiar

23-Jan-06 19:22

int i=7; printf("%d",i++ * i++ ); output is 49 ; how is this possible ?? i think it should it be 56 . if it is 49 how can this be justified

Gavin Taylor23-Jan-06 19:49

23-Jan-06 19:49

First off, if your using the ++ operator and passing the value as an argument you should prefix not postfix the the operator ( ie. ++i ) else the value is incremented after the statement is executed - see the c++ documentation for more details.

Secondly, ur incrementing the value twice - so you'll end up with a result of 64 being printed (8 x 8).

Simple really... Smile | :)

Gavin Taylor
w: http://www.gavspace.com

Owner drawn23-Jan-06 19:55

23-Jan-06 19:55

Gavin Taylor wrote:
so you'll end up with a result of 64 being printed (8 x 8).

But he's saying the output is 49.

Jesus Loves Rose | [Rose]

<marquee direction="up" height="40" scrolldelay="1" step="1" scrollamount="1" style="background:#aabbcc;border-bottom:thin solid 1px #6699cc">
--Owner Drawn Rose | [Rose]

--Nothing special
--Defeat is temporary but surrender is permanent
--Never say quits
--Jesus is Lord Rose | [Rose]

Gavin Taylor23-Jan-06 20:03

23-Jan-06 20:03

Thats my point, he's multiplying 7 * 7 and the ++ is getting executed after the main statement.

Gavin Taylor
w: http://www.gavspace.com

Michael Dunn23-Jan-06 20:19

Michael Dunn

23-Jan-06 20:19

Short answer: don't do that.
Long answer: Having more than one ++ or -- operating on the same variable in the same expression is bound to expose an implementation detail and give unexpected results. It's the same reason that you shouldn't do this:

int a = 7;
int b = a++ + ++a;

--Mike--
Visual C++ MVP Cool | :cool:

LINKS~! Ericahist | NEW!! PimpFish | CP SearchBar v3.0 | C++ Forum FAQ
Pinky, are you pondering what I'm pondering?
I think so Brain, but how will we fit the hamster inside the accordion?

Gavin Taylor23-Jan-06 20:33

23-Jan-06 20:33

Michael Dunn wrote:
b = a++ + ++a;

*shudder* That just kinda makes me feel dirty looking at it Smile | :)

Gavin Taylor
w: http://www.gavspace.com

Dll with real modal dialog boxes

Ryan Binns23-Jan-06 22:01

Ryan Binns

23-Jan-06 22:01

The ++ operator does take affect until the next sequence point is reached, in this case the semicolon at the end of the statement, so i is not incremented until after the function call.

But as Michael said, don't use more than one ++ or -- on a variable in a single line - you are violating the C++ standard, which states that no variable can be modified more than once between successive sequence points.

Ryan

"Punctuality is only a virtue for those who aren't smart enough to think of good excuses for being late" John Nichol "Point Of Impact"

romano_sk23-Jan-06 19:20

romano_sk

23-Jan-06 19:20

Hi,

I have created a dll file with dialog box. Dll I am using in Visual Basic .NET. How can I display the dialog box so the user could not switch back to the original form without closing the dialog box? Like system Open or Save dialog boxes...

1. For displaying my dialog box from DLL I am using following code:

DialogBox(_hInstDLL, MAKEINTRESOURCE(DLG_MAIN), NULL, (DLGPROC)MainDlgProc);

With this code the user could change focus to the application window in Visual Basic .NET.

2. I have tried also send an handle of application window:

DWORD WINAPI ShowConfigurationDialog (HWND hwndParent, ...)
{
    ...
    DialogBox(_hInstDLL, MAKEINTRESOURCE(DLG_MAIN), hwndParent, (DLGPROC)MainDlgProc);
}

And from Basic:

ShowConfigurationDialog(Me.Handle.ToInt32, ...)

In this case the dialog box will not be displayed at all and DialogBox returns with 0.

Thanks, Roman

Re: Dll with real modal dialog boxes

romano_sk26-Jan-06 22:23

romano_sk

26-Jan-06 22:23

Ooo

, I did not pass the handle's value but the handle's address!

I have mistake in declaration:
ShowConfigurationDialog(ByRef ParentHWND, ...)

Right one:
ShowConfigurationDialog(ByVal ParentHWND, ...)

Big Grin | :-D

Compiler doesn't know class.... sometimes

Lilith.C23-Jan-06 19:01

Lilith.C

23-Jan-06 19:01

In preparation for retro-incorporating the MiniExcel class into a number of my projects I've set up a practice project in order to get familiar with the class. I'm in VC++ 6.0 and the project is an MFC exe. I've put the mexcel.cpp and mexcel.h files in the base project directory. I've added both files to the project. I've #included mexcel.h in stdafx.h and also, for good measure, in the view doc file. The class shows up in the Classes tab, though it doesn't show up in ClassWizard after a rebuild of the CLW file.

I've declare an object of class CMiniExcel as a local variable inside a button message handler. When I go to compile I get four errors. The first three indicate that the class is unknown. The fourth is:

fatal error C1010: unexpected end of file while looking for precompiled header directive

Additionally I've noticed that instead of being placed in the DEBUG directory the system has created a directory with the projects base name followed by ___Win32_Debug

Am I using a class that needs to be modified to work under MFC or am I overlooking something else.

Thanks,
Lilith

Michael Dunn23-Jan-06 20:22

Michael Dunn

23-Jan-06 20:22

See the FAQ
2.5 I added some source files I got from someone else into my project and the compiler gives the error "C1010: unexpected end of file while looking for precompiled header directive." Why?[^]

Fixing the PCH settings may take care of the other errors

--Mike--
Visual C++ MVP Cool | :cool:

LINKS~! Ericahist | NEW!! PimpFish | CP SearchBar v3.0 | C++ Forum FAQ
Come quietly or there will be... trouble.

Lilith.C24-Jan-06 2:10

Lilith.C

24-Jan-06 2:10

Sorry, still no change. But thanks nonetheless.

Lilith

Lilith.C24-Jan-06 6:29

Lilith.C

24-Jan-06 6:29

blockquote class="FQ">

Michael Dunn wrote:

Fixing the PCH settings may take care of the other errors

A revision to my previous reply. I've gotten past the error but have gotten four warnings of the same type. It compiles and links. But I'd be interested in suppressing the warnings if possible. The error/warning is

C4786
'identifier' : identifier was truncated to 'number' characters in the debug information

The identifier string exceeded the maximum allowable length and was truncated.

It doesn't appear to be an identifer as much as it's an expansion of a vector template. Since namespace is specified as std that gets included in the expansion to the point that the entire line is over 300 characters.

Lilith

MDI non-themed max/min boxes

Michael Dunn24-Jan-06 7:17

Michael Dunn

24-Jan-06 7:17

Lilith.C wrote:
C4786
'identifier' : identifier was truncated to 'number' characters in the debug information

That's harmless, you can turn it off.

--Mike--
Visual C++ MVP Cool | :cool:

LINKS~! Ericahist | NEW!! PimpFish | CP SearchBar v3.0 | C++ Forum FAQ
Ford, what's this fish doing in my ear?

picazo23-Jan-06 18:49

picazo

23-Jan-06 18:49

Hello.

When creating a MDI application (with MFC AppWizard VC++ 6.0) you have the choice of excluding the maximize/minimize boxes for the child frames.

When creating my MDI app, I chose to not have the maximize/minimize boxes, but to have the child frames start in 'maximize mode'. However, when the child frames are viewed in 'maximized mode', the non-themed minimize and maximize buttons are still drawn.

Is there a way to remove or at least disable the non-themed maximize/minimize buttons?

-----------------
Genaro

Owner drawn23-Jan-06 18:54

23-Jan-06 18:54

You can remove WS_MAXIMIZEBOX and WS_MINIMIZEBOX from the concerned window's style.

BOOL CChildFrame::PreCreateWindow(CREATESTRUCT& cs)
{
	//Modify the Window class or styles here by modifying the CREATESTRUCT cs

	<code>cs.style&=~(WS_MAXIMIZEBOX|WS_MINIMIZEBOX);</code>
	if( !CMDIChildWnd::PreCreateWindow(cs) )
		return FALSE;

	return TRUE;
}

Jesus Loves Rose | [Rose]

<marquee direction="up" height="40" scrolldelay="1" step="1" scrollamount="1" style="background:#aabbcc;border-bottom:thin solid 1px #6699cc">
--Owner Drawn Rose | [Rose]

--Nothing special
--Defeat is temporary but surrender is permanent
--Never say quits
--Jesus is Lord Rose | [Rose]

picazo23-Jan-06 18:59

picazo

23-Jan-06 18:59

I tried that in the BOOL CChildFrame::PreCreateWindow(CREATESTRUCT& cs) function. However, that only removes the boxes if the child frame is not in 'maximized mode'. What function should I edit/override to also remove the non-themed buttons (those show when in maximized mode)?

Thank you very much,

-----------------
Genaro

Owner drawn23-Jan-06 19:22

23-Jan-06 19:22

This is going to be dirty... Dead | X|

Remove WS_SYSMENU style from the window style.

Jesus Loves Rose | [Rose]

<marquee direction="up" height="40" scrolldelay="1" step="1" scrollamount="1" style="background:#aabbcc;border-bottom:thin solid 1px #6699cc">
--Owner Drawn Rose | [Rose]

--Nothing special
--Defeat is temporary but surrender is permanent
--Never say quits
--Jesus is Lord Rose | [Rose]

picazo23-Jan-06 19:56

picazo

23-Jan-06 19:56

Thank you very much for the help...

I am almost there. The only thing is that removing the WS_SYSMENU also removes the [x], which I would like to keep. Is it possible to do that?

Thanks,

-----------------
Genaro

Owner drawn23-Jan-06 22:04