From lists at ruby-forum.com Tue Mar 1 03:31:31 2011 From: lists at ruby-forum.com (Chase Wilson) Date: Tue, 01 Mar 2011 09:31:31 +0100 Subject: [wxruby-users] Waiting for user input without dialog Message-ID: <75b7da1b4141a9a3d9727753dc97ae49@ruby-forum.com> I'm trying to make a wxruby dialog that will always be visible to the user, but occasionally require user input before continuing on. However, I'm having trouble trying to figure out how I can wait around for user input. In a dialog wx::ruby does the waiting for you, but if it's not a dialog I don't know how to do it. I tried running the dialog in a separate thread, and when I need to wait for user input just have the main thread loop until it receives a response, but the timer I have that calls Thread.pass stops running when the while loop goes. Additionally during the loop the program windows stop responding. Anyone have any solutions? Is there a way to make a Frame or Window in general to behave like a dialog for a period of time? -- Posted via http://www.ruby-forum.com/. From sebastien.bureaux at dbmail.com Tue Mar 1 14:46:44 2011 From: sebastien.bureaux at dbmail.com (=?utf-8?Q?S=C3=A9bastien?=) Date: Tue, 1 Mar 2011 20:46:44 +0100 (CET) Subject: [wxruby-users] KeyEvent#get_key_code Message-ID: <7180230.2597291299008804058.JavaMail.www@wwumf0208> Bonsoir Alex, en utilisant "event.get_key_code" avec les touches du pav? num?rique(clavier azerty) j'obtient les r?sultats suivants: par exemple: 1 = 324 2 = 325 3 = 326 Est-ce que j'obtient les m?mes r?sultats avec les m?mes touches avec un clavier querty? merci. -------------- section suivante -------------- Une pi?ce jointe HTML a ?t? nettoy?e... URL: From sebastien.bureaux at dbmail.com Wed Mar 2 16:14:29 2011 From: sebastien.bureaux at dbmail.com (=?utf-8?Q?S=C3=A9bastien?=) Date: Wed, 2 Mar 2011 22:14:29 +0100 (CET) Subject: [wxruby-users] evt_key_down() { | event | ... } Message-ID: <20028955.4774471299100469961.JavaMail.www@wwumf0210.worldlinemail.net> Bonsoir Alex. J'ai un probl?me avec "evt_key_down() { | event | ... }". Je m'explique: Quand j'ouvre mon application, "evt_key_down() { | event | ... }" fonctionne correctement, mais ? partir du moment que je fait un clique avec la souris sur TextCtrl par exemple, "evt_key_down() { | event | ... }" ce d?sactive et ne fonctionne plus. Que faut-il que je fasse pour que "evt_key_down() { | event | ... }" reste activ?? merci. -------------- section suivante -------------- Une pi?ce jointe HTML a ?t? nettoy?e... URL: From mario at ruby-im.net Wed Mar 2 19:09:27 2011 From: mario at ruby-im.net (Mario Steele) Date: Wed, 2 Mar 2011 19:09:27 -0500 Subject: [wxruby-users] evt_key_down() { | event | ... } In-Reply-To: <20028955.4774471299100469961.JavaMail.www@wwumf0210.worldlinemail.net> References: <20028955.4774471299100469961.JavaMail.www@wwumf0210.worldlinemail.net> Message-ID: Bonjour S?bastien, Le probl?me que vous rencontrez, est d? au fait que evt_key_down () {| ?v?nement | ...} est li? ? l'instance que votre question lorsque vous l'invoquez. En d'autres termes, evt_key_down () est fix? en fonction de votre fen?tre / cadre, pas le TextCtrl. Le TextCtrl a son propre syst?me de touche de gestion, qui est contr?l?e en interne par la biblioth?que wxWidgets. Afin de saisir le texte entr? dans un TextCtrl, vous devez utiliser evt_text () {| ?v?nement | ...} afin de capturer le texte saisi dans un TextCtrl. Si vous voulez capturer des ?v?nements Tab ainsi, vous devrez ajouter le Wx:: drapeau TE_PROCESS_TAB ? la cr?ation de votre TextCtrl. M?me avec le traitement d'un retour, vous devez utiliser Wx:: TE_PROCESS_ENTER pour capturer le retour aussi.Mais pour le traitement de Wx:: TE_PROCESS_ENTER, vous devez utiliser la evt_text_enter () {| ?v?nement | ...} pour le processus. (( Hello Sebastian, The problem you are having, is due to the fact that evt_key_down() {|event| ...} is bound to the instance that your dealing with when you invoke it. In other words, evt_key_down() is being set on your Window / Frame, not the TextCtrl. The TextCtrl has it's own Key Handling system, that is controlled internally by the wxWidgets library. In order to capture text entered in a TextCtrl, you need to use evt_text() {|event| ...} in order to capture text entered in a TextCtrl. If you want to capture Tab Events as well, you will need to add the Wx::TE_PROCESS_TAB flag to the creation of your TextCtrl. Same with processing a Return, you need to use Wx::TE_PROCESS_ENTER to capture the return as well. But for processing Wx::TE_PROCESS_ENTER, you need to use the evt_text_enter() {|event| ...} to process it. hth, Mario )) 2011/3/2 S?bastien > > Bonsoir Alex. > J'ai un probl?me avec "evt_key_down() { | event | ... }". > Je m'explique: > Quand j'ouvre mon application, "evt_key_down() { | event | ... }" fonctionne correctement, mais ? partir du moment que je fait un clique avec la souris sur TextCtrl par exemple, "evt_key_down() { | event | ... }" ce d?sactive et ne fonctionne plus. > Que faut-il que je fasse pour que "evt_key_down() { | event | ... }" reste activ?? > merci. > > _______________________________________________ > wxruby-users mailing list > wxruby-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users (( Good evening Alex. I have a problem with "evt_key_down () {| event | ...}". Let me explain: When I open my application, "evt_key_down () {| event | ...}" works fine, but from the time I made a mouse click on TextCtrl for example, "evt_key_down () {| event |. ..} "this off and no longer works. What should I do to that "evt_key_down () {| event | ...}" is enabled? thank you. )) -- Mario Steele Lieutenant Commander 3 XO - Geo 99 XO - STO IFT Fleet http://www.trekfederation.com http://geo99.ruby-im.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From sebastien.bureaux at dbmail.com Thu Mar 3 03:14:00 2011 From: sebastien.bureaux at dbmail.com (=?utf-8?Q?S=C3=A9bastien?=) Date: Thu, 3 Mar 2011 09:14:00 +0100 (CET) Subject: [wxruby-users] evt_key_down() { | event | ... } Message-ID: <8138817.28081299140040132.JavaMail.www@wwumf0206> Bonjour Mario Voici le code que j'utilise: evt_key_down :evenement_clavier ...... def CreationTexteCtrl ??? @calcul = TextCtrl.new(@l, -1, "", Point.new(10, 10), Size.new(397, 30), TE_RICH|TE_READONLY) ??? @calcul.set_font(Font.new(14, SWISS, NORMAL, BOLD)) ??? @calcul.set_size(@calcul.get_best_size) ?end ...... def evenement_clavier(event) ??? code_cle = event.get_key_code ??? case code_cle.to_i ??? when 324 ????? onChiffre0 ??? when 325 ????? onChiffre1 ??? when 326 ????? onChiffre2 ??? when 327 ????? onChiffre3 ??? when 328 ????? onChiffre4 ??? when 329 ????? onChiffre5 ??? when 330 ????? onChiffre6 ??? when 331 ????? onChiffre7 ??? when 332 ????? onChiffre8 ??? when 333 ????? onChiffre9 ??? when 391 ????? onPoint ??? when 392 ????? onDivi ??? when 387 ????? onMulti ??? when 390 ????? onMoins ??? when 388 ????? onPlus ??? when 370 ????? onEgal ??? when 13 ????? onEgal ? end ????? event.skip end def onChiffre0 ??? @calcul << 0 ? end end ...... J'ai essayer avec "TE_PROCESS_TAB" et "TE_PROCESS_ENTER": "@calcul = TextCtrl.new(@l, -1, "", Point.new(10, 10), Size.new(397, 30), TE_RICH|TE_READONLY|TE_PROCESS_TAB|TE_PROCESS_ENTER" mais j'ai toujours le m?me probl?me. Par contre je pr?cise que j'utilise "TE_READONLY" avec le "TextCtrl" En fait j'aimerais pouvoir r?cup?rer que certains caract?res grace ? l'aide de "evt_key_down() { | event | ... }" et de pouvoir les affich?es par la suite dans le TextCtrl. ----------------------------------------------------------------------------------------------------------------- >Le probl?me que vous rencontrez, est d? au fait que evt_key_down () {| >?v?nement | ...} est li? ? l'instance que votre question lorsque vous >l'invoquez. En d'autres termes, evt_key_down () est fix? en fonction de >votre fen?tre / cadre, pas le TextCtrl. Le TextCtrl a son propre syst?me de >touche de gestion, qui est contr?l?e en interne par la biblioth?que >wxWidgets. Afin de saisir le texte entr? dans un TextCtrl, vous devez >utiliser evt_text () {| ?v?nement | ...} afin de capturer le texte saisi >dans un TextCtrl. Si vous voulez capturer des ?v?nements Tab ainsi, vous >devrez ajouter le Wx:: drapeau TE_PROCESS_TAB ? la cr?ation de votre >TextCtrl. M?me avec le traitement d'un retour, vous devez utiliser Wx:: >TE_PROCESS_ENTER pour capturer le retour aussi.Mais pour le traitement de >Wx:: TE_PROCESS_ENTER, vous devez utiliser la evt_text_enter () {| ?v?nement >| ...} pour le processus. -------------- section suivante -------------- Une pi?ce jointe HTML a ?t? nettoy?e... URL: From lists at ruby-forum.com Fri Mar 4 01:18:57 2011 From: lists at ruby-forum.com (Galymzhan K.) Date: Fri, 04 Mar 2011 07:18:57 +0100 Subject: [wxruby-users] wxRuby global hotkeys Message-ID: <1eb8ee5f2bfb37f3338b442406c9750f@ruby-forum.com> Is it possible to assign global hotkeys in wxRuby, I want to show window when user presses key combination? I've found that there is a Window#register_hot_key method - is this method cross-platform? -- Posted via http://www.ruby-forum.com/. From sutniuq at gmx.net Wed Mar 9 10:38:05 2011 From: sutniuq at gmx.net (Quintus) Date: Wed, 09 Mar 2011 16:38:05 +0100 Subject: [wxruby-users] Packaging wxRuby fails Message-ID: <4D779EDD.4090806@gmx.net> Hi there, I (once again) just compiled wxRuby 2.0.1 successfully, but I can't get "rake gem" to work: =========================================== $ rake gem (in /home/quintus/Downloads/wxruby-2.0.1) Enabling DYNAMIC build Enabling RELEASE build Enabling UNICODE build The following wxWidgets features are not available and will be skipped: PrinterDC rake aborted! undefined method `write' for # /opt/rubies/ruby-1.9.2-p180/lib/ruby/1.9.1/psych/visitors/emitter.rb:17:in `end_document' /opt/rubies/ruby-1.9.2-p180/lib/ruby/1.9.1/psych/visitors/emitter.rb:17:in `visit_Psych_Nodes_Document' /opt/rubies/ruby-1.9.2-p180/lib/ruby/1.9.1/psych/visitors/visitor.rb:10:in `accept' /opt/rubies/ruby-1.9.2-p180/lib/ruby/1.9.1/psych/visitors/emitter.rb:10:in `block in visit_Psych_Nodes_Stream' /opt/rubies/ruby-1.9.2-p180/lib/ruby/1.9.1/psych/visitors/emitter.rb:10:in `each' /opt/rubies/ruby-1.9.2-p180/lib/ruby/1.9.1/psych/visitors/emitter.rb:10:in `visit_Psych_Nodes_Stream' /opt/rubies/ruby-1.9.2-p180/lib/ruby/1.9.1/psych/visitors/visitor.rb:11:in `accept' /opt/rubies/ruby-1.9.2-p180/lib/ruby/1.9.1/psych/nodes/node.rb:36:in `to_yaml' /opt/rubies/ruby-1.9.2-p180/lib/ruby/1.9.1/psych.rb:166:in `dump' /opt/rubies/ruby-1.9.2-p180/lib/ruby/1.9.1/psych/core_ext.rb:13:in `psych_to_yaml' /opt/rubies/ruby-1.9.2-p180/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:715:in `node_export' /opt/rubies/ruby-1.9.2-p180/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:715:in `add' /opt/rubies/ruby-1.9.2-p180/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:715:in `encode_with' /opt/rubies/ruby-1.9.2-p180/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:737:in `block (2 levels) in to_yaml' /opt/rubies/ruby-1.9.2-p180/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:736:in `map' /opt/rubies/ruby-1.9.2-p180/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:736:in `block in to_yaml' /opt/rubies/ruby-1.9.2-p180/lib/ruby/1.9.1/syck.rb:401:in `call' /opt/rubies/ruby-1.9.2-p180/lib/ruby/1.9.1/syck.rb:401:in `emit' /opt/rubies/ruby-1.9.2-p180/lib/ruby/1.9.1/syck.rb:401:in `quick_emit' /opt/rubies/ruby-1.9.2-p180/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:735:in `to_yaml' /opt/rubies/ruby-1.9.2-p180/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:78:in `block (2 levels) in write_package' /opt/rubies/ruby-1.9.2-p180/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:73:in `block (3 levels) in add_gem_contents' /opt/rubies/ruby-1.9.2-p180/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_writer.rb:83:in `new' /opt/rubies/ruby-1.9.2-p180/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:67:in `block (2 levels) in add_gem_contents' /opt/rubies/ruby-1.9.2-p180/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:65:in `wrap' /opt/rubies/ruby-1.9.2-p180/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:65:in `block in add_gem_contents' /opt/rubies/ruby-1.9.2-p180/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_writer.rb:113:in `add_file' /opt/rubies/ruby-1.9.2-p180/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:63:in `add_gem_contents' /opt/rubies/ruby-1.9.2-p180/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:31:in `open' /opt/rubies/ruby-1.9.2-p180/lib/ruby/site_ruby/1.9.1/rubygems/package.rb:68:in `open' /opt/rubies/ruby-1.9.2-p180/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:77:in `block in write_package' /opt/rubies/ruby-1.9.2-p180/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:76:in `open' /opt/rubies/ruby-1.9.2-p180/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:76:in `write_package' /opt/rubies/ruby-1.9.2-p180/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:39:in `build' /home/quintus/Downloads/wxruby-2.0.1/rake/rakepackage.rb:68:in `block in create_gem_tasks' /opt/rubies/ruby-1.9.2-p180/lib/ruby/1.9.1/rake.rb:634:in `call' /opt/rubies/ruby-1.9.2-p180/lib/ruby/1.9.1/rake.rb:634:in `block in execute' /opt/rubies/ruby-1.9.2-p180/lib/ruby/1.9.1/rake.rb:629:in `each' /opt/rubies/ruby-1.9.2-p180/lib/ruby/1.9.1/rake.rb:629:in `execute' /opt/rubies/ruby-1.9.2-p180/lib/ruby/1.9.1/rake.rb:595:in `block in invoke_with_call_chain' /opt/rubies/ruby-1.9.2-p180/lib/ruby/1.9.1/monitor.rb:201:in `mon_synchronize' /opt/rubies/ruby-1.9.2-p180/lib/ruby/1.9.1/rake.rb:588:in `invoke_with_call_chain' /opt/rubies/ruby-1.9.2-p180/lib/ruby/1.9.1/rake.rb:581:in `invoke' /opt/rubies/ruby-1.9.2-p180/lib/ruby/1.9.1/rake.rb:2041:in `invoke_task' /opt/rubies/ruby-1.9.2-p180/lib/ruby/1.9.1/rake.rb:2019:in `block (2 levels) in top_level' /opt/rubies/ruby-1.9.2-p180/lib/ruby/1.9.1/rake.rb:2019:in `each' /opt/rubies/ruby-1.9.2-p180/lib/ruby/1.9.1/rake.rb:2019:in `block in top_level' /opt/rubies/ruby-1.9.2-p180/lib/ruby/1.9.1/rake.rb:2058:in `standard_exception_handling' /opt/rubies/ruby-1.9.2-p180/lib/ruby/1.9.1/rake.rb:2013:in `top_level' /opt/rubies/ruby-1.9.2-p180/lib/ruby/1.9.1/rake.rb:1992:in `run' /opt/rubies/ruby-1.9.2-p180/bin/rake:31:in `
' =========================================== It seems the Rakefiles are mixing up Psych with Syck. What's happening here? And how do I get a gem file? Valete, Marvin From chauk.mean at gmail.com Sat Mar 12 17:07:38 2011 From: chauk.mean at gmail.com (Chauk-Mean Proum) Date: Sat, 12 Mar 2011 23:07:38 +0100 Subject: [wxruby-users] Packaging wxRuby fails In-Reply-To: <4D779EDD.4090806@gmx.net> References: <4D779EDD.4090806@gmx.net> Message-ID: Hi Marvin, 2011/3/9 Quintus : > Hi there, > > I (once again) just compiled wxRuby 2.0.1 successfully, but I can't get > "rake gem" to work: Are you on Ubuntu / Linux ? If so, may be the following page from the wiki will help : http://wxruby.rubyforge.org/wiki/wiki.pl?BuildingForUbuntu Cheers, Chauk-Mean From sutniuq at gmx.net Sun Mar 13 03:37:04 2011 From: sutniuq at gmx.net (Quintus) Date: Sun, 13 Mar 2011 08:37:04 +0100 Subject: [wxruby-users] Packaging wxRuby fails In-Reply-To: References: <4D779EDD.4090806@gmx.net> Message-ID: <4D7C7420.70107@gmx.net> Am 12.03.2011 23:07, schrieb Chauk-Mean Proum: > Hi Marvin, > > 2011/3/9 Quintus : >> Hi there, >> >> I (once again) just compiled wxRuby 2.0.1 successfully, but I can't get >> "rake gem" to work: > > Are you on Ubuntu / Linux ? > If so, may be the following page from the wiki will help : > http://wxruby.rubyforge.org/wiki/wiki.pl?BuildingForUbuntu > Nope, I'm running Arch Linux. And the actual *building* of wxRuby went well, I end up with wxruby2.so, but the command to build the gem, which doesn't do any compiling anymore but is just supposed to grab all necessary files and put them into the gem file, fails. "rake" (without arguments) works fine, but then "rake gem" fails. In the meantime I've solved the problem by buiding a second Ruby without Psych support--all went well and I got my gem, but sadly it segfaults. I suspect it's that incredible libcairo/libpixman error I've been expierencing so many times now, and if wxRuby hadn't been my favourite GUI toolkit for such a long time, I wouldn't hesitate to look for a new one. The minimal sample runs without problems, but any other more complex thing crashes. Here's the output of running bigdemo.rb: ===================================================================== $ ruby bigdemo.rb (wxruby:2222): Gtk-WARNING **: Error parsing gtk-icon-sizes string: 'panel-menu=24,24 panel=20,20 gtk-button=18,18 gtk-large-toolbar=24,24' bigdemo.rb:345: [BUG] Segmentation fault ruby 1.9.2p180 (2011-02-18 revision 30909) [x86_64-linux] -- control frame ---------- c:0010 p:---- s:0047 b:0047 l:000046 d:000046 CFUNC :set_active_target c:0009 p:1359 s:0043 b:0043 l:000c68 d:000c68 METHOD bigdemo.rb:345 c:0008 p:---- s:0024 b:0024 l:000023 d:000023 FINISH c:0007 p:---- s:0022 b:0022 l:000021 d:000021 CFUNC :new c:0006 p:0047 s:0016 b:0016 l:000015 d:000015 METHOD bigdemo.rb:814 c:0005 p:---- s:0012 b:0012 l:000011 d:000011 FINISH c:0004 p:---- s:0010 b:0010 l:000009 d:000009 CFUNC :main_loop c:0003 p:0300 s:0007 b:0007 l:000ba8 d:002360 EVAL bigdemo.rb:823 c:0002 p:---- s:0004 b:0004 l:000003 d:000003 FINISH c:0001 p:0000 s:0002 b:0002 l:000ba8 d:000ba8 TOP --------------------------- -- Ruby level backtrace information ---------------------------------------- bigdemo.rb:823:in `
' bigdemo.rb:823:in `main_loop' bigdemo.rb:814:in `on_init' bigdemo.rb:814:in `new' bigdemo.rb:345:in `initialize' bigdemo.rb:345:in `set_active_target' -- C level backtrace information ------------------------------------------- /opt/rubies/ruby-1.9.2-p180/lib/libruby.so.1.9(rb_vm_bugreport+0x5f) [0x7f199b9e135f] /opt/rubies/ruby-1.9.2-p180/lib/libruby.so.1.9(+0x62b04) [0x7f199b8c0b04] /opt/rubies/ruby-1.9.2-p180/lib/libruby.so.1.9(rb_bug+0xb3) [0x7f199b8c1a33] /opt/rubies/ruby-1.9.2-p180/lib/libruby.so.1.9(+0x116715) [0x7f199b974715] /lib/libpthread.so.0(+0xf150) [0x7f199b650150] /usr/lib/libpixman-1.so.0(pixman_image_composite32+0x400) [0x7f198f15a000] /usr/lib/libcairo.so.2(+0x3a31c) [0x7f1992bbc31c] /usr/lib/libcairo.so.2(+0x6480c) [0x7f1992be680c] /usr/lib/libcairo.so.2(+0x65cac) [0x7f1992be7cac] /usr/lib/libcairo.so.2(+0x4848b) [0x7f1992bca48b] /usr/lib/libcairo.so.2(+0x4b000) [0x7f1992bcd000] /usr/lib/libcairo.so.2(+0x4a123) [0x7f1992bcc123] /usr/lib/libcairo.so.2(+0x4ac02) [0x7f1992bccc02] /usr/lib/libcairo.so.2(+0x4b9d1) [0x7f1992bcd9d1] /usr/lib/libcairo.so.2(+0x48073) [0x7f1992bca073] /usr/lib/libcairo.so.2(+0x216ed) [0x7f1992ba36ed] /usr/lib/libcairo.so.2(cairo_fill_preserve+0x20) [0x7f1992b9a2e0] /usr/lib/libcairo.so.2(cairo_fill+0x9) [0x7f1992b9a2f9] /usr/lib/gtk-2.0/2.10.0/engines/libclearlooks.so(+0x14a5e) [0x7f198d472a5e] /usr/lib/gtk-2.0/2.10.0/engines/libclearlooks.so(+0x18fa9) [0x7f198d476fa9] /usr/lib/gtk-2.0/2.10.0/engines/libclearlooks.so(+0x947f) [0x7f198d46747f] /usr/lib/libgtk-x11-2.0.so.0(+0x8d01b) [0x7f1996dc401b] /usr/lib/libgtk-x11-2.0.so.0(+0x8d24f) [0x7f1996dc424f] /usr/lib/libgtk-x11-2.0.so.0(+0x1363a8) [0x7f1996e6d3a8] /usr/lib/libgobject-2.0.so.0(g_closure_invoke+0xa9) [0x7f1996844e09] /usr/lib/libgobject-2.0.so.0(+0x1f618) [0x7f1996856618] /usr/lib/libgobject-2.0.so.0(g_signal_emit_valist+0x625) [0x7f199685f9e5] /usr/lib/libgobject-2.0.so.0(g_signal_emit+0x83) [0x7f199685fe13] /usr/lib/libgtk-x11-2.0.so.0(+0x25181f) [0x7f1996f8881f] /usr/lib/libgtk-x11-2.0.so.0(gtk_container_propagate_expose+0x1c6) [0x7f1996defc96] /usr/lib/libgtk-x11-2.0.so.0(+0x8399b) [0x7f1996dba99b] /usr/lib/libgtk-x11-2.0.so.0(+0xb7804) [0x7f1996dee804] /usr/lib/libgtk-x11-2.0.so.0(+0x1363a8) [0x7f1996e6d3a8] /usr/lib/libgobject-2.0.so.0(g_closure_invoke+0xa9) [0x7f1996844e09] /usr/lib/libgobject-2.0.so.0(+0x1f618) [0x7f1996856618] /usr/lib/libgobject-2.0.so.0(g_signal_emit_valist+0x625) [0x7f199685f9e5] /usr/lib/libgobject-2.0.so.0(g_signal_emit+0x83) [0x7f199685fe13] /usr/lib/libgtk-x11-2.0.so.0(+0x25181f) [0x7f1996f8881f] /usr/lib/libgtk-x11-2.0.so.0(gtk_container_propagate_expose+0x1c6) [0x7f1996defc96] /usr/lib/libgtk-x11-2.0.so.0(+0x8399b) [0x7f1996dba99b] /usr/lib/libgtk-x11-2.0.so.0(+0xb7804) [0x7f1996dee804] /usr/lib/libgtk-x11-2.0.so.0(+0x1363a8) [0x7f1996e6d3a8] /usr/lib/libgobject-2.0.so.0(g_closure_invoke+0xa9) [0x7f1996844e09] /usr/lib/libgobject-2.0.so.0(+0x1f618) [0x7f1996856618] /usr/lib/libgobject-2.0.so.0(g_signal_emit_valist+0x625) [0x7f199685f9e5] /usr/lib/libgobject-2.0.so.0(g_signal_emit+0x83) [0x7f199685fe13] /usr/lib/libgtk-x11-2.0.so.0(+0x25181f) [0x7f1996f8881f] /usr/lib/libgtk-x11-2.0.so.0(gtk_container_propagate_expose+0x1c6) [0x7f1996defc96] /usr/lib/libgtk-x11-2.0.so.0(+0xb7804) [0x7f1996dee804] /usr/lib/libgtk-x11-2.0.so.0(+0x1363a8) [0x7f1996e6d3a8] /usr/lib/libgobject-2.0.so.0(g_closure_invoke+0x15e) [0x7f1996844ebe] /usr/lib/libgobject-2.0.so.0(+0x1f618) [0x7f1996856618] /usr/lib/libgobject-2.0.so.0(g_signal_emit_valist+0x625) [0x7f199685f9e5] /usr/lib/libgobject-2.0.so.0(g_signal_emit+0x83) [0x7f199685fe13] /usr/lib/libgtk-x11-2.0.so.0(+0x25181f) [0x7f1996f8881f] /usr/lib/libgtk-x11-2.0.so.0(gtk_main_do_event+0x58a) [0x7f1996e6bbca] /usr/lib/libgdk-x11-2.0.so.0(+0x42cf2) [0x7f1996ac8cf2] /usr/lib/libgdk-x11-2.0.so.0(+0x3dc1b) [0x7f1996ac3c1b] /usr/lib/libgdk-x11-2.0.so.0(gdk_window_process_all_updates+0x129) [0x7f1996ac5e39] /usr/lib/libgtk-x11-2.0.so.0(+0xb74b1) [0x7f1996dee4b1] /usr/lib/libgdk-x11-2.0.so.0(+0x1d366) [0x7f1996aa3366] /usr/lib/libglib-2.0.so.0(g_main_context_dispatch+0x1f3) [0x7f199628cbf3] /usr/lib/libglib-2.0.so.0(+0x423d0) [0x7f199628d3d0] /usr/lib/libglib-2.0.so.0(g_main_loop_run+0x182) [0x7f199628da42] /usr/lib/libgtk-x11-2.0.so.0(gtk_dialog_run+0x19b) [0x7f1996df174b] /usr/lib/libwx_gtk2u_core-2.8.so.0(_ZN15wxMessageDialog9ShowModalEv+0x4a) [0x7f1997e30bca] /usr/lib/libwx_gtk2u_core-2.8.so.0(_Z12wxMessageBoxRK8wxStringS1_lP8wxWindowii+0x4e) [0x7f1997dad02e] /usr/lib/libwx_gtk2u_core-2.8.so.0(_ZN8wxLogGui5FlushEv+0x279) [0x7f1997edabe9] /usr/lib/libwx_baseu-2.8.so.0(_ZN5wxLog15SetActiveTargetEPS_+0x27) [0x7f199792c867] /opt/rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/wxruby-ruby19-2.0.1-x86_64-linux/lib/wxruby2.so(+0x45ccb8) [0x7f1999b02cb8] /opt/rubies/ruby-1.9.2-p180/lib/libruby.so.1.9(+0x17d206) [0x7f199b9db206] /opt/rubies/ruby-1.9.2-p180/lib/libruby.so.1.9(+0x172d8e) [0x7f199b9d0d8e] /opt/rubies/ruby-1.9.2-p180/lib/libruby.so.1.9(+0x1791ab) [0x7f199b9d71ab] /opt/rubies/ruby-1.9.2-p180/lib/libruby.so.1.9(+0x17a488) [0x7f199b9d8488] /opt/rubies/ruby-1.9.2-p180/lib/libruby.so.1.9(rb_class_new_instance+0x30) [0x7f199b911b70] /opt/rubies/ruby-1.9.2-p180/lib/libruby.so.1.9(+0x17d206) [0x7f199b9db206] /opt/rubies/ruby-1.9.2-p180/lib/libruby.so.1.9(+0x172d8e) [0x7f199b9d0d8e] /opt/rubies/ruby-1.9.2-p180/lib/libruby.so.1.9(+0x1791ab) [0x7f199b9d71ab] /opt/rubies/ruby-1.9.2-p180/lib/libruby.so.1.9(+0x17a488) [0x7f199b9d8488] /opt/rubies/ruby-1.9.2-p180/lib/libruby.so.1.9(rb_funcall+0xba) [0x7f199b9d90ea] /opt/rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/wxruby-ruby19-2.0.1-x86_64-linux/lib/wxruby2.so(_ZN9wxRubyApp6OnInitEv+0x5c) [0x7f19998b808c] /usr/lib/libwx_baseu-2.8.so.0(_Z7wxEntryRiPPw+0x54) [0x7f1997920c64] /opt/rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/wxruby-ruby19-2.0.1-x86_64-linux/lib/wxruby2.so(+0x20f060) [0x7f19998b5060] /opt/rubies/ruby-1.9.2-p180/lib/libruby.so.1.9(+0x17d206) [0x7f199b9db206] /opt/rubies/ruby-1.9.2-p180/lib/libruby.so.1.9(+0x172d8e) [0x7f199b9d0d8e] /opt/rubies/ruby-1.9.2-p180/lib/libruby.so.1.9(+0x1791ab) [0x7f199b9d71ab] /opt/rubies/ruby-1.9.2-p180/lib/libruby.so.1.9(rb_iseq_eval_main+0xb1) [0x7f199b9dc6a1] /opt/rubies/ruby-1.9.2-p180/lib/libruby.so.1.9(+0x68eba) [0x7f199b8c6eba] /opt/rubies/ruby-1.9.2-p180/lib/libruby.so.1.9(ruby_exec_node+0x1d) [0x7f199b8c7e1d] /opt/rubies/ruby-1.9.2-p180/lib/libruby.so.1.9(ruby_run_node+0x1e) [0x7f199b8ca08e] ruby(main+0x4b) [0x40099b] /lib/libc.so.6(__libc_start_main+0xfd) [0x7f199aa38dcd] ruby() [0x400889] [NOTE] You may have encountered a bug in the Ruby interpreter or extension libraries. Bug reports are welcome. For details: http://www.ruby-lang.org/bugreport.html ===================================================================== This is my libpixman: ===================================================================== $ LANG=EN_US pacman -Qi pixman Name : pixman Version : 0.20.2-1 URL : http://xorg.freedesktop.org Licenses : custom Groups : None Provides : None Depends On : glibc Optional Deps : None Required By : cairo lib32-pixman xorg-server Conflicts With : None Replaces : None Installed Size : 528.00 K Packager : Jan de Groot Architecture : x86_64 Build Date : Wed Jan 19 15:45:12 2011 Install Date : Sat Jan 22 14:50:33 2011 Install Reason : Installed as a dependency for another package Install Script : No Description : Pixman library ===================================================================== Btw. this was the reason why I wanted to compile wxRuby myself. But appearently it didn't help. Vale, Marvin From lists at ruby-forum.com Tue Mar 15 19:06:17 2011 From: lists at ruby-forum.com (Zhimin Zhan) Date: Wed, 16 Mar 2011 00:06:17 +0100 Subject: [wxruby-users] wxStyledTextCtrl: how to set caret at begining of a selection? Message-ID: <43c27f5db7db89709dec611f1b34eba6@ruby-forum.com> Hi there, I was trying to select text backwards in a StyledTextCtrl, i.e, want the caret to be in the front, not at the end of selection, however unsucessful. My code like this: set_selection_end(11) set_selection_start(5) Any suggestions? thanks in advance. Zhimin -- Posted via http://www.ruby-forum.com/. From chauk.mean at gmail.com Wed Mar 16 16:56:57 2011 From: chauk.mean at gmail.com (Chauk-Mean Proum) Date: Wed, 16 Mar 2011 21:56:57 +0100 Subject: [wxruby-users] Packaging wxRuby fails In-Reply-To: <4D7C7420.70107@gmx.net> References: <4D779EDD.4090806@gmx.net> <4D7C7420.70107@gmx.net> Message-ID: Hi Marvin, 2011/3/13 Quintus : >> Are you on Ubuntu / Linux ? >> If so, may be the following page from the wiki will help : >> http://wxruby.rubyforge.org/wiki/wiki.pl?BuildingForUbuntu > > Nope, I'm running Arch Linux. And the actual *building* of wxRuby went > well, I end up with wxruby2.so, but the command to build the gem, which > doesn't do any compiling anymore but is just supposed to grab all > necessary files and put them into the gem file, fails. "rake" (without > arguments) works fine, but then "rake gem" fails. That's strange. What options did you use for building ruby-1.9.2-p180 ? Do you use the built-in rubygems or have you upgraded rubygems ? FWIW, you can also install wxRuby without creating the gem via : rake install. Cheers, Chauk-Mean. From sutniuq at gmx.net Wed Mar 16 17:45:59 2011 From: sutniuq at gmx.net (Quintus) Date: Wed, 16 Mar 2011 22:45:59 +0100 Subject: [wxruby-users] Packaging wxRuby fails In-Reply-To: References: <4D779EDD.4090806@gmx.net> <4D7C7420.70107@gmx.net> Message-ID: <4D812F97.8020005@gmx.net> Am 16.03.2011 21:56, schrieb Chauk-Mean Proum: > Hi Marvin, > > 2011/3/13 Quintus : >>> Are you on Ubuntu / Linux ? >>> If so, may be the following page from the wiki will help : >>> http://wxruby.rubyforge.org/wiki/wiki.pl?BuildingForUbuntu >> >> Nope, I'm running Arch Linux. And the actual *building* of wxRuby went >> well, I end up with wxruby2.so, but the command to build the gem, which >> doesn't do any compiling anymore but is just supposed to grab all >> necessary files and put them into the gem file, fails. "rake" (without >> arguments) works fine, but then "rake gem" fails. > > That's strange. > What options did you use for building ruby-1.9.2-p180 ? $ ./configure --prefix=/opt/rubies/ruby-1.9.2-p180 --enable-shared CFLAGS=-I/usr/src/linux-2.6.37-ARCH/include $ make $ sudo make install I have to provide the extra CFLAGS, because on Arch recently some header files in /usr/inclide/asm-generic/ disappeared and made Ruby fail to compile when it came to socket (which I need). The files are present in the bare kernel header directory, so I put that into CFLAGS. > Do you use the built-in rubygems or have you upgraded rubygems ? I upgraded via gem update --system. At the moment I'm running: $ gem env RubyGems Environment: - RUBYGEMS VERSION: 1.6.2 - RUBY VERSION: 1.9.2 (2011-02-18 patchlevel 180) [x86_64-linux] - INSTALLATION DIRECTORY: /opt/rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1 - RUBY EXECUTABLE: /opt/rubies/ruby-1.9.2-p180/bin/ruby - EXECUTABLE DIRECTORY: /opt/rubies/ruby-1.9.2-p180/bin - RUBYGEMS PLATFORMS: - ruby - x86_64-linux - GEM PATHS: - /opt/rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1 - /home/quintus/.gem/ruby/1.9.1 - GEM CONFIGURATION: - :update_sources => true - :verbose => true - :benchmark => false - :backtrace => false - :bulk_threshold => 1000 - "install" => "--format-executable" - "update" => "--format-executable" - "rdoc" => "--format=hanna" - REMOTE SOURCES: - http://rubygems.org/ > FWIW, you can also install wxRuby without creating the gem via : > rake install. As I already said, I compiled a Ruby without Psych support (by deleting the psych extension's directory from the Ruby sources prior to the building commands), then I recompiled wxRuby with $ rake $ rake gem and got the gem file. I took it and installed it onto the Ruby with Psych support--works fine. However, I don't want to have an extra Ruby installation solely for building wxRuby. Which then segfaults. If I remember correctly, in Rails one can force the YAML engine to Syck like this: YAML::Engine.default_yamler = Syck I'm not sure wheather this is rails-specific or not (can't try today), but if not including this line in the main Rakefile should be a possible workaround. Vale, Quintus From sutniuq at gmx.net Thu Mar 17 04:20:16 2011 From: sutniuq at gmx.net (Quintus) Date: Thu, 17 Mar 2011 09:20:16 +0100 Subject: [wxruby-users] Packaging wxRuby fails In-Reply-To: <4D812F97.8020005@gmx.net> References: <4D779EDD.4090806@gmx.net> <4D7C7420.70107@gmx.net> <4D812F97.8020005@gmx.net> Message-ID: <4D81C440.6010909@gmx.net> Am 16.03.2011 22:45, schrieb Quintus: > If I remember correctly, in Rails one can force the YAML engine to Syck > like this: > > YAML::Engine.default_yamler = Syck > > I'm not sure wheather this is rails-specific or not (can't try today), > but if not including this line in the main Rakefile should be a possible > workaround. It's not specific to Rails and works like this: require "yaml" YAML::ENGINE.yamler = "syck" Note the uppercase ENGINE and the "syck" string. However, adding it to the top of wxRuby's Rakefile didn't do the trick, I'm still getting the same error. Vale, Marvin From joiey.seeley at gmail.com Sat Mar 19 14:41:21 2011 From: joiey.seeley at gmail.com (Joe Seeley) Date: Sat, 19 Mar 2011 13:41:21 -0500 Subject: [wxruby-users] Exclusively For You Message-ID: Check this http://tashicake.com/info.html It might be useful for u. -- Joiey Seeley Software Engineer Cell: (319)329-8552 Email: joiey.seeley at gmail.com From giff.h92 at gmail.com Sat Mar 19 15:39:46 2011 From: giff.h92 at gmail.com (Hameed Gifford) Date: Sat, 19 Mar 2011 15:39:46 -0400 Subject: [wxruby-users] Exclusively For You In-Reply-To: References: Message-ID: <1300563587.9521.0.camel@hamstap85-laptop> This appears to be spam. Looks like he was infected and the mailing list was on his contacts. Hope you get it fixed, dude. On Sat, 2011-03-19 at 13:41 -0500, Joe Seeley wrote: > Check this http://tashicake.com/info.html It might be useful for u. > From sutniuq at gmx.net Tue Mar 22 16:17:08 2011 From: sutniuq at gmx.net (Quintus) Date: Tue, 22 Mar 2011 21:17:08 +0100 Subject: [wxruby-users] Packaging wxRuby fails In-Reply-To: <4D81C440.6010909@gmx.net> References: <4D779EDD.4090806@gmx.net> <4D7C7420.70107@gmx.net> <4D812F97.8020005@gmx.net> <4D81C440.6010909@gmx.net> Message-ID: <4D8903C4.2070903@gmx.net> Am 17.03.2011 09:20, schrieb Quintus: > Am 16.03.2011 22:45, schrieb Quintus: >> If I remember correctly, in Rails one can force the YAML engine to Syck >> like this: >> >> YAML::Engine.default_yamler = Syck >> >> I'm not sure wheather this is rails-specific or not (can't try today), >> but if not including this line in the main Rakefile should be a possible >> workaround. > > It's not specific to Rails and works like this: > > require "yaml" > YAML::ENGINE.yamler = "syck" > > Note the uppercase ENGINE and the "syck" string. However, adding it to > the top of wxRuby's Rakefile didn't do the trick, I'm still getting the > same error. > > Vale, > Marvin > Regarding the pixman segfault I can now narrow this down between three versions of libpixman. I just downgraded my pixman lib to 0.20.0, leaving everything else on my system untouched and I got wxRuby working again. Previously installed was 0.20.2, so somewhere between those versions there must be something wrong with libpixman. Tomorrow I'm going to file a bug on the Arch tracker, and hopfully I'll get some informative input there because pinning pixman to 0.20.0 is not a real solution I think (first I'll try to get a hold on pixman 0.20.1, but getting Arch packages for versions out of date that are not cached on your system is kinda difficult). Btw. what's with Ubuntu? Does it work there at the moment? Valete, Marvin From sutniuq at gmx.net Wed Mar 23 11:10:23 2011 From: sutniuq at gmx.net (Quintus) Date: Wed, 23 Mar 2011 16:10:23 +0100 Subject: [wxruby-users] Packaging wxRuby fails In-Reply-To: <4D8903C4.2070903@gmx.net> References: <4D779EDD.4090806@gmx.net> <4D7C7420.70107@gmx.net> <4D812F97.8020005@gmx.net> <4D81C440.6010909@gmx.net> <4D8903C4.2070903@gmx.net> Message-ID: <4D8A0D5F.7060007@gmx.net> Am 22.03.2011 21:17, schrieb Quintus: >> > > Regarding the pixman segfault I can now narrow this down between three > versions of libpixman. I just downgraded my pixman lib to 0.20.0, > leaving everything else on my system untouched and I got wxRuby working > again. Previously installed was 0.20.2, so somewhere between those > versions there must be something wrong with libpixman. Tomorrow I'm > going to file a bug on the Arch tracker, and hopfully I'll get some > informative input there because pinning pixman to 0.20.0 is not a real > solution I think (first I'll try to get a hold on pixman 0.20.1, but > getting Arch packages for versions out of date that are not cached on > your system is kinda difficult). Btw. what's with Ubuntu? Does it work > there at the moment? > > Valete, > Marvin Just thinking that the Arch tracker is not the correct place to file this bug--it's not in Arch, it's in cairo/pixman. However, filing a bug "pixman 0.20.2 breaks wxRuby and segfaults" on bugs.freedesktop.org doesn't seem an adequate information for the pixman developers (btw. there has never been a 0.20.1 version of pixman, so the change breaking wxRuby happened between the 0.20.0 release and the 0.20.2 one). As I'm not familiar with wxRuby's internals I cannot be of much help on tracking down the problem--I don't even know if it's really a pixman problem or a wxRuby one. Suggestions? Valete, Marvin From mario at ruby-im.net Wed Mar 23 19:11:20 2011 From: mario at ruby-im.net (Mario Steele) Date: Wed, 23 Mar 2011 19:11:20 -0400 Subject: [wxruby-users] Packaging wxRuby fails In-Reply-To: <4D8A0D5F.7060007@gmx.net> References: <4D779EDD.4090806@gmx.net> <4D7C7420.70107@gmx.net> <4D812F97.8020005@gmx.net> <4D81C440.6010909@gmx.net> <4D8903C4.2070903@gmx.net> <4D8A0D5F.7060007@gmx.net> Message-ID: This isn't so much a wxRuby issue, as it is a wxWidgets issue. Specifically, the version we use with wxRuby. Newer versions I believe does not have this issue. But the main issue that happens, is that the change between 0.20.0 and 0.20.2, is that pixman_image_composite32() changed the function signature from what wxWidgets is expecting, and what pixman is expecting. I tracked this problem down, specifically to that issue, and difference in signatures. Sadly, I haven't been able to get newer versions of wxWidgets to work with wxRuby 2.0.1, and I haven't been working on wxRuby as of lately, as I've been having issues in Real Life to deal with. Hence for the lateness in the conversation. Basically, what is happening, is Ruby is catching the C/C++ Side of the system error, that attempts to access invalid memory, when pixman_image_composite32() attempts to access a memory location, that is not valid. I believe that the previous method signature in question, had an integer at the position of question, where it's now expecting a memory address. Again, sadly, I don't remember all of the specifics, and I know it is an issue with the older version of wxWidgets that is being used, that is at fault. Not wxRuby. I apologize for the lateness in this reply, and hope this helps you to track down the problem, or find a way for wxRuby 2.0.1 to compile against a newer version of wxWidgets. hth, Mario On Wed, Mar 23, 2011 at 11:10 AM, Quintus wrote: > Am 22.03.2011 21:17, schrieb Quintus: > >> > > > > Regarding the pixman segfault I can now narrow this down between three > > versions of libpixman. I just downgraded my pixman lib to 0.20.0, > > leaving everything else on my system untouched and I got wxRuby working > > again. Previously installed was 0.20.2, so somewhere between those > > versions there must be something wrong with libpixman. Tomorrow I'm > > going to file a bug on the Arch tracker, and hopfully I'll get some > > informative input there because pinning pixman to 0.20.0 is not a real > > solution I think (first I'll try to get a hold on pixman 0.20.1, but > > getting Arch packages for versions out of date that are not cached on > > your system is kinda difficult). Btw. what's with Ubuntu? Does it work > > there at the moment? > > > > Valete, > > Marvin > > Just thinking that the Arch tracker is not the correct place to file > this bug--it's not in Arch, it's in cairo/pixman. However, filing a bug > "pixman 0.20.2 breaks wxRuby and segfaults" on bugs.freedesktop.org > doesn't seem an adequate information for the pixman developers (btw. > there has never been a 0.20.1 version of pixman, so the change breaking > wxRuby happened between the 0.20.0 release and the 0.20.2 one). As I'm > not familiar with wxRuby's internals I cannot be of much help on > tracking down the problem--I don't even know if it's really a pixman > problem or a wxRuby one. > > Suggestions? > > Valete, > Marvin > _______________________________________________ > wxruby-users mailing list > wxruby-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users > -- Mario Steele Lieutenant Commander 3 XO - Geo 99 XO - STO IFT Fleet http://www.trekfederation.com http://geo99.ruby-im.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From sutniuq at gmx.net Fri Mar 25 18:31:20 2011 From: sutniuq at gmx.net (Quintus) Date: Fri, 25 Mar 2011 23:31:20 +0100 Subject: [wxruby-users] Packaging wxRuby fails In-Reply-To: References: <4D779EDD.4090806@gmx.net> <4D7C7420.70107@gmx.net> <4D812F97.8020005@gmx.net> <4D81C440.6010909@gmx.net> <4D8903C4.2070903@gmx.net> <4D8A0D5F.7060007@gmx.net> Message-ID: <4D8D17B8.9010802@gmx.net> Am 24.03.2011 00:11, schrieb Mario Steele: > This isn't so much a wxRuby issue, as it is a wxWidgets issue. > Specifically, the version we use with wxRuby. Newer versions I believe > does not have this issue. But the main issue that happens, is that the > change between 0.20.0 and 0.20.2, is that pixman_image_composite32() changed > the function signature from what wxWidgets is expecting, and what pixman is > expecting. I tracked this problem down, specifically to that issue, and > difference in signatures. Sadly, I haven't been able to get newer versions > of wxWidgets to work with wxRuby 2.0.1, and I haven't been working on wxRuby > as of lately, as I've been having issues in Real Life to deal with. Hence > for the lateness in the conversation. Basically, what is happening, is Ruby > is catching the C/C++ Side of the system error, that attempts to access > invalid memory, when pixman_image_composite32() attempts to access a memory > location, that is not valid. I believe that the previous method signature > in question, had an integer at the position of question, where it's now > expecting a memory address. > > Again, sadly, I don't remember all of the specifics, and I know it is an > issue with the older version of wxWidgets that is being used, that is at > fault. Not wxRuby. I apologize for the lateness in this reply, and hope > this helps you to track down the problem, or find a way for wxRuby 2.0.1 to > compile against a newer version of wxWidgets. > > hth, > > Mario > Not sure why my mail didn't make it to the list, but I'll try again. First, thanks for your answer. If it's not a wxRuby issue, there's some hope to get the whole thing resolved. I really do like the wxRuby GUI toolkit, and unless I'm forced to I wouldn't like to change it. But before further developing, solve the Real Life problems. Although Open-Source software is a great way to spend time, tough. :-) I've just started learning C++ one week ago, and when I've gathered some experience, I'll take a look at the wxRuby code and hopefully get it to compile with newer wxWidgets versons. I'm however not familiar with SVN (always used Git until now), but that can be worked out either. Vale, Marvin