Re: discovering if a process is busy
Re: discovering if a process is busy
- Subject: Re: discovering if a process is busy
- From: John Stiles <email@hidden>
- Date: Wed, 19 Dec 2007 17:51:07 -0800
Activity Monitor is running a helper process as root to do its magic,
and this helper process is using parts of the OS which can change from
release to release. In other words, it's not easy to write your own
Activity Monitor :(
justin webster wrote:
I would investigate whether your synthesized key events are being
properly posted. You can write an app to "listen" and log key press
events (essentially, a key logger). Maybe you'll find that the
problem is on your end. That would be a happy thing since you are at
least in a position to fix it.
I'm pretty sure what I'm seeing is Pro Tools not handling the keys I
send.
If I add pauses between key events I get the desired result so the key
events themselves are fine.
it is also the case that the more work Pro Tools has to do between key
events the more likely an error.
is there some way to get the kind of stats I see in Activity Monitor?
eg. CPU usage per process, memory usage per process.
I could theoretically take baseline readings for the "idle" app before
I run my routine, then check the values before deciding if it's safe
to send a key event.
pretty shonky but might be an option.
justin
_______________________________________________
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
_______________________________________________
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