C / C++ / MFC

Blake Coverett22-Sep-03 18:11

Blake Coverett

22-Sep-03 18:11

SetROP2(R2_XORPEN) and don't forget to redraw the old line before drawing the next one.

--
-Blake (com/bcdev/blake)

whiteclouds22-Sep-03 18:28

whiteclouds

22-Sep-03 18:28

Hi.
I do so.The color of the line I drawn is changed.But the line didn't dispear.Why?

Blake Coverett22-Sep-03 21:34

Blake Coverett

22-Sep-03 21:34

That's the second part of what I wrote earlier. You have to remember the coordinates to which you last drew the line. Then on a mouse move you redraw it again at the old location to erase it and draw it at the new location.

--
-Blake (com/bcdev/blake)

whiteclouds22-Sep-03 23:06

whiteclouds

22-Sep-03 23:06

I know the principle of the procedure.I use the SetRop2() function to realize it.But which parameter should I select? R2_NOT? Or R2_XORPEN?Almost all parameter I had test.None looks like correct.
And I've another question.I wrote message processed module associate to mousemove to draw line.But when the window is restore from behind other window,the line dispeared.Why?How can I resolve it?
Please help me!If you resolve my question,I can buy some gift for you if you want.;)

A ridiculous beginners question

Blake Coverett22-Sep-03 23:39

Blake Coverett

22-Sep-03 23:39

R2_NOT will work, it simply inverts the background pixels and ignores the pen.

R2_XORPEN will work better, as it lets you controlly the visual result better, using a dashed pen for example.

If it isn't looking correct I suspect you are not redrawing over the previous line exactly.

Things you draw during mousemove are not permanent. Your application needs to redraw everything, including the newly added line, when handling WM_PAINT as well.

--
-Blake (com/bcdev/blake)

Terry O'Nolley22-Sep-03 17:23

22-Sep-03 17:23

I have laboriously coded around this little problem for years and I know that the solution is quite simple. But I am resistant to change and hate having to delve into documentation.

I am getting that "class already defined" error message when I include the same header file in more than 1 source file.

Here is what is happening:

ClassX - a user defined class
Window1 - the apps main window
Window2 - a modal dialog box invoked from Window1

Window1 has an instance of ClassX and so has "#include ClassX.h" in its header file (and won't compile without it of course)

Window2 has an instance of ClassX and so needs to "#include ClassX.h" in its header file

But it can't because it throws that error "C2011: 'ClassX' : 'class' type redefinition" error

Why is it that you can include headers like "afxdb.h" in a zillion files and not get this error?

If the compiler knows that the class is already defined, then why does it need the header file in both places?

Nish Nishant22-Sep-03 17:39

Nish Nishant

22-Sep-03 17:39

Terry O`Nolley wrote:
Window1 has an instance of ClassX and so has "#include ClassX.h" in its header file (and won't compile without it of course)

Window2 has an instance of ClassX and so needs to "#include ClassX.h" in its header file

Declare the ClassX header file in Window1's and Window2's cpp files and not in the h files. make sure you include this header *before* you include te header file for Window1/Window2. So Window1.cpp would ne :-

include classx header
include window2 header
include window1 header
...

and window2.cpp wopuld be :-

include classx header
include window2 header
...

Regards
Nish

Extending MFC Applications with the .NET Framework [NW] (coming soon...)
Summer Love and Some more Cricket [NW] (My first novel)
Shog's review of SLASMC [NW]
Come with me if you want to live

Terry O'Nolley22-Sep-03 17:54

22-Sep-03 17:54

Thanks Nish.

This brings me to a problem though - since Window2 needs a member variable of ClassX (because that member variable will be filled in by Window1 after instantiating Window2 but before calling DoModal()) doesn't the #include ClassX.h need to go before the class definition for Window2?

Nish Nishant22-Sep-03 18:19

Nish Nishant

22-Sep-03 18:19

Hey Terry

While Mike's ifdef solution probably solved the issue, by including header files in the right order in cpp files, the issue can be solved without using preprocessor directives (which makes the code easy to port assuming you wanna port it of course)

Anyway, glad you got it working right Smile | :)

Nish

Extending MFC Applications with the .NET Framework [NW] (coming soon...)
Summer Love and Some more Cricket [NW] (My first novel)
Shog's review of SLASMC [NW]
Come with me if you want to live

Terry O'Nolley22-Sep-03 19:15

22-Sep-03 19:15

How would you resolve the issue I was having without using preprocessor directives?

I seemed to have been caught in a Catch-22.

WHen I followed your example, it didn't give an error relating to duplicate class definitions, but I got errors for an undefined keyword (ClassX) because the ClassX header wasn't included until after I tried to define an object of ClassX.

Nish Nishant22-Sep-03 19:17

Nish Nishant

22-Sep-03 19:17

Terry O`Nolley wrote:
WHen I followed your example, it didn't give an error relating to duplicate class definitions, but I got errors for an undefined keyword (ClassX) because the ClassX header wasn't included until after I tried to define an object of ClassX

In any CPP file, you *must* include the ClassX header file *before* you include any other header file that might declare a ClassX member.

Nish

Extending MFC Applications with the .NET Framework [NW] (coming soon...)
Summer Love and Some more Cricket [NW] (My first novel)
Shog's review of SLASMC [NW]
Come with me if you want to live

Terry O'Nolley23-Sep-03 7:53

23-Sep-03 7:53

I know this. But your first suggestion told me to include the header file in the .cppp file for Window 2 to avoid the "duplicate class name" error. I couldn't do this, because there was a member variable of tyoe ClassX in Window2.

When presented with the preprocessor directives, I implemented them and it fixed the problem but you said this was not a preferred technique because of portability concerns.

How would you do this without preprocessor directives?

ClassX

Window1 : has a member var of ClassX so needs #include ClassX.h
Window2 : has a member var of ClassX so needs #include ClassX.h

if I include them both where you have agreed they need to be ie before the ClassX object is defined I get a compiler error of a duplicate class name.

If I include them where you first told me (in the CPP file before the window header) I get an undefined name error.

Using preprocessor directives allowed me to successfully do what I needed but you said it was a poor solution.

I would like to know the correct solution.

Michael Dunn22-Sep-03 17:58

Michael Dunn

22-Sep-03 17:58

You need include guards in your header files:

// In ClassX.h
 
#ifndef CLASSX_H_INCLUDED
#define CLASSX_H_INCLUDED
 
// rest of header here...
 
#endif // ndef CLASSX_H_INCLUDED

There is also #pragma once but I prefer the above way since you can test for whether ClassX.h has been included with #ifdef CLASSX_H_INCLUDED

--Mike--
Ericahist | Homepage | RightClick-Encrypt | 1ClickPicGrabber
CP SearchBar v2.0.2 released

Terry O'Nolley22-Sep-03 18:15

22-Sep-03 18:15

Thanks Mike - that did the trick.

I had used those a while back without remembering why I used them Smile | :)

And I never noticed when I stopped using them.

I guess it took a big screeching halt to make me remember to always use them.

Rick York22-Sep-03 18:26

Rick York

22-Sep-03 18:26

I take things a bit farther. Here is what I do :

#ifndef _HEADER_H
#define _HEADER_H
#else
#error repeated include of this file
#endif

then if this header must be included in another header file (nested) I do this -

#ifndef _HEADER_H
#include header.h
#endif

I went through and converted a rather large project to this scheme and my compile times decreased considerably. If you use a standard macro naming mechanism (_HEADER_H for me) then this is quite easy to use.

The Ten Commandments For C Programmers

Alvaro Mendez23-Sep-03 4:22

Alvaro Mendez

23-Sep-03 4:22

Rick York wrote:
#ifndef _HEADER_H
#include header.h
#endif

I used this technique for a while and then I realized that the increased code clutter (three lines/include vs just one) wasn't worth the extra milliseconds saved per compiled unit. Instead, I made sure to use a precompiled header which really sped things up.

Regards,
Alvaro

Hey! It compiles! Ship it.

Rick York24-Sep-03 14:09

Rick York

24-Sep-03 14:09

I know what you mean but I only do this when nesting include files - including one header in another. This keeps the headers safe. I don't do this in standard code as I'll see the error soon enough.

Yes, in most projects, the savings amount to milliseconds but in large scale projects this can add up significantly. I have been forced to use a library that is absolutely atrocious in this respect.

The Ten Commandments For C Programmers

John M. Drescher22-Sep-03 18:02

John M. Drescher

22-Sep-03 18:02

Terry O`Nolley wrote:
Why is it that you can include headers like "afxdb.h" in a zillion files and not get this error?
You can use either an ifdef to include the cpp file only once

#if !defined(_MYCPPFILENAME_)
// make sure _MYCPPFILENAME_ is not defined in any of your headers or cpp files
#define _MYCPPFILENAME_

// Put your class def here.

#endif //def _MYCPPFILENAME_

Or you can use this as the first statement in your header file

#pragma once

There is a macro in vc6 that does this for you. Click Tools then customize then addins and macro files and then make sure SAMPLE is checked. Then open your header file and click tools then macros select sample and then select OneTimeInclude and click run.

John

Terry O'Nolley22-Sep-03 18:20