Re: AUCarbonView - 16-bit controls
Re: AUCarbonView - 16-bit controls
- Subject: Re: AUCarbonView - 16-bit controls
- From: Michael <email@hidden>
- Date: Mon, 10 Feb 2003 09:49:09 -0800
This seems like this could be a very useful thing. I've marked it as an
enhancement for a future SDK release. Thank you for your feedback.
Michael Hopkins
CoreAudio Engineering
On Sunday, February 9, 2003, at 10:00 PM,
email@hidden wrote:
Message: 1
Date: Sun, 9 Feb 2003 12:06:18 +0100
Subject: Re: AUCarbonView - 16-bit controls
Cc: <email@hidden>
To: Marc Poirier <email@hidden>
From: =?ISO-8859-1?Q?Airy_Andr=E9?= <email@hidden>
Le jeudi, 23 jan 2003, ` 22:06 Europe/Paris, Marc Poirier a icrit :
Why does the AUCarbonView stuff use the 16-bit Control calls
(SetControlValue, GetControlValue, etc.) and not the 32-bit control
calls
(SetControl32BitValue, GetControl32BitValue, etc.)?
Thanks,
Marc
I just wondered the same.
While I know it seems that 16 bits seems to be enough for a visual
control, you
can have "sub-pixel" fine mode on controls (I have a /10 and /100 mode
on my
knob control).
Is there any technical reason ?
It would also be nice if we could choose the number of digits to be
shown in
text fields.
Airy
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.