The idea is to add a new catalog on top of the one already loaded
Somewhat tied to #59, but will probably require to split main.load_obs() in two new functions (load and display obs). There is probably some redundancy with the current display_obs() and update_and_display_model() functions, some rewriting/refactoring might be needed here.
Then comes the question of how to deal with duplicate obs. Best way is probably to have a warning popup asking which target the user wants to keep, and have a button to apply his choice to all the upcoming conflicts.
Edit: in progress in a dedicated branch.
There are more things to consider than I previously thought.
[x] split the current load function in smaller chunks
There are now dedicated functions to i) initialize an empty obs list and ii) associate the correct headers from a popup. Updating the model and observability is done through the update_and_display_model() and update_obs() functions.
[x] add the option to "append" to the existing list when importing a non-pouet catalog
There is now a checkbox in the header popup for that
[x] add the option to "append" to the existing list when importing a pouet catalog
Need to add a popup for that. But then the .pouet load is not immediate. Might add an option in the config file to override the popup with a default behaviour
[x] properly handle/warn about duplicate targets import
Currently, the duplicated target to import are silently ignored. We might either ask the user what he wants to do, keep the duplicates (not sure the rest of the code is proofed against that...), overwrite with the most recent import, or keep the current behaviour.
[x] importing duplicates when original are hidden makes pouet crash
[x] handle corrupted .pouet files
Trying to load a corrupted .pouet file is currently not catched as an exception, thus might crash/perturb POUET's behaviour.
The idea is to add a new catalog on top of the one already loaded
Somewhat tied to #59, but will probably require to split main.load_obs() in two new functions (load and display obs). There is probably some redundancy with the current display_obs() and update_and_display_model() functions, some rewriting/refactoring might be needed here.
Then comes the question of how to deal with duplicate obs. Best way is probably to have a warning popup asking which target the user wants to keep, and have a button to apply his choice to all the upcoming conflicts.
Edit: in progress in a dedicated branch. There are more things to consider than I previously thought.