Ah, makes sense. I'm totally unfamiliar with the way IronRuby is implemented. Is it possible to switch it to a clr string any time it calls any framework code? (like the invoke function I'm using). ~sean
On Fri, Aug 15, 2008 at 10:33 AM, Curt Hagenlocher <[EMAIL PROTECTED]>wrote: > This isn't a Silverlight issue but an IronRuby one. A Ruby string simply > isn't the same as a CLR string – the Ruby string is mutable while the CLR > string is not. > > > > We need to come up with a cohesive plan for dealing with the difference > before we can "fix" anything. > > > > *From:* [EMAIL PROTECTED] [mailto: > [EMAIL PROTECTED] *On Behalf Of *Sean Clark Hess > *Sent:* Friday, August 15, 2008 9:25 AM > *To:* [email protected] > *Subject:* [Ironruby-core] Stupid to_clr_string > > > > Ok, I keep running into this over and over. Whenever Silverlight passes a > string to javascript, it comes out as some unreadable object. You have to > call to_clr_string to get it working. > > > > This is ok... You can monkey patch some of the javascript library code to > fix it, but with HtmlPage.window.invoke, for example, it's not easy to do > because it sends a variable number of arguments. > > > > Is this being fixed? Or is this something we're going to have to deal with > for a while? > > > > Thanks > > ~sean > > _______________________________________________ > Ironruby-core mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/ironruby-core > >
_______________________________________________ Ironruby-core mailing list [email protected] http://rubyforge.org/mailman/listinfo/ironruby-core
