Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow autocompleting aircraft selection by callsign NUMBERS only #720

Closed
erikquinn opened this issue Nov 13, 2016 · 2 comments
Closed

Allow autocompleting aircraft selection by callsign NUMBERS only #720

erikquinn opened this issue Nov 13, 2016 · 2 comments

Comments

@erikquinn
Copy link
Collaborator

Currently, you can type out any callsign and select the aircraft that way instead of shuffling back and forth from keyboard to type and mouse to click on the aircraft to select it.

A more useful implementation of callsign matching would be to allow matching via flight numbers only. Conveniently, the game is already set up to ensure every flight number is unique (eg there will never be a AAL525 and UAL525 in the same game). Therefore, if I want to select VRD858, I should be able to, with nothing selected and without clicking, type 858 c 50 to climb the guy to 5000.

@erikquinn
Copy link
Collaborator Author

Note: this is ESPECIALLY important when it comes to adding pseudopilots (people who can enter the commands you say to them), as there may be many many airplanes on the screen and if they can hear and type the numbers and enter the command instead of searching for the airplane first, much time and effort can be spared. (Trust me, this plagued us with some of the students pseudopiloting in our simulators at Kent State).

@erikquinn
Copy link
Collaborator Author

The ATC repository is being migrated to it's new home at https://github.com/openscope/openscope,
and thus, all issues are being closed. If this is still an issue with the latest version of the sim
(accessible at http://www.openscope.co), or is a feature you still think we are lacking,
please reopen the issue at the new repo.

Please note that the vast majority of these issues have been copied to the new repository, or else are covered by other issues created there. See the below screenshot for what it looks like when your issue is known in the new repo:

image

Thank you!

Closing this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant