The current behavior is that the Python Tkinter-based ASDF dialog window remains even if one quits the ds9 instance that creates it. This potentially can cause confusion of ds9 is started again and a new dialog is created.
Since SAMP does not provide tools to easily identify which ds9 process created the dialog, it will be necessary for the creation of Python process to include an identifying means for locating the right ds9 instance (presumably the pid). And then periodically check the status of that pid while the Python process is otherwise idle; if the ds9 process disappears, then the Python process will kill the dialog and any other related windows and end its process.
The current behavior is that the Python Tkinter-based ASDF dialog window remains even if one quits the ds9 instance that creates it. This potentially can cause confusion of ds9 is started again and a new dialog is created.
Since SAMP does not provide tools to easily identify which ds9 process created the dialog, it will be necessary for the creation of Python process to include an identifying means for locating the right ds9 instance (presumably the pid). And then periodically check the status of that pid while the Python process is otherwise idle; if the ds9 process disappears, then the Python process will kill the dialog and any other related windows and end its process.