@asiair@zwo#44349 Thanks for the response! From my development background: you would just ignore a faulty file. The flow would be:
- load the records as usually from an internal storage
- look if this external file has been changed since the last time
- try to parse and merge the content
- if this fails ignore the content and post an error message to the user, e.g. "Cannot parse the custom target list file. The content will be ignored. Correct it, or delete it to restore its content from the internal list"
- if this works, continue and update the file on the next change for the custom list by the user
- If the file was incorrectly formatted by the user, a "reset" option for the user would be to delete the file, and the system would restore it on the next start up and fill it with values from the internal storage.
I'm not sure you are working on the often requested mosaic feature or some other automation, but I can imagine such an interface as the first shot which can be done in a simple way. With this, people could use some third-party software for planning, and the ASIAIR would just walk through the list target by target. I can imagine people would ask for an interface for 3rd-party software anyways.
PS. I suspect you use Qt for the UI. Qt already provides APIs to read/write data in JSON format incl. error handling.
