On Fri, Apr 03, 2009 at 10:57:03PM +0200, Melchior FRANZ wrote:
>ANSI color codes can be turned off with
>--prop:sim/startup/terminal-ansi-colors=0
Thanks for your answer, Franz!
>all people that do (mostly developers), do have ANSI support. Distributors
>for MS-Windows platforms may want to turn that flag off.
The Amiga already supported those ANSI sequences more than
20 years ago, and, IIRC, for Windows consoles, there also is a
means to enable them. Something, like »DEVICE=ANSI.SYS« in
some startup file (possibly, one then needs to reboot).
But since they are used so rarely, I have not enabled this.
>>{ key: 0, modifier: { meta: 0, shift: 0, alt: 0, super: 0, ctrl: 0, hyper: 0
>>}, pressed: 1 }
>That shouldn't happen. key-code 0 is for Ctrl-Space, and shouldn't appear
>otherwise. Can you check if OSG's "osgkeyboard" example works properly?
I now can confirm that, whatever I do/type, this is the only
key code observed. Also, when »shift« is being held, the
»shift: 0« does not change. The only thing that /does/ work
is »pressed: ...«, which seems to show »0« or »1« correctly.
»osgkeyboard.exe« is not part of my FlightGear distribution,
so I would need to have to rebuild it from the sources. I have
Dev-Cpp (including Min-GW (including gpp)), but I am not sure
how much effort and time it will take from me to successfully
build an appropriate »osgkeyboard.exe« from the sources.
Therefore, I have not yet done it.
Stefan
------------------------------------------------------------------------------
_______________________________________________
Flightgear-users mailing list
Flightgear-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-users
