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

Empty document created on startup handled by Rnote as modified by default while it should be considered as empty and unmodified by default #1258

Open
wl0t opened this issue Oct 18, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@wl0t
Copy link

wl0t commented Oct 18, 2024

Describe the bug
A prompt to save file or ignore modifications appears when trying to close the default empty and unmodified document that is created at startup of rnote.

The first empty document created at start-up should be considered as empty and unmodified by default. (as it is the case for other empty document created when opening new tabs).

To Reproduce 1
1.Start rnote
2.Try to close rnote
3.A popup appears prompting to save the modifications or ignore modifications of the empty document.

Or equivalently:

To Reproduce 2
1.Start rnote.
2. Create a new empty document in a new tab.
3. Try to close the first empty document of the initial tab.
3.A popup appears prompting to save the modifications or ignore modifications of the empty document.

Expected behavior
This prompt should not appear as the document is empty and unmodified.

Desktop (please complete the following information):

  • OS: Fedora 40 or Windows 11
  • App Version: Rnote v0.11.0
  • Installation Source: Flatpak or .exe
@wl0t wl0t changed the title Prompt to save changes of the the first default blank file created on each startup of rnote Empty document created on startup handled by Rnote as modified by default while it should be considered as empty and unmodified by default Oct 18, 2024
@Doublonmousse Doublonmousse added the bug Something isn't working label Oct 21, 2024
@Doublonmousse
Copy link
Collaborator

I'm not sure I'm able to reproduce this. Do you have "draw with touch" enabled in the settings (maybe some unwanted strokes slipped in between).

Though I haven't tried exactly the same version/os combination yet

Repository owner deleted a comment Oct 24, 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

3 participants
@Doublonmousse @wl0t and others