It appears to be that the WIN32OLE.connect method cannot be fixed as long as the WIN32OLE is class in IronRuby. This is b/c the connect method substitutes for the new(initialize) method when called. I don't believe ruby allows you to create a class instance with out calling the new method. Therefore, I see (2) possible solutions:
1. Change WIN32OLE to a module not a class and have the ability to call connect or new. 2. Add a connect method to WIN32OLE class and change the way connect has to be coded to connect to a running instance of an application. I have attached a file showing a possible way to accomplish solution #1. My questions are: Which way should it go? And are there issues that would come up if WIN32OLE were a module and not a class? Thanks for any help on this. Timothy Attachments: http://www.ruby-forum.com/attachment/5968/win32ole_test.rb -- Posted via http://www.ruby-forum.com/. _______________________________________________ Ironruby-core mailing list Ironruby-core@rubyforge.org http://rubyforge.org/mailman/listinfo/ironruby-core
