-
Notifications
You must be signed in to change notification settings - Fork 2
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
PDC reminder #7
Comments
Ideally any position covering GMP role :) |
Could also quite easily have a config option to auto-connect if it's on, so then vStrips/vEFPS users can turn it off but we still get the benefit for the rest 🤔 |
If it's going to be a prompt, why not prompt immediately at log-on? SImpler than waiting 3 mins imo |
Mainly because when you log on taking over from someone, they often won't have disconnected the PDC at that point so there's not much you can do. I think what would work well: With auto-connectOn login, try auto-connect. If it fails, re-run after like 1/2 mins. Without auto-connectPrompt after, say, 5 minutes if no other PDC connection is detected to the current selected station. |
Would be nice to know any time the Hoppie connection goes down at the airport you're covering DEL at. (e.g. GND has it but logs off, TWR is top-down, notify TWR "Would you like to connect smr hoppies"). Equally, imediately at log-on if it's not connected. I just feel 5 mins later is kinda useless cos 80% of the time I wanna connect it immediately. |
The downside is that if it takes a second for vStrips or whatever else to connect we don't want to annoy the user with notifications. With auto-connect yeah it could be useful, maybe also a message to the GMP (or top-down) if vSMR notices that the connection has gone down |
After 3 minutes connected (?), poll hoppies to see if the station is connected. If not, probe to connect, if the controller is on GMP (or GMC with no one below if this isn't going to explode my brain)
The text was updated successfully, but these errors were encountered: