Displaying 4 results from an estimated 4 matches for "wxart_information".
Did you mean:
art_information
2006 Sep 13
2
RubyConstants.i.patch
This patch fixes up two problems with ArtProvider constants and fixes a
small typo.
Roy
_______________________________________________
wxruby-users mailing list
wxruby-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/wxruby-users
2006 Apr 17
4
Quick status report
...onight, and I think I''m close to having a
wxruby2 build that works with wxWidgets 2.6.3 and SWIG 1.3.29. It should
run bigdemo as well as the other samples. Unfortunately, I probably
won''t have much time to work on it until next weekend :-(
Tonight''s frustration was with wxART_INFORMATION. It''s sort of a wxArtID
and sort of a wxString. I finally(!) got the generated C++ code to look
pretty good, but it segfaults deep within the wx code. So for now I plan
to disable wxArtProvider#get_icon and #get_bitmap, and comment those
calls out in the controls.rb sample.
One other quir...
2006 Sep 14
2
Patch to fix ArtProvider and ArtProvider sample
These patches better implement ArtProvider and add the demo for it. I
also expanded the bigdemo window a little bit. I really think we should
go larger but I suppose there might be some people at 800x600 still.
Note that creating your own art provider still doesn''t quite work
correctly. I didn''t have time to get into that.
The RubyConstants.i.patch file looks weird. Not
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...