Displaying 3 results from an estimated 3 matches for "wxlogerror".
Did you mean:
logerror
2005 Aug 02
1
Latest tarball
...ng'' : cannot convert
parameter 1 from ''const class wxWCharBuffer'' to ''const char *''
No user-defined-conversion operator available that can perform
this conversion, or the operator cannot be called
src/Functions.cpp(614) : error C2664: ''wxLogError'' : cannot convert
parameter 1 from ''const class wxWCharBuffer'' to ''const char *''
No user-defined-conversion operator available that can perform
this conversion, or the operator cannot be called
Exception `RuntimeError'' at
c:/ruby/lib/...
2007 Jan 23
0
[853] trunk/wxruby2/swig: Replace deprecated STR2CSTR with StringValuePtr
...s="lines">@@ -57,7 +57,7 @@
</span><span class="cx"> log_error(int argc, VALUE *argv, VALUE self)
</span><span class="cx"> {
</span><span class="cx"> VALUE str = rb_f_sprintf(argc, argv);
</span><del>- wxLogError(wxString(STR2CSTR(str), wxConvUTF8));
</del><ins>+ wxLogError(wxString(StringValuePtr(str), wxConvUTF8));
</ins><span class="cx"> }
</span><span class="cx">
</span><span class="cx">
</span><span class="...
2005 Aug 04
9
wxruby2 retooling
I finally gave up on swig 1.3.22, since it seems to be causing too many
problems. Ubuntu breezy will have 1.3.24, so I''m retargeting wxruby2 to
swig 1.3.24+. At the moment, I have 1.3.25 on my system, since that''s
the current release.
I''m finding all kinds of problems with the post-processors we have that
clean up the .cpp files that swig creates. The