[Flightgear-devel] [PATCH] jsclient and jsserver 64 bit support and 6 axes
bug #100 recently submitted is a fix for 64bit system. http://code.google.com/p/flightgear-bugs/issues/detail?id=100 pete -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [PATCH] jsclient and jsserver 64 bit support and 6 axes
> bug #100 recently submitted is a fix for 64bit system. > > http://code.google.com/p/flightgear-bugs/issues/detail?id=100 > > pete > The 64bit fix is commited with some tiny cosmetic modifications. I did not commit the 6-axes fix for the following reason: If we change the protocol anyway, why not do it right an support the maximum number of axes from plib (currently 16)? I'd suggest sending the number of axes in the first 32bit word followed by a 32bit word for each used axes. Torsten -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [PATCH] jsclient and jsserver 64 bit support and 6 axes
On 03/10/2010 01:47 AM, Torsten Dreyer wrote: > I did not commit the 6-axes fix for the following reason: > If we change the protocol anyway, why not do it right an support the maximum > number of axes from plib (currently 16)? The following idea is better: > I'd suggest sending the number of axes in the first 32bit word followed by a > 32bit word for each used axes. "Doing it right" means supporting an _arbitrary_ number of axes, not 6 or 16. Also an arbitrary number of buttons. Just because plib is currently limited to 16 does not mean FG should make the same mistake. Over the years FG has become progressively less vulnerable to the limitations of plib. It is easy to foresee a day when all plib dependencies have been removed from FG. -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [PATCH] jsclient and jsserver 64 bit support and 6 axes
Thanks for the positive repsonse ;-) however... I have pasted your replies into the bug tracker so the original filer(david) can have a trackable chain as the submitter who is not on this mailing list. http://code.google.com/p/flightgear-bugs/issues/detail?id=100 Should this have been a "forward" from the issues list to this mailing list, then the thread would be upon the issues tracker and not the mailing list., however the exact same volume of traffic + response. This leads to a double jepardy and indeed confusion via replication.. imho pete John Denker wrote: > On 03/10/2010 01:47 AM, Torsten Dreyer wrote: > > >> I did not commit the 6-axes fix for the following reason: >> > > >> If we change the protocol anyway, why not do it right an support the maximum >> number of axes from plib (currently 16)? >> > > The following idea is better: > > >> I'd suggest sending the number of axes in the first 32bit word followed by a >> 32bit word for each used axes. >> > > "Doing it right" means supporting an _arbitrary_ number of > axes, not 6 or 16. Also an arbitrary number of buttons. > > Just because plib is currently limited to 16 does not mean > FG should make the same mistake. > > Over the years FG has become progressively less vulnerable > to the limitations of plib. It is easy to foresee a day > when all plib dependencies have been removed from FG. > > > -- > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > ___ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel > -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel