• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Calling methods on other applications?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Calling methods on other applications?


  • Subject: Re: Calling methods on other applications?
  • From: Ken Tozier <email@hidden>
  • Date: Sun, 3 Apr 2005 05:04:07 -0400

You might be able to do this with an AppleScript. You can ask the finder for a list of application processes which you could then loop through, sending a request for a list of documents. Once you have the list of documents, you could use a try block to resize them. This would most likely require a bit of trial and error to get the syntax right, but the end result would be a legal, non-hackey way to accomplish what you're trying to do.


On Apr 3, 2005, at 12:18 AM, Conrad Carlen wrote:

On Apr 2, 2005, at 3:19 PM, Finlay Dobbie wrote:

On Apr 2, 2005 11:55 PM, Benjamin Blonder <email@hidden> wrote:
Ideally I'd like to be able to somehow
convert the PIDs it returns into actual NSApplication pointers I could
then use to call the relevant resize methods. Right now though I'm
stumped as to how to do this. It seems like it ought to be possible -
any ideas?

What makes you think it ought to be possible? It isn't.
There is no supported way to accomplish what you are trying to do. Your best bet is the unsupported hacks like APE or SIMBL.

Benjamin,

For Cocoa, see NSObject's <x-tad-bigger>poseAsClass:(Class)</x-tad-bigger>aClass.

poseAsClass is part of NSObject, is not deprecated, and thus not a "hack." What you do with it, to somebody else's app, may be another story. The bad part about poseAsClass is that there isn't a good way that I know of to use it in the context of somebody else's app. Input Managers have been used but that seems likely to break in the future if Input Manager modules are executed later than launch time - when it becomes too late to pose. Depending on how you use poseAsClass, particularly if you can find a way to use it without the Input Manager, it's not altogether evil - you'll probably have to revise your code whenever the app you're posing in changes, though.

-Conrad

 -- Finlay
 


_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden _______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: Calling methods on other applications?
      • From: "Mike Hall" <email@hidden>
References: 
 >Calling methods on other applications? (From: Benjamin Blonder <email@hidden>)
 >Re: Calling methods on other applications? (From: Finlay Dobbie <email@hidden>)
 >Re: Calling methods on other applications? (From: Conrad Carlen <email@hidden>)

  • Prev by Date: Re: intercepting keydowns
  • Next by Date: Re: Calling methods on other applications?
  • Previous by thread: Re: Calling methods on other applications?
  • Next by thread: Re: Calling methods on other applications?
  • Index(es):
    • Date
    • Thread