|
Thanks, I sorta understand what you mean, but can you tell me what additional code I need to use it/how to set it up?
|
|
|
|
|
For eg:
BYTE redValue;
BYTE greenValue;
BYTE blueValue;
redValue = GetRValue(GetPixel(hdc,50,50));
greenalue = GetGValue(GetPixel(hdc,50,50));
blueValue = GetBValue(GetPixel(hdc,50,50));
Press: 1500 to 2,200 messages in just 6 days? How's that possible sir?
Dr.Brad :Well,I just replied to everything Graus did and then argued with Negus for a bit.
|
|
|
|
|
hdc = undeclared identifier.
|
|
|
|
|
Are you trying to get the color of a pixel on the screen? In a bitmap? If a bitmap, what form
of bitmap...Windows device independent, Windows device dependent?
"Great job, team. Head back to base for debriefing and cocktails."
(Spottswoode "Team America")
|
|
|
|
|
arunforce wrote: undeclared identifier.
Weird exception!;P But is it not good you learn something before asking questions? I help you out : HDC[^]
Press: 1500 to 2,200 messages in just 6 days? How's that possible sir?
Dr.Brad :Well,I just replied to everything Graus did and then argued with Negus for a bit.
|
|
|
|
|
You only wanted one word, but for Windows graphics programming, DCs are an essential concept,
regardless of classes and OOP stuff.
If you decide you want to learn it, here's some free info: Device Contexts[^]
"Great job, team. Head back to base for debriefing and cocktails."
(Spottswoode "Team America")
|
|
|
|
|
"undeclared identifier"
Your code has an error maybe compiler has an internal error;P;)
|
|
|
|
|
Sorry, I should of specified. It's just to get the pixel color of the pixel on the entire screen, doesn't matter what application or whatever, I could probably code it in VB or Java easier, but I want to make it professional. It's been a good 2 years since I've even touched C++, and it's a bit troubling.
C++'s keywords and stuff throw me off, I find that it has no relation to a similar structure, and it's a bit confusing. I probably need more experience, but then again, I'm just 17. :/
|
|
|
|
|
arunforce wrote: It's just to get the pixel color of the pixel on the entire screen
In that case, as Vunic suggested, the GetDC(NULL) API will get you a screen DC. Don't forget to
free it when you are finished with it (ReleaseDC()).
Mark
"Great job, team. Head back to base for debriefing and cocktails."
(Spottswoode "Team America")
|
|
|
|
|
arunforce wrote: I could probably code it in VB or Java easier
Yup it is, when you opt for the Ignorance is bliss thinge. Just 17? Great, you are trying something good. At your age I never managed to install an IDE in my pc. The only user-made directory in my pc was "GAMES". C:\CD GAMES.  lol.. it was all games.
Press: 1500 to 2,200 messages in just 6 days? How's that possible sir?
Dr.Brad :Well,I just replied to everything Graus did and then argued with Negus for a bit.
|
|
|
|
|
Is there anyway to Parse a Macro with the Visual Express Debugger When I try to Step into it It says on Source Code and askss me if I want to see Assembly code
|
|
|
|
|
You could manually preprocess the file in question using the compiler's /P[^] and /C[^] options. This will product a .i file from the .c or .cpp file. Remove the .c or .cpp file in question and replace it with the .i file with the extension renamed to .c or .cpp, as the case may be. Now debug as normal.
Steve
|
|
|
|
|
I am assuming the compiler will parse the Macro with options in question and produce a .i file If I reanme to a .c The debugger will use that source code
|
|
|
|
|
Yeah, that's the idea. I use this technique when debugging macro code. The problem you're experiencing is just one reason why macros should be avoided if possible.
Steve
|
|
|
|
|
Cool I an Assembler MVS internals guy I found some intresting project that helped me learn C/C++
Since you seem to be on really good at this Visual C any ideas how I can become better at it
|
|
|
|
|
I guess just practice and read.
Steve
|
|
|
|
|
Thankx But unfortantly the code in question is in .h file anything to parse that out
|
|
|
|
|
That's no problem: you pre-preprocess the C/CPP file(s) that include it.
Steve
|
|
|
|
|
Okay you have been very helpfull thankx much
|
|
|
|
|
I got the parsed out listing rename it to .c however doesn't seem like I am able to make a breakpoint or at least have Visual studio Stop at the Macro like it did without the preprocessor listing
|
|
|
|
|
I tried to send you this message but looks I sent it to myself
anyway here goes
I got the parsed out listing rename it to .c however doesn't seem like I am able to make a breakpoint or at least have Visual studio Stop at the Macro like it did without the preprocessor listing
|
|
|
|
|
At this stage the easiest thing to do would be to rename the original file, place the pre-preprocessed file in the same location and rename it so it's used instead of the original file. Place breakpoints in this file: all macros have been expanded.
Steve
|
|
|
|
|
I did that meaning make a breakpoint with the renamed .i file
The code above it gets excuted a millon times so can'nt move the breakpoint further up
Maybe I should rebuild with renamed .i file which has the parsed code
|
|
|
|
|
ForNow wrote: Maybe I should rebuild with renamed .i file which has the parsed code
I took that as given; sorry, perhaps I should have been more explicit. To rebuild with the pre-preprocessed file replacing the original file is the whole point.
Steve
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
