Urgent!!!
hello,guys
i need emergency help from yeah.here is my problem
i need to know certain thing in here.
what is common device content?
2.class device content
3.parent device content.
4.owner device content.
5.window device content..
i wanna to know what is it and the usage of it. moreover the the different of each other.
thanks..urgent
sorry man, never heard of device contents, are you sure itīs not Device context?
yes,i am learning win32api.it's on the chapter.
Api functions for working with device contexts.
example like this code one.
hdc=getdc(hwnd);
textout(hdc,10,10,"text displaying",20);
releasedc(hwnd,hdc);
plss help me...........
Think of a device context as the "canvas" upon which everything is drawn.
There are a few types of DCs (Display, Printer, Memory, and Information) which tell how the DC acts. Display and memory DCs are the primary DCs you will need.
Now, there are a few types of display DCs (common, class, private) which basically tell how the DC is stored in memory. This basically determines whether the attributes are reset after you are done using it or not.
There are a few useful display DCs:
* The screen DC is the entire screen -- when you draw on this, the changes appear on the screen. Most applications never need to use this.
* The window DC allows you to get a "canvas" that is as large as the window -- so you can draw as much as you want on your window, but not outside of it. You can us the WinAPI call GetWindowDC() to get this type of DC.
* The client DC is like the window DC, but it is the window without menus, borders, etc. -- it is the "main part" of the window. This is a very useful DC, perhaps the most useful, and you can get it with GetDC().
* The paint DC is an important and useful one -- it is sent to your program when an area of the window needs to be redrawn -- so your program can paint on this DC to do that. Unlike other DCs, this is actually passed as a parameter during the WM_PAINT message, so you don't need to create the DC yourself (unless it passes a null handle).
A Memory DC is a DC that, when changed, does not immediately affect the screen, but rather, it is something like having a "back buffer" -- you can use this to make sure all changes you plan on making happen at once, as far as the user is concerned, rather than have a lot of flicker as you constantly redraw parts of an image.
Also, if your book didn't include win32.hlp, MS's documentation of the WinAPI, GET IT!
This is a 12 MB help file, and has a lot of useful info.
Listen to the V. 12 megs seems like a lot, but once you have it you will find that it was worth the d/l.
