• 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: Apple Remote and exclusivity
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Apple Remote and exclusivity


  • Subject: Re: Apple Remote and exclusivity
  • From: Ilan Volow <email@hidden>
  • Date: Tue, 3 Jun 2008 17:17:48 -0400
  • Domainkey-status: no signature

There's been some changes to device seizing in Leopard. I've had some code of my own (albeit keyboard/barcode scanner stuff) that's been affected by it.

http://developer.apple.com/technotes/tn2007/tn2187.html

I'd think that the Apple remote wouldn't be affected (unless it's being interpreted as some kind of really tiny infra-red keyboard), but it's something to keep in mind.

-- Ilan

On Jun 2, 2008, at 3:44 PM, Elan Feingold wrote:

Hi,

The app I'm working on makes use of the Apple Remote; specifically, it runs a helper app (daemon) so that the app can be started with a press of the Apple Remote Menu button, and then passes key presses it receives to the app via UDP messages.

I'm seeing two issues:

1) Even though I open the device with kIOHIDOptionsTypeSeizeDevice, I'm seeing times where it seems to lose exclusivity. I can't pin it to any specific event (i.e. wake from sleep, etc.), but it definitely seems to lose it after a period of time (hours, days). After that hitting the Menu button brings up both the application *and* Front Row, which is not exactly optimal :-)

I read somewhere that if an application loses focus and then regains it, it should reopen the device to assure exclusivity. I'm not sure how this would work with a daemon that doesn't ever have focus in the application sense.

2) I'm seeing cases where key-presses on the Apple Remote are lost. It might be correlated with the actual application using a bit more CPU. I'm not sure if the process doing the Apple Remote reception needs to be run at a higher priority?

Any help you could offer would be much appreciated!

Thanks,

-elan
_______________________________________________

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


References: 
 >Apple Remote and exclusivity (From: Elan Feingold <email@hidden>)

  • Prev by Date: Re: Manipulating images with meta-data
  • Next by Date: IBOutlet, multiple nibs, method duplication
  • Previous by thread: Re: Apple Remote and exclusivity
  • Next by thread: My windows don't cascade
  • Index(es):
    • Date
    • Thread