Hi catullum, Many thanks for your response, I've just tried explicitly setting the Keyboard type in code to Default and/or ASCII, but no change unfortunately.
Yes, I've questioned (in my own mind) the robustness of the whole Mono/MT/MD environment across various versions over the last few months and come close to throwing in the towel a number of times (mostly Friday afternoons!), and biting the bullet with Objective C. Bit by bit I'm making progress and persevering, and after another dabble with Google's horrendously slow Android emulators yesterday the few crashes/issues with MonoTouch/MD don't seem so bad. I've just moved to MD 2.6b3, but think I'm gonna go back to 2.4.2 as getting lots more spinning color wheel hangs, and also getting all sorts of odd intellisense problems - where it's giving me intellisense for a completely different line in my source. Steve. -- View this message in context: http://monotouch.2284126.n4.nabble.com/SIGSEGV-Crash-dyld-could-not-load-inserted-library-monotouch-fixes-dylib-tp3722121p3726452.html Sent from the MonoTouch mailing list archive at Nabble.com. _______________________________________________ MonoTouch mailing list [email protected] http://lists.ximian.com/mailman/listinfo/monotouch
