`wx.Bitmap`) and then copied to the screen only once, when this object
is destroyed.
-It can be used in the same way as any other device
-context. wx.BufferedDC itself typically replaces `wx.ClientDC`, if you
-want to use it in your EVT_PAINT handler, you should look at
+It can be used in the same way as any other device context.
+wx.BufferedDC itself typically replaces `wx.ClientDC`, if you want to
+use it in your EVT_PAINT handler, you should look at
`wx.BufferedPaintDC`.
+
+Please note that GTK+ 2.0 and OS X provide double buffering themselves
+natively so using this class on those platforms will normally result
+in an unneeded level of buffering.
", "");
class wxBufferedDC : public wxMemoryDC
EVT_SCROLL_PAGEDOWN page down events
EVT_SCROLL_THUMBTRACK thumbtrack events (frequent events sent
as the user drags the 'thumb')
- EVT_SCROLL_THUMBRELEASE thumb release events.
- EVT_SCROLL_ENDSCROLL End of scrolling
+ EVT_SCROLL_THUMBRELEASE thumb release events
+ EVT_SCROLL_CHANGED End of scrolling
======================= ==========================================
Note
The EVT_SCROLL_THUMBRELEASE event is only emitted when actually
dragging the thumb using the mouse and releasing it (This
EVT_SCROLL_THUMBRELEASE event is also followed by an
- EVT_SCROLL_ENDSCROLL event).
+ EVT_SCROLL_CHANGED event).
- The EVT_SCROLL_ENDSCROLL event also occurs when using the keyboard
+ The EVT_SCROLL_CHANGED event also occurs when using the keyboard
to change the thumb position, and when clicking next to the thumb
(In all these cases the EVT_SCROLL_THUMBRELEASE event does not
happen).
- In short, the EVT_SCROLL_ENDSCROLL event is triggered when
+ In short, the EVT_SCROLL_CHANGED event is triggered when
scrolling/ moving has finished. The only exception (unfortunately)
is that changing the thumb position using the mousewheel does give
- a EVT_SCROLL_THUMBRELEASE event but NOT an EVT_SCROLL_ENDSCROLL
+ a EVT_SCROLL_THUMBRELEASE event but NOT an EVT_SCROLL_CHANGED
event.
");
EVT_SCROLLWIN_PAGEDOWN page down events
EVT_SCROLLWIN_THUMBTRACK thumbtrack events (frequent events sent
as the user drags the 'thumb')
- EVT_SCROLLWIN_THUMBRELEASE thumb release events.
- EVT_SCROLLWIN_ENDSCROLL End of scrolling
+ EVT_SCROLLWIN_THUMBRELEASE thumb release events
+ EVT_SCROLLWIN_CHANGED End of scrolling
========================== ==========================================
:see: `wx.ScrollEvent`
%extend {
wxWindow* GetMainWindow() {
- #ifdef __WXMSW__
+ #if defined(__WXMSW__) || defined(__WXMAC__)
return self;
#else
return (wxWindow*)self->m_mainWin;
wxTB_HORZ_LAYOUT,
wxTB_HORZ_TEXT,
wxTB_NO_TOOLTIPS,
+ wxTB_BOTTOM
};
TB_HORZ_LAYOUT = _controls_.TB_HORZ_LAYOUT
TB_HORZ_TEXT = _controls_.TB_HORZ_TEXT
TB_NO_TOOLTIPS = _controls_.TB_NO_TOOLTIPS
+TB_BOTTOM = _controls_.TB_BOTTOM
class ToolBarToolBase(_core.Object):
"""Proxy of C++ ToolBarToolBase class"""
thisown = property(lambda x: x.this.own(), lambda x, v: x.this.own(v), doc='The membership flag')
SWIG_Python_SetConstant(d, "TB_HORZ_LAYOUT",SWIG_From_int(static_cast< int >(wxTB_HORZ_LAYOUT)));
SWIG_Python_SetConstant(d, "TB_HORZ_TEXT",SWIG_From_int(static_cast< int >(wxTB_HORZ_TEXT)));
SWIG_Python_SetConstant(d, "TB_NO_TOOLTIPS",SWIG_From_int(static_cast< int >(wxTB_NO_TOOLTIPS)));
+ SWIG_Python_SetConstant(d, "TB_BOTTOM",SWIG_From_int(static_cast< int >(wxTB_BOTTOM)));
SWIG_addvarlink(SWIG_globals(),(char*)"ListCtrlNameStr",ListCtrlNameStr_get, ListCtrlNameStr_set);
SWIG_Python_SetConstant(d, "LC_VRULES",SWIG_From_int(static_cast< int >(wxLC_VRULES)));
SWIG_Python_SetConstant(d, "LC_HRULES",SWIG_From_int(static_cast< int >(wxLC_HRULES)));
`wx.Bitmap`) and then copied to the screen only once, when this object
is destroyed.
- It can be used in the same way as any other device
- context. wx.BufferedDC itself typically replaces `wx.ClientDC`, if you
- want to use it in your EVT_PAINT handler, you should look at
+ It can be used in the same way as any other device context.
+ wx.BufferedDC itself typically replaces `wx.ClientDC`, if you want to
+ use it in your EVT_PAINT handler, you should look at
`wx.BufferedPaintDC`.
+ Please note that GTK+ 2.0 and OS X provide double buffering themselves
+ natively so using this class on those platforms will normally result
+ in an unneeded level of buffering.
+
"""
thisown = property(lambda x: x.this.own(), lambda x, v: x.this.own(v), doc='The membership flag')
__repr__ = _swig_repr
TB_HORZ_LAYOUT = _controls_.TB_HORZ_LAYOUT
TB_HORZ_TEXT = _controls_.TB_HORZ_TEXT
TB_NO_TOOLTIPS = _controls_.TB_NO_TOOLTIPS
+TB_BOTTOM = _controls_.TB_BOTTOM
class ToolBarToolBase(_core.Object):
"""Proxy of C++ ToolBarToolBase class"""
thisown = property(lambda x: x.this.own(), lambda x, v: x.this.own(v), doc='The membership flag')
}
SWIGINTERN wxWindow *wxPyListCtrl_GetMainWindow(wxPyListCtrl *self){
+ return self;
+
- return (wxWindow*)self->m_mainWin;
-
}
#include <wx/treectrl.h>
SWIG_Python_SetConstant(d, "TB_HORZ_LAYOUT",SWIG_From_int(static_cast< int >(wxTB_HORZ_LAYOUT)));
SWIG_Python_SetConstant(d, "TB_HORZ_TEXT",SWIG_From_int(static_cast< int >(wxTB_HORZ_TEXT)));
SWIG_Python_SetConstant(d, "TB_NO_TOOLTIPS",SWIG_From_int(static_cast< int >(wxTB_NO_TOOLTIPS)));
+ SWIG_Python_SetConstant(d, "TB_BOTTOM",SWIG_From_int(static_cast< int >(wxTB_BOTTOM)));
SWIG_addvarlink(SWIG_globals(),(char*)"ListCtrlNameStr",ListCtrlNameStr_get, ListCtrlNameStr_set);
SWIG_Python_SetConstant(d, "LC_VRULES",SWIG_From_int(static_cast< int >(wxLC_VRULES)));
SWIG_Python_SetConstant(d, "LC_HRULES",SWIG_From_int(static_cast< int >(wxLC_HRULES)));
`wx.Bitmap`) and then copied to the screen only once, when this object
is destroyed.
- It can be used in the same way as any other device
- context. wx.BufferedDC itself typically replaces `wx.ClientDC`, if you
- want to use it in your EVT_PAINT handler, you should look at
+ It can be used in the same way as any other device context.
+ wx.BufferedDC itself typically replaces `wx.ClientDC`, if you want to
+ use it in your EVT_PAINT handler, you should look at
`wx.BufferedPaintDC`.
+ Please note that GTK+ 2.0 and OS X provide double buffering themselves
+ natively so using this class on those platforms will normally result
+ in an unneeded level of buffering.
+
"""
thisown = property(lambda x: x.this.own(), lambda x, v: x.this.own(v), doc='The membership flag')
__repr__ = _swig_repr
TB_HORZ_LAYOUT = _controls_.TB_HORZ_LAYOUT
TB_HORZ_TEXT = _controls_.TB_HORZ_TEXT
TB_NO_TOOLTIPS = _controls_.TB_NO_TOOLTIPS
+TB_BOTTOM = _controls_.TB_BOTTOM
class ToolBarToolBase(_core.Object):
"""Proxy of C++ ToolBarToolBase class"""
thisown = property(lambda x: x.this.own(), lambda x, v: x.this.own(v), doc='The membership flag')
SWIG_Python_SetConstant(d, "TB_HORZ_LAYOUT",SWIG_From_int(static_cast< int >(wxTB_HORZ_LAYOUT)));
SWIG_Python_SetConstant(d, "TB_HORZ_TEXT",SWIG_From_int(static_cast< int >(wxTB_HORZ_TEXT)));
SWIG_Python_SetConstant(d, "TB_NO_TOOLTIPS",SWIG_From_int(static_cast< int >(wxTB_NO_TOOLTIPS)));
+ SWIG_Python_SetConstant(d, "TB_BOTTOM",SWIG_From_int(static_cast< int >(wxTB_BOTTOM)));
SWIG_addvarlink(SWIG_globals(),(char*)"ListCtrlNameStr",ListCtrlNameStr_get, ListCtrlNameStr_set);
SWIG_Python_SetConstant(d, "LC_VRULES",SWIG_From_int(static_cast< int >(wxLC_VRULES)));
SWIG_Python_SetConstant(d, "LC_HRULES",SWIG_From_int(static_cast< int >(wxLC_HRULES)));
`wx.Bitmap`) and then copied to the screen only once, when this object
is destroyed.
- It can be used in the same way as any other device
- context. wx.BufferedDC itself typically replaces `wx.ClientDC`, if you
- want to use it in your EVT_PAINT handler, you should look at
+ It can be used in the same way as any other device context.
+ wx.BufferedDC itself typically replaces `wx.ClientDC`, if you want to
+ use it in your EVT_PAINT handler, you should look at
`wx.BufferedPaintDC`.
+ Please note that GTK+ 2.0 and OS X provide double buffering themselves
+ natively so using this class on those platforms will normally result
+ in an unneeded level of buffering.
+
"""
thisown = property(lambda x: x.this.own(), lambda x, v: x.this.own(v), doc='The membership flag')
__repr__ = _swig_repr