-
Notifications
You must be signed in to change notification settings - Fork 231
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
Should changes be saved dialog #96
Comments
Thanks for the bug report. I've managed to reproduce it. Pressing Cancel with the mouse causes the expected behaviour, but pressing escape is equivalent to selecting "No" which closes the whole window. |
Hi. I have just downloaded and used Protege 5 beta and the behavior is still the same for me. Am I doing something wrong? Best,
|
Sebastian, It's fixed in the latest release which was made available this week (5.0.0-beta-16). |
Note: In case Sebastian, or anyone else has problems downloading the latest version from the Protege web site (http://protege.stanford.edu/products.php#desktop-protege), please try to reload the page in your browser manually. We observed that some browsers don't load the updated content when there is change, and show the old (cached) content, unless you manually reload it. You can also get the latest release directly from GitHub: |
Hi,
when closing Protege and having unsaved changes, I am asked if I would like to save those changes. When I hit the Escape-Key on my keyboard Protege quits without saving, although my intention was to abort/cancel the "protege-closing". Is it possible to change this (for me unintuitive) behaviour?
Thanks,
Sebastian
I am on MacOS and use Protege 4.3.
The text was updated successfully, but these errors were encountered: