search for: wxdirection

Displaying 4 results from an estimated 4 matches for "wxdirection".

Did you mean: direction
2008 Mar 04
1
enum arguments not recognized
...I was able to fix, but I''m not sure if this is the right way to handle it, being new to swig and all. Basically, in wxDC.h, there''s a function declaration: void GradientFillLinear(const wxRect& rect, const wxColour& initialColour, const wxColour& destColour, wxDirection nDirection = wxEAST); The problem is that since swig does not see the definition of the enum wxDirection (defined in RubyConstants.i), it treats it as an unknown class. Attempting to call the generated method from Ruby while specifying the nDirection argument then becomes impossible. My...
2007 Mar 19
0
[900] branches/wxruby2/wxwidgets_282/swig/classes: Initial commit of AUI core classes
...t wxPoint& action_offset = wxPoint(0,0)); + + wxAuiDockUIPart* HitTest(int x, int y); + wxAuiDockUIPart* GetPanePart(wxWindow* pane); + int GetDockPixelOffset(wxAuiPaneInfo& test); + void OnFloatingPaneMoveStart(wxWindow* window); + void OnFloatingPaneMoving(wxWindow* window, wxDirection dir ); + void OnFloatingPaneMoved(wxWindow* window, wxDirection dir); + void OnFloatingPaneActivated(wxWindow* window); + void OnFloatingPaneClosed(wxWindow* window, wxCloseEvent& evt); + void OnFloatingPaneResized(wxWindow* window, const wxSize& size); + void Render(wxDC* dc...
2007 Mar 27
0
[922] branches/wxruby2/wxwidgets_282: Changes, additions and deprecations 2.6 -> 2.8 Wx API
...xColour& destColour); + void GradientFillConcentric(const wxRect& rect, const wxColour& initialColour, const wxColour& destColour, const wxPoint& circleCenter); + void GradientFillLinear(const wxRect& rect, const wxColour& initialColour, const wxColour& destColour, wxDirection nDirection = wxEAST); </ins><span class="cx"> wxCoord LogicalToDeviceX(wxCoord x ) ; </span><span class="cx"> wxCoord LogicalToDeviceXRel(wxCoord x ) ; </span><span class="cx"> wxCoord LogicalToDeviceY(wxCoord y ) ; </spa...
2005 May 03
10
Is wxRuby-SWIG version usable enough to package for download?
If wxRuby-SWIG is as usable as wxRuby 0.6.0, maybe it should be given a version number and packaged up for download. Given the nature of SWIG, having a lot more people use it would probably result in more code contributions to this project. Seems most of the changes are 2+ months old, so I''m guessing wxRuby-SWIG is fairly stable right now in terms of frequency of changes...