Erik Veenstra wrote:

>> An 'include Qt' statement in qtruby.rb where a couple of
>> methods were being added to class Module was causing all the
>> Qt methods to be added to Module. Oops, this a really serious
>> bug. Various methods in qtruby.rb are now module methods in
>> the Qt::Internal module.
> 
> This "hack" caused a problem in RubyScript2Exe when trying to
> "compile" a Ruby application which uses Qt. I've tested the
> combination RubyScript2Exe and Qt with a little HelloWorld
> program. It works!
Yes, my mistake was to think of 'include Qt' being just like a 'using
namespace' statement in a static language like C++. But it isn't like that
at all, and in this case was having quite major unexpected effects. 

I'd known there was something 'not quite right' in the namespace handling of
QtRuby for a while, but couldn't work out what it was. That was I was so
pleased when you found the problem.

-- Richard