Re: InputManagers in Leopard
Re: InputManagers in Leopard
- Subject: Re: InputManagers in Leopard
- From: "Gerriet M. Denkmann" <email@hidden>
- Date: Thu, 20 Nov 2008 15:21:14 +0700
On 19 Nov 2008, at 23:16, "Michael Ash" <email@hidden> wrote:
On Wed, Nov 19, 2008 at 7:04 AM, Gerriet M. Denkmann
<email@hidden> wrote:
I know that InputManagers are "now officially unsupported." And
also that
"this functionality is likely to be disabled in a future release."
But while it is still possible I would like to continue using them.
So I copied my thing into the /Library/InputManagers folder.
Then did
sudo chown -R root:admin /Library/InputManagers
and
sudo chown -R go-w /Library/InputManagers
and started some non-64 Bit programm, expecting to see the NSLog()
call made
in the +load method.
But, alas, I did see nothing.
This used to work on ppc-Tiger - but no more on intel-Leopard.
Anything else I should check?
You need the correct permissions as well, not just the correct owner.
Does "chown -R go-w" even work?
Why should it not? Anyway, it seems to work ok - no group nor other
has any write permissions.
Anyway, download a known working input manager such as SIMBL, and
compare the permissions with yours until you find the discrepancy.
It turned out not to be a permissions-problem at all.
If I have:
/Library/InputManagers/MyFancyInputManager (owned by root etc.)
and also (with the same name)
~/Library/InputManagers/MyFancyInputManager
then things get very confusing, inconsistent and in most cases just do
not work.
But when I rename one of these to:
~/Library/InputManagers/AnInputManagerNotToBeLookedAt
then everything starts working just fine.
Kind regards,
Gerriet.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden