Virtualize StartEditor and add implementations for the ports that can do it.

[wxWidgets.git] / interface / wx / dcbuffer.h

diff --git a/interface/wx/dcbuffer.h b/interface/wx/dcbuffer.h
index ef03428a370cf6ee73501e69f935f3e73c9e2fb8..ec2bb28d7000685d7a2b18345035c358b8ba1e9e 100644 (file)
--- a/interface/wx/dcbuffer.h
+++ b/interface/wx/dcbuffer.h
@@ -10,7 +10,7 @@
     @class wxBufferedDC
 
     This class provides a simple way to avoid flicker: when drawing on it,
     @class wxBufferedDC
 
     This class provides a simple way to avoid flicker: when drawing on it,

-    everything is infact first drawn on an in-memory buffer (a wxBitmap) and
+    everything is in fact first drawn on an in-memory buffer (a wxBitmap) and

     then copied to the screen, using the associated wxDC, only once, when this
     object is destroyed. wxBufferedDC itself is typically associated with
     wxClientDC, if you want to use it in your @c EVT_PAINT handler, you should
     then copied to the screen, using the associated wxDC, only once, when this
     object is destroyed. wxBufferedDC itself is typically associated with
     wxClientDC, if you want to use it in your @c EVT_PAINT handler, you should


@@ -120,7 +120,7 @@ public:
 
     The difference between wxBufferedPaintDC and this class is that this class
     won't double-buffer on platforms which have native double-buffering
 
     The difference between wxBufferedPaintDC and this class is that this class
     won't double-buffer on platforms which have native double-buffering

-    already, avoiding any unneccessary buffering to avoid flicker.
+    already, avoiding any unnecessary buffering to avoid flicker.

 
     wxAutoBufferedPaintDC is simply a typedef of wxPaintDC on platforms that
     have native double-buffering, otherwise, it is a typedef of
 
     wxAutoBufferedPaintDC is simply a typedef of wxPaintDC on platforms that
     have native double-buffering, otherwise, it is a typedef of