First of all, I want to be able to set them, so I primarily need the setters, 
but I also want the getters because I want to be able to restore the previous 
values when my app exits or is swapped out.

Second, my goal is to move entirely to Cocoa since, as I understand it, support 
for Carbon is being frozen with the release of Snow Leopard.  So, I'm currently 
in the process of removing all of my Carbon dependencies.  However, I'm just 
fine with C APIs, and, in fact, I'm retaining all of my CGL code since it would 
completely break my platform independent architecture -- which separates the 
rendering layer from the application/event handling layer -- to use Cocoa for 
my rendering.

Christopher



________________________________
From: Sean McBride <cwat...@cam.org>
To: Christopher Hansen <christopher.han...@yahoo.com>; Cocoa-dev@lists.apple.com
Sent: Sunday, May 17, 2009 9:40:29 PM
Subject: Re: LMSetKey[Rep]Thresh

Christopher Hansen (christopher.han...@yahoo.com) on 2009-05-14 1:45 PM said:

>I'm writing a game and I need to set the key and key repeat thresholds
>in my Cocoa application.  The functions needed to do to this under
>Carbon (Events.h) are:
>
>LMGetKeyThresh
>LMSetKeyThresh
>LMGetKeyRepThresh
>LMSetKeyRepThresh
>
>I'm looking for the Cocoa equivalents.

Such questions perplex me.  You don't like procedural C APIs?  You'd
rather some class method?  Or a C API that starts with NS?  Though the
setters are deprecated, the getters above are not deprecated and are
available in 64 bit.  Are you trying to avoid linking to the
Carbon.framework because you currently don't link to it?  In any case, I
believe those API are your only/best choice.

Sean



_______________________________________________

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Reply via email to