652
edits
Stand Alone ATC Control Development: Difference between revisions
Jump to navigation
Jump to search
m
Stand Alone ATC Control Development (view source)
Revision as of 05:04, 27 September 2010
, 27 September 2010no edit summary
m (beauty job) |
mNo edit summary |
||
| Line 116: | Line 116: | ||
**1 fully active according to ATC-function | **1 fully active according to ATC-function | ||
**1 just for monitoring another frequency (maybe TWR listening also to GND, etc.) - but without activated Microphone (to avoid mishaps under stress!) | **1 just for monitoring another frequency (maybe TWR listening also to GND, etc.) - but without activated Microphone (to avoid mishaps under stress!) | ||
:those two must be exchangeable by one mouse-click (e.g. to tell the other something or just help out on another Twr, etc.) | |||
Off course MPchat is needed – it should be an extra GUI located somewhere | *Off course MPchat is needed – it should be an extra GUI located somewhere | ||
*Have command-selection for non FGCOM users similar to ATC-ML | *Have command-selection for non FGCOM users similar to ATC-ML | ||
**but not numbers to select (as e.g. in VATSIM) but Mouse-click onto understandable abbreviations (as in ATC-ML) | **but not numbers to select (as e.g. in VATSIM) but Mouse-click onto understandable abbreviations (as in ATC-ML) | ||