On Nov 19, 2008, at 10:06 AM, Donnie Lee wrote:
3. Since there's already an "Input Methods" folder in Leopard that
replaces
the (supported) functionality of input managers and which
developers are
encouraged to use instead of input managers, since Apple clearly
disapproves
of this sort of hack, and since input managers don't work with 64-
bit apps,
it shouldn't be a surprise to anyone if they disappear in some
future OS X
version. Even in the best case, your hack will stop working as apps
begin
migrating to 64-bit.
Should I use mach_inject then? Will it work on 10.6?
Again, I don't have 10.6, so I don't know, and if I *did* know I
wouldn't be able to tell you anyway. My *guess* would be that it
won't, but even if it does end up working on 10.6, it will stop
working at some point after that, since if I am correctly informed
(someone correct me if I'm wrong), mach_inject doesn't work on 64-bit
apps either, so as more and more apps go 64-bit, your hack won't work
with them. In general, 64-bit code on OS X is fairly injection-proof,
and Apple clearly is frowning on code injection these days. My
suggestion would be to do something else that's more kosher.
Charles
P. S. Found the Apple document I wasn't able to find the first time,
which says that Input Managers are going away at some undetermined
point in the future:
http://developer.apple.com/releasenotes/Cocoa/AppKit.html#NSInputManager
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
