OpenRadarFeatureWishlist: Difference between revisions

Jump to navigation Jump to search
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...
* 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.
* 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 ==
292

edits

Navigation menu