On Thursday 29 November 2007 12:29, gerard robin wrote:
> On jeu 29 novembre 2007, AnMaster wrote:
> > LeeE wrote:
> > > Re the secondary flight controls, we need to allow for separate
> > > ground steering and rudder control, in addition to differential
> > > braking - with tandem and quadracycle
On jeu 29 novembre 2007, AnMaster wrote:
> LeeE wrote:
> >
> > Re the secondary flight controls, we need to allow for separate ground
> > steering and rudder control, in addition to differential braking - with
> > tandem and quadracycle landing gear you need to steer independently in
> > cross-win
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
LeeE wrote:
> On Wednesday 28 November 2007 10:18, Stuart Buchanan wrote:
>> Hi All,
>>
>> I've added the key assignments currently defined in keyboard.xml to
>> the wiki page, so that we can easily see what assignments people
>> think are missing, a
On Wednesday 28 November 2007 10:18, Stuart Buchanan wrote:
> Hi All,
>
> I've added the key assignments currently defined in keyboard.xml to
> the wiki page, so that we can easily see what assignments people
> think are missing, and any inconsistencies:
>
> http://wiki.flightgear.org/flightgear_wi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Another problems with key bindings:
The Ctrl-M used for menu in some aircrafts (Concorde and a few more by same
author) should be changed. Ctrl-M is same as enter, and that breaks rudder if
you don't have a joystick, so you can only use left rudder,
Stuart wrote
> Sent: 28 November 2007 10:18
> To: FlightGear developers discussions
> Subject: Re: [Flightgear-devel] Keyboard reorg
>
>
> Hi All,
>
> I've added the key assignments currently defined in
> keyboard.xml to the wiki page, so that we can easil
Hi All,
I've added the key assignments currently defined in keyboard.xml to the wiki
page, so that we can easily see what assignments people think are missing, and
any inconsistencies:
http://wiki.flightgear.org/flightgear_wiki/index.php?title=Keyboard_function_priority_list
Note that this onl
* Melchior FRANZ -- Sunday 18 November 2007:
>white ... syntactically correct path to not yet existing property
>green ... path to existing property
>red ... broken path syntax (e.g. "/foo*bar" ... '*' not allowed)
>yellow ... while typing in value for a valid property pat
* Melchior FRANZ -- Wednesday 14 November 2007:
> Here's a more sophisticated and useful toy:
>
> http://members.aon.at/mfranz/keyboard.nas [5.0 kB]
I added a few more features and committed it to CVS. But don't
worry (especially simple-minded emacs users ;-), it's off by
default. There's a di
Don't worry, I'm not going to announce every little addition.
But I just changed debug.nas, and people using this script
need to fetch a new version (or replace _attrib by attributes):
http://members.aon.at/mfranz/keyboard.nas [5.7 kB]
> > -> outputs path and value to screen and
On 14/11/2007, Melchior FRANZ <[EMAIL PROTECTED]> wrote:
> * David Megginson -- Wednesday 14 November 2007:
> > I think you've just made FlightGear into Emacs.
>
> I detest emacs. The script is inspired by vi! :-P
Now you're making me nervous.
All the best,
David
---
* Melchior FRANZ -- Wednesday 14 November 2007:
> -> outputs path and value to screen and terminal
> = -> sets property to value and outputs result
> ? -> lists all properties containing the search
> expression in the path to the terminal
N
* David Megginson -- Wednesday 14 November 2007:
> I think you've just made FlightGear into Emacs.
I detest emacs. The script is inspired by vi! :-P
m.
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through
On 14/11/2007, Melchior FRANZ <[EMAIL PROTECTED]> wrote:
> Here's a more sophisticated and useful toy:
>
> http://members.aon.at/mfranz/keyboard.nas [5.0 kB]
>
> It is started with the '/'-key and then waits for the input of a
> property path, optionally followed by "=" or "?":
Gott im Himmel!
* Georg Vollnhals -- Wednesday 14 November 2007:
> Very interested but with a little time-delay I tested this feature and
> really, this could get one very nice feature of FlightGear.
Here's a more sophisticated and useful toy:
http://members.aon.at/mfranz/keyboard.nas [5.0 kB]
It is started
Some comments about various suggestions:
[non US-keyboards]
* gerard robin -- Tuesday 13 November 2007:
> Some time ago (i must say some years), we where talking about the
> difficulties
> to get an easy use of the keyboard but the ENGLISH one which is the ONLY
> one :)
> As far i remember, yo
Is it possible to consider it as a plugable keyboard system? The sim
would include a standard keyboard layout that was simular to the
normal layout as we know it uptil now, and then if some could use a
more sophisticated layout, they could themselves swap in a keyboard
layout file that supported se
Georg Vollnhals schrieb:
Hi,
I have to add another nice idea.
If the parser could store values from the parser-list then this could be
possible:
MY EDITED PARSERLIST (loaded on startup of FG)
(this is good for an more advanced user who likes it short)
sb=standby
sel=selected
Weser=[112.9]
Nien=[1
Melchior FRANZ schrieb:
> I haven't thought much about the whole matter, but here are
> some of my thoughts anyway. :-)
>
> ..
>
> (3) I find parts of John's idea nice, but the examples in
> the referenced file are much too complex for my taste.
> Also, I wouldn't like a "language" parser
On mar 13 novembre 2007, gerard robin wrote:
> On lun 12 novembre 2007, Melchior FRANZ wrote:
> > I haven't thought much about the whole matter, but here are
> > some of my thoughts anyway. :-)
> >
> > (1) A complete reorganization shouldn't be done before the
> > 0.9.11 release, but I don't a
On lun 12 novembre 2007, Melchior FRANZ wrote:
> I haven't thought much about the whole matter, but here are
> some of my thoughts anyway. :-)
>
> (1) A complete reorganization shouldn't be done before the
> 0.9.11 release, but I don't assume that anyone aimed for
> that.
>
> (2) I'd say t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
David Megginson schrieb:
> [...]
> 2. Decide on a block of keys to be set aside for per-aircraft key assignment.
> [...]
Hi David,
it's a great idea at the right time to set a standard for the key bindings.
Here are some of my thoughts:
1) try to
* Melchior FRANZ -- Monday 12 November 2007:
> (3) I find parts of John's idea nice, but the examples in
> the referenced file are much too complex for my taste.
But then again, if this only "wastes" one key, then I don't
even see a problem with that. We could reserve the ':' key
for that, lik
* Ralf Gerlich -- Monday 12 November 2007:
> Hm, wouldn't that - in UNIX manner - call for an external configuration
> tool to edit the XML bindings?
Yes. And we call this tool "editor". ;-)
> It's not unreasonable to assume that such a solution would require more
> effort than modifying the
Hi!
Melchior FRANZ wrote:
> (2) I'd say that we want to keep the power of XML defined
> bindings (with embedded Nasal where appropriate.) But
> one could think about not having those automatically
> triggered, but read them into a map, and let the
> keys trigger such bindings by na
I haven't thought much about the whole matter, but here are
some of my thoughts anyway. :-)
(1) A complete reorganization shouldn't be done before the
0.9.11 release, but I don't assume that anyone aimed for
that.
(2) I'd say that we want to keep the power of XML defined
bindings (wi
On 11/12/2007 05:52 AM, Stuart Buchanan wrote:
> That's a really interesting idea, and I like your proposed language.
:-)
> 1) I'm pretty sure that implementing this will require quite a change
> to the input code, as we'll need a proper input parser rather than
> the simple keyboard mapping we
On Monday 12 November 2007 13:55:13 Richard Bytheway wrote:
> Willie Fleming wrote:
> > Oh and I'd like NOT to have any functions on the keyboard (such as the
> > time-warp) that will screw up the flight if Im clumsy with the typing.
>
> Although dropping the flaps, airbrakes or gear while at cruis
Willie Fleming wrote:
> Oh and I'd like NOT to have any functions on the keyboard (such as the
> time-warp) that will screw up the flight if Im clumsy with the typing.
Although dropping the flaps, airbrakes or gear while at cruise speed
isn't going to do your flight much good :-)
Richard
---
AJ MacLeod wrote
> Sent: 12 November 2007 12:09
> To: FlightGear developers discussions
> Subject: Re: [Flightgear-devel] Keyboard reorg
>
>
> On Monday 12 November 2007 06:31:26 John Denker wrote:
> > Agreed! I've thought for ages that a top-to-bottom reo
On Monday 12 November 2007 12:08:34 AJ MacLeod wrote:
> On Monday 12 November 2007 06:31:26 John Denker wrote:
> > Agreed! I've thought for ages that a top-to-bottom reorg
> > would be helpful.
> > The starting point for me was the realization that there
> > are far more aircraft functions that ne
On Monday 12 November 2007 06:31:26 John Denker wrote:
> Agreed! I've thought for ages that a top-to-bottom reorg
> would be helpful.
> The starting point for me was the realization that there
> are far more aircraft functions that need to be controlled
> than there are keys on the keyboard
Which
Hi John,
John Denker wrote:
> There are a few aircraft functions that need to be bound to
> a single key for immediate access. The vast majority, however,
> can be bound to a multi-key sequence without causing a problem.
> I definitely don't need a single key for engaging the starter
> or sett
On 11/11/2007 09:36 PM, David Megginson wrote:
> This is a good discussion that we've started.
> I think that we need to take a few steps:
Agreed! I've thought for ages that a top-to-bottom reorg
would be helpful.
The starting point for me was the realization that there
are far more aircraft f
On Sun, 11 Nov 2007 21:36:35 -0500
"David Megginson" <[EMAIL PROTECTED]> wrote:
> This is a good discussion that we've started. Way back when, we
> didn't have menus (or scripting), so every function had to be
> accessible from the keyboard (and all the assignments were hard-coded
> in C++ to boo
35 matches
Mail list logo
