FROM : Michael Vannorsdel
DATE : Sat Mar 22 18:29:34 2008
Thanks for that. Almost forgot about method swizzling.
On Mar 22, 2008, at 7:16 AM, ∞ wrote:
>
> Il giorno 19/mar/08, alle ore 13:53, mikevann ha scritto:
>> Is it possible to keep input managers from loading into your
>> application? Too often developers are using these to hack
>> different behavior into all programs and causing crashes which
>> shouldn't normally happen.
>
> My own PlugSuit offers a mechanism for applications to be auto-added
> to the excluded apps list with a message (PlSAllowsInjection = NO;
> in Info.plist -- LinoType FontExplorer X uses it, for instance).
> However, in the end I leave the choice to the user.
>
> You may hijack NSBundle's methods using method swizzling or class
> posing, returning NO's and errors if the bundle is in (any Library)/
> InputManager.
DATE : Sat Mar 22 18:29:34 2008
Thanks for that. Almost forgot about method swizzling.
On Mar 22, 2008, at 7:16 AM, ∞ wrote:
>
> Il giorno 19/mar/08, alle ore 13:53, mikevann ha scritto:
>> Is it possible to keep input managers from loading into your
>> application? Too often developers are using these to hack
>> different behavior into all programs and causing crashes which
>> shouldn't normally happen.
>
> My own PlugSuit offers a mechanism for applications to be auto-added
> to the excluded apps list with a message (PlSAllowsInjection = NO;
> in Info.plist -- LinoType FontExplorer X uses it, for instance).
> However, in the end I leave the choice to the user.
>
> You may hijack NSBundle's methods using method swizzling or class
> posing, returning NO's and errors if the bundle is in (any Library)/
> InputManager.
| Related mails | Author | Date |
|---|---|---|
| mikevann | Mar 19, 13:53 | |
| ? | Mar 22, 14:16 | |
| Michael Vannorsdel | Mar 22, 18:29 |






Cocoa mail archive

