Skip to content
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

[Bug] Data loss, because confirmation dialog logic is inverted #1586

Open
1 task
NewUser2020 opened this issue Mar 8, 2024 · 0 comments
Open
1 task

[Bug] Data loss, because confirmation dialog logic is inverted #1586

NewUser2020 opened this issue Mar 8, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@NewUser2020
Copy link

Operating System

Windows

What's the issue you encountered?

Hello,

first of all: Thanks for the awesome tool!

Here's my problem:

When closing a changed file, ImHex asks me whether I want to close it.
Are you sure you want to close them?
YES: File is closed => Data loss
NO: File is not closed

Every program I work with asks the other way around:
Do you want to save changes to your file?
YES: File is saved => NO Data loss
NO: File is not closed
CANCEL: Keep file

The problem I repeatedly run into is that I confirm the ImHex dialog with YES, because that is how all programs behave.

Honestly, there is so much text to read in that dialog that it costs lots of time to read it, decode the logic and make a decision.

It would save me (and probably many others) a lot of time and data loss, if the logic in that dialog could be reversed.

How can the issue be reproduced?

  1. Start ImHex.
  2. Create New File
  3. Menü: File > Close
  4. Dialog appears

ImHex Version

1.32.1

ImHex Build Type

  • Nightly or built from sources

Installation type

msi

Additional context?

No response

@NewUser2020 NewUser2020 added the bug Something isn't working label Mar 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant