Re: [Flightgear-devel] keyboard mappings and Short Ref doc
Norman Vine wrote: Jim Wilson writes: Also F8 (Cycle fog type) and F9 (toggle textures) no longer work. Should thes bindings be removed? F8 seems to work on my machines Sigh It looks like F9 needs to get fixed again. This is a *very* useful essential debugging feature for anyone interested in seeing what is 'really' happening during rendering It is also a good indicator as to whether or not 'GL state' is being kept track of properly This functionality has been removed about three months ago. It is no longer possible to use the scenery without textures. Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] keyboard mappings and Short Ref doc
Jim Wilson [EMAIL PROTECTED] wrote: If someone has the TeX utils (and tex4ht) setup on their system, the FGShortRef.* could use an update. Attached below is a list of changes that need to be made. I'm listening - thanks for your input, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] keyboard mappings and Short Ref doc
Martin Spott [EMAIL PROTECTED] said: Jim Wilson [EMAIL PROTECTED] wrote: If someone has the TeX utils (and tex4ht) setup on their system, the FGShortRef.* could use an update. Attached below is a list of changes that need to be made. I'm listening - thanks for your input, Does this mean you've got tex4ht and can do this? Thanks! BTW one thing came to mind. The doc probably should show a few different keys when possible to reduce confusion for non-english users. For example, !,@,#,$ could be listed as SHIFT+1, SHIFT+2, SHIFT+3, SHIFT+4, which will work with most keyboard layouts. Some keys we just can't do that with but maybe something like ~ could be further identified as the upper left on the main keyboard. Best, Jim ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] keyboard mappings and Short Ref doc
Jim Wilson wrote: BTW one thing came to mind. The doc probably should show a few different keys when possible to reduce confusion for non-english users. For example, !,@,#,$ could be listed as SHIFT+1, SHIFT+2, SHIFT+3, SHIFT+4, which will work with most keyboard layouts. Some keys we just can't do that with but maybe something like ~ could be further identified as the upper left on the main keyboard. Well, on french keyboards, we have to hold SHIFT to get the digits, so SHIFT+1 is already 1. The companion of '1' is '' and can be obtained without holding SHIFT. Combinaisons of characters are not the same from keyboards to keyboards so you can't assume that '!' is SHIFT+1 everywhere. This to say that I have difficulties to start all engines with the keyboard, and I don't speak about flaps that is the third glyph that requires Alt-Gr too. -Fred ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] keyboard mappings and Short Ref doc
Jim Wilson [EMAIL PROTECTED] wrote: Martin Spott [EMAIL PROTECTED] said: Jim Wilson [EMAIL PROTECTED] wrote: If someone has the TeX utils (and tex4ht) setup on their system, the FGShortRef.* could use an update. Attached below is a list of changes that need to be made. I'm listening - thanks for your input, Does this mean you've got tex4ht and can do this? Thanks! Hmmm, currently I'm the only maintainer of this document. This means I really _should_ (TM) do that ;-) I'll do my best as time permits. BTW one thing came to mind. The doc probably should show a few different keys when possible to reduce confusion for non-english users. For example, !,@,#,$ could be listed as SHIFT+1, SHIFT+2, SHIFT+3, SHIFT+4, which will work with most keyboard layouts. Nope. I have to repeat myself here - people simply don't listen what I'm talking about! Users with a German keyboard _have_ to use these keys. We definitely can't use Shift-2 to select the second engine on a C310, we have to use @ (AltGr-q). This means Q is the only 'correct' identification for the key you need to press here. I refuse to deal with different keyboard layouts in the manual - this has to be solved in the software. Cheers, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] keyboard mappings and Short Ref doc
Martin Spott [EMAIL PROTECTED] wrote: [...] We definitely can't use Shift-2 to select the second engine on a C310, we have to use @ (AltGr-q). This means Q [...] ^ Errr I mean @, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] keyboard mappings and Short Ref doc
Martin Spott [EMAIL PROTECTED] said: Hmmm, currently I'm the only maintainer of this document. This means I really _should_ (TM) do that ;-) I'll do my best as time permits. We could just move that out of the way and do a plain text file with the correct info (I'm talking about the copy in the base package /Docs folder). BTW one thing came to mind. The doc probably should show a few different keys when possible to reduce confusion for non-english users. For example, !,@,#,$ could be listed as SHIFT+1, SHIFT+2, SHIFT+3, SHIFT+4, which will work with most keyboard layouts. Nope. I have to repeat myself here - people simply don't listen what I'm talking about! Users with a German keyboard _have_ to use these keys. We definitely can't use Shift-2 to select the second engine on a C310, we have to use @ (AltGr-q). This means Q is the only 'correct' identification for the key you need to press here. I refuse to deal with different keyboard layouts in the manual - this has to be solved in the software. Ah ok. That's a problem for another release. Best, Jim ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] keyboard mappings and Short Ref doc
Jim Wilson [EMAIL PROTECTED] wrote: Martin Spott [EMAIL PROTECTED] said: Nope. I have to repeat myself here - people simply don't listen what I'm talking about! Users with a German keyboard _have_ to use these keys. We definitely can't use Shift-2 to select the second engine on a C310, we have to use @ (AltGr-q). This means Q is the only 'correct' identification for the key you need to press here. I refuse to deal with different keyboard layouts in the manual - this has to be solved in the software. Ah ok. That's a problem for another release. Oh, i'd vote for fixing this _before_ the next release because this problem is already known for quite some time, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] keyboard mappings and Short Ref doc
Jim Wilson writes: Also F8 (Cycle fog type) and F9 (toggle textures) no longer work. Should thes bindings be removed? F8 seems to work on my machines Sigh It looks like F9 needs to get fixed again. This is a *very* useful essential debugging feature for anyone interested in seeing what is 'really' happening during rendering It is also a good indicator as to whether or not 'GL state' is being kept track of properly Cheers Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
