Hello, Do you load the WebKit framework before initializing the bridge ? You should have the following statements in your main method:ObjectiveCRuntime.LoadFramework("Cocoa"); * ObjectiveCRuntime.LoadFramework("WebKit");*ObjectiveCRuntime.Initialize(); Regards, Laurent Etiemble. 2008/8/29 osx <[EMAIL PROTECTED]>I tried: 1. get wv.IsFlipped 2. get wv.IsHidden 3. set wv.IsHidden 4. get wv.MainFrame #1, #2, and #3 work. #4 yields similar result as original email (settingwv.MainFrameURL). According to the documentation, #4 only needs OS X v10.2. - sam - Laurent Etiemble writes:Hello, The WebKit wrapper has not been touched recently, so you must have an up-to-date wrapper. After digging around in the doc, I think you have spot a (trivial) bug in Monobjc: - the 'MainFrameURL' property is marked as available on Mac OS X v10.4.11and later (seehttp://developer.apple.com/documentation/Cocoa/Reference/WebKit/Classes/WebView_Class/Reference/Reference.html#//apple_ref/doc/uid/20001903-30112 ) - the 'MainFrameURL' property is marked as Mac OS X 10.5 only in Monobjc ( http://api.monobjc.net/html/P_Monobjc_WebKit_WebView_MainFrameURL.htm) You have to run your application on Mac OS X v10.4.11 or later. According to the stack trace, I think this is not the case. Can you check the Mac OS X version you are running ? I will file a bug to mark properly this property in the Monobjc.WebKit.dll assembly.Regards, Laurent Etiemble. 2008/8/29 Monobjc Support <[EMAIL PROTECTED]>Hello, The WebKit wrapper has not been touched recently, so you must have an up-to-date wrapper. After digging around in the doc, I think you have spot a (trivial) bug in Monobjc: - the 'MainFrameURL' property is marked as available on Mac OS X v10.4.11and later (seehttp://developer.apple.com/documentation/Cocoa/Reference/WebKit/Classes/WebView_Class/Reference/Reference.html#//apple_ref/doc/uid/20001903-30112 ) - the 'MainFrameURL' property is marked as Mac OS X 10.5 only in Monobjc ( http://api.monobjc.net/html/P_Monobjc_WebKit_WebView_MainFrameURL.htm) You have to run your application on Mac OS X v10.4.11 or later. According to the stack trace, I think this is not the case. Can you check the Mac OS X version you are running ? I will file a bug to marke properly this property in the Monobjc.WebKit.dll assembly.Regards, Laurent Etiemble.2008/8/29 osx <[EMAIL PROTECTED]>Does WebView work? [with previous release of Monobjc -- my Monobjc DLLsare dated Jun 26 -- either your release dates or my install dates] For something simple like: wv.MainFrameURL = "http://www.google.com"; where wv is hooked up as an outlet in Interface Builder, I get: 2008-08-29 03:30:23.049 web[72370:717] *** -[WebView setMainFrameURL:]: unrecognized selector sent to instance 0x8eb810 2008-08-29 03:30:23.051 web[72370:717] An uncaught exception was raised 2008-08-29 03:30:23.051 web[72370:717] *** -[WebView setMainFrameURL:]: unrecognized selector sent to instance 0x8eb810 2008-08-29 03:30:23.052 web[72370:717] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[WebView setMainFrameURL:]: unrecognized selector sent to instance 0x8eb810' Thanks! I've had no problems with other controls I've used so far.- sam -
that's it... it's working now. you rock!
thanks!
- sam -
Laurent Etiemble writes:
- [EMAIL PROTECTED] WebView osx
- Re: [EMAIL PROTECTED] WebView Laurent Etiemble
- Re: [EMAIL PROTECTED] WebView osx
- Re: [EMAIL PROTECTED] WebView osx
- Re: [EMAIL PROTECTED] WebView Laurent Etiemble
- Re: [EMAIL PROTECTED] WebView osx

