Displaying 20 results from an estimated 1000 matches similar to: "wxruby-swig problem: MDIChildFrame::Maximize"
2004 Apr 27
15
Building wxruby on Solaris 9
Hi all,
Ruby 1.8.1
Solaris 9
wxwindows 2.4.2 (package from blastwave.org)
wxruby 0.3.0
I''m having trouble getting this sucker to build on my Solaris box.
Here''s how I''m building:
ruby extconf.rb --with-xrc-dir=/opt/csw
--with-xrc-include=/opt/csw/lib/wx
The include directive I added because the setup.h file is there (for
whatever reason). And yes, /opt/csw/bin and
2005 Jul 30
7
Can''t compile the cvs-tree
Hi folks,
Let me start off by saying I''ve just been following wxruby development
for two or three days now and have read up on alot on what has been
going on. I must say I''m impressed and happy about all the things being
developed and created by you guys! You got me all excited and I know I''m
not the only one. If I have an opportunity to spend more time
investigating
2006 Oct 15
2
[Fwd: [ wxruby-Bugs-6144 ] error: cast from ‘void*’ to ‘int’ loses precision]
I think we can mark this bug closed and check in the patch. Anyone have
any concerns/questions before I do?
Roy
-------- Original Message --------
Subject: [ wxruby-Bugs-6144 ] error: cast from ?void*? to ?int? loses
precision
Date: Sun, 15 Oct 2006 08:37:31 -0400 (EDT)
From: <noreply at rubyforge.org>
To: noreply at rubyforge.org
Bugs item #6144, was opened at 2006-10-15 00:04
2005 Aug 18
3
wxDebug
For debug builds we define __WXDEBUG__ and WXDEBUG=1. In the swig code
we add a check for wxDEBUG to directors. My guess is we mean for one of
those defines to be the other. Which one should we change? wxDEBUG->
WXDEBUG or WXDEBUG-> wxDebug?
Roy
2004 Jun 25
4
wxruby 0.4.0 won''t compile [linux]
Has anyone run across this:
/usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.2/../../../../i686-pc-linux-gnu/bin/ld: wxruby.so: undefined versioned symbol name wxBitmapButtonBase::SetMargins(int, int)@@WXGTK2_2.4
/usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.2/../../../../i686-pc-linux-gnu/bin/ld: failed to set dynamic section sizes: Bad value
collect2: ld returned 1 exit status
make: *** [wxruby.so] Error 1
rm
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
2009 Oct 30
2
wxRuby on Ubuntu 9.10
Installing the gem from rubygems, along with the available wxwidgets
packages from synaptic, I'd recieve this error:
/usr/lib/ruby/gems/1.8/gems/wxruby-2.0.1-x86-linux/lib/wxruby2.so:
/usr/lib/ruby/gems/1.8/gems/wxruby-2.0.1-x86-linux/lib/wxruby2.so:
symbol _ZN13wxAuiNotebook14ShowWindowMenuEv, version WXU_2.8.5 not
defined in file libwx_gtk2u_aui-2.8.so.0 with link time reference -
2004 Feb 10
1
MDI
Hello,
I want to use wxruby in my application, but this should be MDI application.
Kevin, could you add MDIParentFrame, MDIClientWindow and MDIChildFrame
in wxruby-0.3, please?
--
Best regards,
Pavel
mailto:papushev@inp.nsk.su
2006 Aug 10
3
update on samples
Hi all
Have been taking a look at the samples to see what''s broken. Not looking
TOO bad overall, but a few problems we should try and tackle before alpha:
Firstly, I have a few commits (minimal, dialogs, unicode) - anyone else
been working on these or can I go ahead?
One general issue is that many of the samples rely on being run from
their own directory, but don''t enforce
2004 Aug 26
18
wxRuby 0.5.0 has been released!
wxRuby 0.5.0 has been released and is now available for
download from RubyForge at http://wxruby.rubyforge.org/
This release includes binary builds for Max OS X and
MS Windows.
Please report any bugs or feature requests here:
http://rubyforge.org/tracker/?group_id=35
Changes in this release include:
* Added XRC (Xml Resource File) support.
* Added totally awesome HTML widget from Tobi
2009 Nov 05
17
installing wxruby 2.0.1. missing lwx_gtk2u_media-2.8
Hi,
i tried too install wxruby-2.0.1 on opensuse 11.2 from the rake command
I get the following error:
...
usr/lib/gcc/i586-suse-linux/4.4/../../../../i586-suse-linux/bin/ld:
cannot find -lwx_gtk2u_media-2.8
collect2: ld returned 1 exit status
rake aborted!
Command failed with status (1): [g++ -shared -fPIC -o -L. -rdynamic
-Wl,-...]
/usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:995:in
2004 May 22
4
couple of questions
Hi folks
A couple of questions:
1) I seem to get funny artifacts in the display of TreeCtrl, ComboBox
and ListBox when the MDI child frame containing it is first painted (see
attached - it should be two-root treeview, unopened). I''m not sure if
it''s related to being in a MDI, but the controls sample looks OK. The
artifacts are cleared up when it''s repainted or
2007 Dec 27
4
build problems, part III, and runtime problems, part I
After decoding the unresolved symbols from wxruby2.so using c++filt, and
comparing with the symbols provided by wxGTK, it became clear that wxGTK was
using wchar_t whereas wxruby2.so was using char. So I rebuilt wxGTK,
turning off unicode. That worked. No more unresolved symbols. What
gives? Should the wxruby code have been built using wchar_t, and if so,
how?
However, now I get the
2004 Aug 05
2
libraries needed to distribute app
Hi
I''m making an installer for my WxRuby app, using exerb. I''ve included
wxruby.so in the package, and it seems to work fine on my computer, but
are there any other dlls or whatever I''m likely to need, for example for
WxWidgets itself?
Cheers
alex
2008 Feb 17
15
A bug in wxRuby. Segmentation fault in random situations.
Hello,
I wrote an application in wxRuby:
ruby 1.8.6
wxruby 1.9.4 installed from gem
windows xp sp2
After several minutes of running it crashes with the following error:
"c:/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27: [BUG]
Segmentation fault
ruby 1.8.6 (2007-03-13) [i386-mswin32]
This application has requested the Runtime to terminate it in an unusual way.
Please contact
2007 Feb 12
0
[858] trunk/wxruby2/doc/textile/docmdichildframe.txtl: Added ''methods'' section; removed C++ members
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head><meta http-equiv="content-type" content="text/html; charset=utf-8" /><style type="text/css"><!--
#msg dl { border: 1px #006 solid; background: #369; padding:
2007 Oct 17
19
1.9.2, OpenGL
[third sending attempt...]
I''m going to try and test out the samples on MSW over the next few days
and if things look good I think we should release 1.9.2. Might try and
fix the bugs related to TreeCtrl#get_first_child as these might involve
minor API changes. So if anyone has any time to test out SVN HEAD and
look for anything funny, please do.
Also, we have an anonymous patch
2009 Jan 24
37
Problem running Samples
Hi. I''m desperately trying to learn Ruby and wxWidgets, on my 64-bit
Linux machine. However when I try to run any of the samples from the
command line I get the following error message:
ruby: symbol lookup error:
/usr/lib/ruby/gems/1.8/gems/wxruby-1.9.8-x86_64-linux/lib/wxruby2.so:
undefined symbol: Init_wxMediaCtrl
I''d be very grateful for any help. Many thanks in advance!
--
2010 Jan 28
5
Compiling problem on Ubuntu 9.10 64 bit
Hello,
I''m trying to compile wxruby for Ruby 1.9 on Ubuntu Karmic 64 bit, but I
can''t get it to work. I''ve already done this for the 32 bit version (on
another machine, of course), so I don''t see where''s the problem with
that. I thought, I had all neccessary libraries installed, but maybe you
know better... After compiling for a long time, rake fails
2006 Oct 21
0
[698] trunk/wxruby2/samples/bigdemo/MDIDemo.rbw: Removed broken background stuff to stop crash on OS X (tho still crashes
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head><meta http-equiv="content-type" content="text/html; charset=utf-8" /><style type="text/css"><!--
#msg dl { border: 1px #006 solid; background: #369; padding: