FxRuby crashes on app.exit

[rleblanc]

Hi,
Just started experimenting with Ruby and FxRuby (which I really like), but I've been crashing when app.exit is called. My main screen also freezes when a sub window is closed using app.stopModal(self) [new line] self.close. I have just installed FxRuby 1.6.34 gem and am still having the same issues. I understood that the first issue had already been dealt with. Can you please help? Yours truly, Raymond

[neillturner]

usually crashes are caused by incorrect coding.

I would try running the fxruby examples from https://github.com/larskanis/fxruby/tree/1.6/examples and getting a copy of FXRuby: Create Lean and Mean GUIs with Ruby you can see the pdf on the internet and work through it.

fxruby is easy to code once you know how and follow the examples but when you code incorrect you get crashes which are difficult to debug. the fxruby is pretty stable now so you can generally assume any crashes are you coding error.

[rleblanc]

Hi Neill,

Thank you for your quick response. I agree with you that crashes are usually caused by incorrect coding. Working as a full time VBA developer and consultant for close to two decades, I know you are right about that .

I really appreciate your suggestions and will check out that link. I already own and have read about 3/4 of that book in its entirety several months ago.

Using FXRuby has been really enjoyable experience and I know I'll figure out the correct syntax sooner or later. I have followed the examples in the book quite closely and they work fine except when I applied them to a view with a FXTreeList.

Regards,

Raymond

From: "Neill Turner" notifications@github.com

To: "larskanis/fxruby" fxruby@noreply.github.com
Cc: "rleblanc" raymond.leblanc@shaw.ca, "Author" author@noreply.github.com
Sent: Tuesday, May 3, 2016 1:01:16 AM
Subject: Re: [larskanis/fxruby] FxRuby crashes on app.exit (#34)

usually crashes are caused by incorrect coding.
I would try running the fxruby examples from https://github.com/larskanis/fxruby/tree/1.6/examples and getting a copy of FXRuby: Create Lean and Mean GUIs with Ruby you can see the pdf on the internet and work through it.
fxruby is easy to code once you know how and follow the examples but when you code incorrect you get crashes which are difficult to debug. the fxruby is pretty stable now so you can generally assume any crashes are you coding error.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub

[neillturner]

I have written alot of FXruby code in my open source devops tool at https://github.com/neillturner/ec2dream
if you looking for sample code. but running the examples are very useful.

[rleblanc]

Much appreciated Neill.

Raymond

----- Original Message -----

From: "Neill Turner" notifications@github.com
To: "larskanis/fxruby" fxruby@noreply.github.com
Cc: "rleblanc" raymond.leblanc@shaw.ca, "Author" author@noreply.github.com
Sent: Tuesday, May 3, 2016 12:46:10 PM
Subject: Re: [larskanis/fxruby] FxRuby crashes on app.exit (#34)

I have written alot of FXruby code in my open source devops tool at https://github.com/neillturner/ec2dream
if you looking for sample code. but running the examples are very useful.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub

[larskanis]

Is this issue still present? Do you have a reproducible test case?

[genie23-tmp]

Hello, I have the same problem. But Ruby Interpreter (CUI) 2.4.2p198 for Windows bug when I try to execute that :
self.connect(SEL_CLOSE) do q = FXMessageBox.question(@app, MBOX_YES_NO, "Sure?", "You sure?") if q == MBOX_CLICKED_YES print "Bye" end end

I did try this other method :
self.connect(SEL_CLOSE, method(:on_close))
with this method :
def on_close q = FXMessageBox.question(@app, MBOX_YES_NO, "Sure?", "You sure?") if q == MBOX_CLICKED_YES print "Bye" end end

I get the same result. My files are encoded in UTF-8 with BOM (I use Notepad++) but I get same result when I encode in UTF-8 without BOM.