Re: [Plib-devel] Re: [PATCH] crease for ac3d files and speedup

[Frederic B. <fre...@fr...>]

Wolfram Kuss wrote :

>On Wed,  1 Dec 2004 09:57:47 +0100, you wrote:
>
>  
>
>>-      num_axes = _JS_MAX_AXES ;
>>+      num_axes = _JS_MAX_AXES_WIN ;
>>    
>>
>
>It is 
>#define _JS_MAX_AXES_WIN 8 
>and _JS_MAX_AXES is 16. I have just been told, windows would
>theoretically support 128 axis and Microsoft would have tested 40+. To
>be honest, I think 8 is really restricted, there is almost no reserve
>left.
>
>Why do you think the change is a good one?
>Maybe we should change to _JS_MAX_AXES_WIN, but up the number?
>  
>

Short answer : the whole windows plib code doesn't actually work with 
16, but works with 8.

longer answer : already posted the 8 october 2004 ( 
http://sourceforge.net/mailarchive/forum.php?thread_id=5726756&forum_id=4479 
)

> the last change to jsWindows.cxx by /smokydiamond/ here :
> http://cvs.sourceforge.net/viewcvs.py/plib/plib/src/js/jsWindows.cxx?r1=1.4&r2=1.5 
>
>
> is giving me an error when running FlightGear. I am getting tons of
> messages like this :
>
> PLIB_JS: Wrong num_axes. Joystick input is now invalid
>
> indicating that the program goes line 251. This is a default case of a
> switch on the number of axis and 16, which is the value of num_axes
> initialized with _JS_MAX_AXES line 129, is not listed as a valid case.
>
> Could someone restore line 129 with its previous wording :
>
> num_axes = _JS_MAX_AXES_WIN
>
> or include 'case 16:' ( or 'case _JS_MAX_AXES:' ) in the switch begining
> line 204

So the problem is not what windows can do, but how the plib code is 
actually written, with numerical literals in it rather than defined 
symbols and code that can use them.

-Fred