Fixed find objects from search history #3671
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
We're using custom objects to visualize locations of objects from SIMBAD (and when these objects are no exists in our database) currently and this feature in Search Tool works good for one session. In next session, these objects will be cannot found via search history - via SIMBAD only.
This pull request is enhancing the CustomObjectsMgr class via adding code for saving SIMBAD objects into special file and restoring list of saved files in next sessions.
Fixes #3199 (issue)
Type of change
How Has This Been Tested?
Checklist: