Re: [isugamedev-devel] gamekernel analog inputs

[Kevin M. <ke...@vr...>]

if it is normalized, then applications who don't normalize it themselves
will not be screwed up by a substitution from one device for another.

I'd say it should always return some sane value such as:

[0..1]     (normalized 0 to 1)
[-1..1]    (normalized -1 to 1)
[0..127]   (7bit)
[0..100]   (0 - 100%)
[0..255]   (8bit)
[0..65530] (16bit)

I think it would enable robust applications with less code.

The other possibility would be to have the app set the value...  but then
the driver would have to know how to scale to any arbitrary value (not too
hard to do considering it would have to anyway)...

I'd hate to make the driver very complex, so I'd definately take that into
consideration..

@--@---@---@----@-----@------@------@-----@----@---@---@--@
Kevin Meinert                                  __  _   __  
http://www.vrac.iastate.edu/~kevn         \  ||  \| \ /  ` 
Virtual Reality Applications Center        \ ||.-'|--\    
Howe Hall, Iowa State University, Ames Iowa \||  \|   \`__,
-----------------------------------------------------------

On Sun, 10 Feb 2002, Ben Scott wrote:

> we currently don't have a spec for what kind of float data is returned 
> from an AnalogInput on an AnalogDevice. Should the application query for 
> the range (i.e. Mouse goes from (0-640) or (0-480) depending on the 
> screen), always constrain to the range [-1,1] or allow the application to 
> set the range of the data that should be returned?
> 
> -----
> Ben Scott
> President ISU Game Developers Club
> Treasurer ISU Ballroom Dance Company
> bs...@ia...
> 
> 
> _______________________________________________
> ISUGameDev-devel mailing list
> ISU...@li...
> https://lists.sourceforge.net/lists/listinfo/isugamedev-devel
>