-
Notifications
You must be signed in to change notification settings - Fork 82
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
Navigation Monitor - Navigation and Route Plotting Enhancements #2555
Labels
9. enhancement
The behaviour is as specified, but we would like to modify or extend the spec.
Comments
Tkael
added
the
9. enhancement
The behaviour is as specified, but we would like to modify or extend the spec.
label
Jun 25, 2023
|
Note: This would require the ship and carrier plotters to be modified to support multiple destinations and a system for ordering those destinations. |
Tkael
changed the title
Navigation Monitor - Add an option to import a ship or carrier route from Spansh.
Navigation Monitor - Navigation and Route Plotting Enhancements
Sep 4, 2023
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
9. enhancement
The behaviour is as specified, but we would like to modify or extend the spec.
What happens now
Routes must be plotted in EDDI.
What I'd like to happen
How it can happen
Each Spansh plotter has its own unique return / .csv output.
The Navigation Monitor UI would need to have a button to import a .csv file. When clicked, it would open a window where the commander could select a .csv file and automatically recognize the plotter used to generate it (or select the Spansh plotter used to generate it from a dropdown list of supported plotters). We would need to be able to parse each of the supported formats.
EDDI Version
4.0.3-b3
The text was updated successfully, but these errors were encountered: