Benjamin Schroeder
9/14/2003 2:29:00 AM
On Saturday, September 13, 2003, at 08:01 PM, gabriele renzi wrote:
> I even get this error with this simple script:
>
>>> require 'dotnet'
> => true
>>> loadLibrary('System.Windows.Forms')
> => #<DotNetObject:0x27eb1a0 @dotNet=#<DotNet:0x27ec4a8>,
> @objectRef=#<WrappedObjectRef:0x27eb518>>
>>> Application.run(Form.new)
>
> ....same error...
Do you get this error when running from irb? That seems to work for
me. (A script file should work as well.) I'd be interested to hear
whether it works in that context.
I think what is going on when you are in the evaluator is that an
application loop is already running (to display the evaluator window),
so .NET doesn't want to run one on top of it. Does it work to do
something like "Form.new.show" instead? When there's already a loop
running, like in the evaluator, that will show the window and let it
handle events.
When running from a top-level script, the Application.run should be the
thing to do. This would set up the "main window" for your app. Just
calling show in that context would cause the window to disappear
immediately afterwards.
Hope this helps - please let me know what you find out!
> OTOH, running tests work fine, some tests are failing cause it seem I
> don't have csc.exe in my path..
I'm glad to hear that! We aren't in general as sure about the
portability of the test and build environments. The tests that are
failing because of csc are, I think, mostly just trying to use
libraries that we set up to test particular interop features.
> anyway this is really an impressive package!
> Just two things:
> - would you please add the online documentation to the archive? goin
> online just to get some docs that could safely fit in the .zip file is
> a PITA.
Thanks - and, yes - that's a good idea. We'll add the documentation to
the next release, R4.
> - would you add some more samples?
Sure! Is there any kind of sample you'd like to see?
Thanks,
Ben Schroeder