3f66f6a5b3
This keyword is not expanded by Git which means it's not replaced with the correct revision value in the releases made using git-based scripts and it's confusing to have lines with unexpanded "$Id$" in the released files. As expanding them with Git is not that simple (it could be done with git archive and export-subst attribute) and there are not many benefits in having them in the first place, just remove all these lines. If nothing else, this will make an eventual transition to Git simpler. Closes #14487. git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@74602 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
48 lines
1.8 KiB
C
48 lines
1.8 KiB
C
/////////////////////////////////////////////////////////////////////////////
|
|
// Name: dc.h
|
|
// Purpose: topic overview
|
|
// Author: wxWidgets team
|
|
// Licence: wxWindows licence
|
|
/////////////////////////////////////////////////////////////////////////////
|
|
|
|
/**
|
|
|
|
@page overview_dc Device Contexts
|
|
|
|
A wxDC is a @e device context onto which graphics and text can be drawn.
|
|
The device context is intended to represent a number of output devices in a
|
|
generic way, with the same API being used throughout.
|
|
|
|
Some device contexts are created temporarily in order to draw on a window.
|
|
This is @true of wxScreenDC, wxClientDC, wxPaintDC, and wxWindowDC.
|
|
The following describes the differences between these device contexts and
|
|
when you should use them.
|
|
|
|
@li @b wxScreenDC. Use this to paint on the screen, as opposed to an individual window.
|
|
@li @b wxClientDC. Use this to paint on the client area of window (the part without
|
|
borders and other decorations), but do not use it from within an wxPaintEvent.
|
|
@li @b wxPaintDC. Use this to paint on the client area of a window, but @e only from
|
|
within a wxPaintEvent.
|
|
@li @b wxWindowDC. Use this to paint on the whole area of a window, including decorations.
|
|
This may not be available on non-Windows platforms.
|
|
|
|
To use a client, paint or window device context, create an object on the stack with
|
|
the window as argument, for example:
|
|
|
|
@code
|
|
void MyWindow::OnMyCmd(wxCommandEvent& event)
|
|
{
|
|
wxClientDC dc(window);
|
|
DrawMyPicture(dc);
|
|
}
|
|
@endcode
|
|
|
|
Try to write code so it is parameterised by wxDC - if you do this, the same piece of code may
|
|
write to a number of different devices, by passing a different device context. This doesn't
|
|
work for everything (for example not all device contexts support bitmap drawing) but
|
|
will work most of the time.
|
|
|
|
@see @ref group_class_dc
|
|
|
|
*/
|