292
edits
OpenRadarFeatureWishlist: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
|||
| Line 9: | Line 9: | ||
* Inter ATC communication. Some method of talk/text just between ATC controllers would be nice, to coordinate handovers (ww: yes, but as much as I know they use mumble right now...) | * Inter ATC communication. Some method of talk/text just between ATC controllers would be nice, to coordinate handovers (ww: yes, but as much as I know they use mumble right now...) | ||
* Make it not working at FG's [[KSFO|default airport]] (to guard against heart attacks on trying-to-be-KSFO-police people). ww: We are living in a free world of free software. Its like forbidding aircrafts at an airport. I have seen pilots missing all decency and mad ATC guys. We cannot lock them out without creating a closed environment... No, that is not the way it should be done... If someone wants to disturb he still can use aircrafts or the different ATC-models out there... | * Make it not working at FG's [[KSFO|default airport]] (to guard against heart attacks on trying-to-be-KSFO-police people). ww: We are living in a free world of free software. Its like forbidding aircrafts at an airport. I have seen pilots missing all decency and mad ATC guys. We cannot lock them out without creating a closed environment... No, that is not the way it should be done... If someone wants to disturb he still can use aircrafts or the different ATC-models out there... | ||
* ( | * (done: SHIFT+F12) The ability to reload the airport without having to restart the whole application. This is while I am developing Routes, it's a pain to constantly have to restart the entire thing. (ww: yes, pretty useful, I think about it. Reloading the routes would be enough I think...) | ||
== RadarMap == | == RadarMap == | ||
| Line 18: | Line 18: | ||
== Route Editing == | == Route Editing == | ||
* ( | * (done: syntax <code><addPoint code="AGOLO" point="50.200000,9.676111"/></code> ) Ability to specific locally specific points. Rather than hacking the Apt.dat.tgz file, adding to say nav.xml within folder. Additionally these points should be in the form of existing points notification and searched first before globals | ||
* Speed limitation point tag for Elements, similar to the arrows. Requires text for speed. (ww: the attribute <code>text=""</code> is not enough?) | * Speed limitation point tag for Elements, similar to the arrows. Requires text for speed. (ww: the attribute <code>text=""</code> is not enough?) | ||
* ( | * (done: example: <code>begin="KOAK-RW29"</code>) The ability to reference runway start and end as nav points | ||
== RadarContact handling == | == RadarContact handling == | ||
== FGCom Integration == | == FGCom Integration == | ||
* Remove CTRL as PTT button, clashes with CTRL-Left click for "neglect", suggest Right Shift (ww: but the right hand is occupied with the mouse. maybe we move the neglected key to the right SHIFT. SH: If using FGcom, most of the time there would be no need to use anything but single key presses, so therefore any button would be fine. Remember LShift is the primary key for PTT2. Fn keys?) | * (Done) Remove CTRL as PTT button, clashes with CTRL-Left click for "neglect", suggest Right Shift (ww: but the right hand is occupied with the mouse. maybe we move the neglected key to the right SHIFT. SH: If using FGcom, most of the time there would be no need to use anything but single key presses, so therefore any button would be fine. Remember LShift is the primary key for PTT2. Fn keys?) | ||
:ww: removed CTRL+CLICK, there is a textbutton above the flightstrips now, to toggle neglect | :ww: removed CTRL+CLICK, there is a textbutton above the flightstrips now, to toggle neglect | ||
* Add "set PTT button" feature | * Add "set PTT button" feature | ||