-
Notifications
You must be signed in to change notification settings - Fork 77
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
Add a confirmation dialog when the reference viewer is closed #1066
Conversation
ejeschke
commented
Sep 8, 2023
- pops up a confirmation dialog that confirms you intend to quit
- adds support across backends
- can be overridden by adding a line to your general.cfg
- example general.cfg updated
For the docs, hopefully #1067 will fix it. 🤞 Thanks for the ping. I will review when I get the chance. |
- pops up a confirmation dialog that confirms you intend to quit - adds support across backends - can be overridden by adding a line to your general.cfg - example general.cfg updated
0febe1e
to
ddfe13a
Compare
Rebased to pick up the RTD fix |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As a user, I cannot tell what is the difference between "close" and "shutdown" in Ginga. Can you please clarify?
It just provides for a 2-step quit sequence. When someplace calls |
Re: #1066 (comment) Maybe I am not fully understanding but won't it be simpler to have |
The "close" and "shutdown" callbacks allow a flexible way to handle the closure of the program. For example, a plugin might want to register for "shutdown" in order to close a running thread they started or close a database connection, or they could register for "close" to make a checkpoint or pop up their own dialog to say that there are unsaved changes, etc. The reference viewer is basically this core around which there are a large collection of plugins. Plus, we use the framework for many other programs that are not the reference viewer, but benefit from this style. |
Thanks for the clarification! The diff looks reasonable to me and I am okay with this feature's addition. Feel free to merge. 😸 |
Co-authored-by: P. L. Lim <2090236+pllim@users.noreply.github.com>
Thanks, @pllim! |