.. include:: headings.inc

.. module:: lib.pdfviewer.dcgraphics

.. currentmodule:: lib.pdfviewer.dcgraphics

.. highlight:: python



.. _lib.pdfviewer.dcgraphics:

==========================================================================================================================================
|phoenix_title|  **dcgraphics**
==========================================================================================================================================

This module implements an API similar to wx.GraphicsContext and the
related classes. The implementation is done using wx.DC

Why do this?  Neither wx.GraphicsContext not the Cairo-based
GraphicsContext API provided by wx.lib.graphics can be written
directly to a PrintDC. It can be done via an intermediate bitmap in
a MemoryDC but transferring this to a PrintDC is an order of magnitude
slower than writing directly.

Why not just use wxPrintDC directly?  There may be times when you do want
to use wx.GraphicsContext for its displayed appearance and for its
clean(er) API, so being able to use the same code for printing as well is nice.

It started out with the intention of being a full implementation of the 
GraphicsContext API but so far only contains the sub-set required to render PDF.
It also contains the co-ordinate twiddles for the PDF origin, which would need
to be separated out if this was ever developed to be more general purpose.



|

|class_hierarchy| Inheritance Diagram
=====================================

Inheritance diagram for module **dcgraphics**

.. raw:: html

   <p class="graphviz">
   <img src="_static/images/inheritance/lib.pdfviewer.dcgraphics_inheritance.png" alt="Inheritance diagram of dcgraphics" usemap="#dummy" class="inheritance"/>
   <map id="dummy" name="dummy"> <area shape="rect" id="node1" href="lib.pdfviewer.dcgraphics.dcGraphicsMatrix.html" title="A matrix holds an affine transformations, such as a scale," alt="" coords="289,5,524,35"/> <area shape="rect" id="node4" href="lib.pdfviewer.dcgraphics.dcGraphicsContext.html" title="dcgraphics.dcGraphicsContext" alt="" coords="284,58,529,89"/> <area shape="rect" id="node7" href="lib.pdfviewer.dcgraphics.dcGraphicsPath.html" title="A GraphicsPath is a representaion of a geometric path, essentially" alt="" coords="295,111,519,142"/> <area shape="rect" id="node6" href="lib.pdfviewer.dcgraphics.dcGraphicsState.html" title="Each instance holds the current graphics state. It can be" alt="" coords="5,5,235,35"/> </map> 
   </p>

|


|class_summary| Classes Summary
===============================

================================================================================ ================================================================================
:ref:`lib.pdfviewer.dcgraphics.dcGraphicsContext`                                
:ref:`lib.pdfviewer.dcgraphics.dcGraphicsMatrix`                                 A matrix holds an affine transformations, such as a scale,
:ref:`lib.pdfviewer.dcgraphics.dcGraphicsPath`                                   A GraphicsPath is a representaion of a geometric path, essentially
:ref:`lib.pdfviewer.dcgraphics.dcGraphicsState`                                  Each instance holds the current graphics state. It can be
================================================================================ ================================================================================


|


.. toctree::
   :maxdepth: 1
   :hidden:

   lib.pdfviewer.dcgraphics.dcGraphicsContext
   lib.pdfviewer.dcgraphics.dcGraphicsMatrix
   lib.pdfviewer.dcgraphics.dcGraphicsPath
   lib.pdfviewer.dcgraphics.dcGraphicsState