|[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]|
Hehe, you caught me... ;-)
1) In the documentation and reference material is written: "Before using any web views, you need to call the WebInitForCarbon function. Doing so initializes Cocoa so you can access the Web Kit from your Carbon application."
My application works best when I do _not_ call WebInitForCarbon anywhere. How could that be? Is this call obsolete with the Safari 1.0 distribution?
Strange: When I call WebInitForCarbon my Application receives corrupted events on hiding/showing the application - and open windows (... only the ones with WebViews on it) disappear when the app is hidden/showed.
And when I try a custom Cocoa init function like...
.. the Mouse events are corrupted. It only works without any initialisation of the above kind!
Strange. When I failed to call WebInitForCarbon I received a large litany of messages on the console about the fact that there was no autorelease pool to clean up after the WebKit. You might try opening the console and see if you really are doing as well without calling it as you think you are.
In what other ways does your application "work best" when you don't call WebInitForCarbon?
Is there anybody else with hide/show WebView trouble?
2) When I receive an event through a WebView delegate I do not exactly know what the best way is to inform my Carbon app. Today I create a command event with some parameters and send it to my app. Is this the nicest way to go? How can I do this more elegant.
It's really up to you and what works best for your application.
Marcel _______________________________________________ webkitsdk-dev mailing list | email@hidden Help/Unsubscribe: http://www.lists.apple.com/mailman/listinfo/webkitsdk-dev Do not post admin requests to the list. They will be ignored.
Visit the Apple Store online or at retail locations.
Copyright © 2011 Apple Inc. All rights reserved.