So I have an odd issue, when I run a ruby application by first opening
up a command window and then typing:
"D:\Ruby186\bin\ruby.exe" 'C:\Program Files
(x86)\VUITOOLS\ce\gui\main.rb'
my application works fine when I do that.
However, If I run it by double clicking on an Icon that has that same
line as the "target" field, it opens up my gui using wxruby, however it
crashes once I begin a process. I had to take a quick screen
shot before the window closed, and the attached photo is what I got. I
have no idea what this means.
Any help would be great, please let me know if you need to see anything
else.
Attachments:
http://www.ruby-forum.com/attachment/6627/best.jpg
···
--
Posted via http://www.ruby-forum.com/.
So I have an odd issue, when I run a ruby application by first
opening up a command window and then typing:
"D:\Ruby186\bin\ruby.exe" 'C:\Program Files
(x86)\VUITOOLS\ce\gui\main.rb'
my application works fine when I do that.
This looks as if you're using Ruby 1.8.6. As far as I know wxRuby only
supports Ruby >= 1.8.7.
However, If I run it by double clicking on an Icon that has that
same line as the "target" field, it opens up my gui using wxruby,
however it crashes once I begin a process. I had to take a quick
screen shot before the window closed, and the attached photo is
what I got. I have no idea what this means.
The exception looks as if you somewhere require a file called
"defaultDriver.rb" relative to the current working directory, and
double-clicking on an icon sets your current working directory
somewhere else, causing Ruby to not find that file. In Ruby 1.9 you
would have spotted such an error right away as it disallows requiring
files relative to the current directory by default with "require". You
would have to use "require_relative" or modify your $:.
It could also be caused by a too old version of RubyGems as the
exception seems to come from somewhere inside RubyGems.
Any help would be great, please let me know if you need to see
anything else.
$ ruby -v
$ gem -v
Vale,
Marvin
···
Am 27.09.2011 20:22, schrieb Chase Wilson: