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

Save broken #303

Closed
Cuperino opened this issue Nov 19, 2024 · 1 comment
Closed

Save broken #303

Cuperino opened this issue Nov 19, 2024 · 1 comment
Assignees
Labels
bug Something isn't working
Milestone

Comments

@Cuperino
Copy link
Owner

Issue reported by Elimar Beck via Telegram.

Today I was working with QPrompt 2.0 beta 3... and a saving problem occurred... I was working with a file that kept being saved until a certain time, as the file had several changes I renamed it generating a second file. I made some more changes during the saving and in the end I always send a copy of the "saved" file to the client, however this file did not save the last changes. for the record, before closing the file I used CTRL+s a few times, but I didn't notice that the "saved" message did not appear in the footer.

What could have happened? The shortcut doesn't work? Well, I'll keep an eye on it... (I remember that with every change I always use the ctrl+s shortcut) but this time the changes weren't saved.

To which videosmith replied:

Stuart Scoon, [nov 18, 2024, 5:51:40 p.m.]:
I've noticed when saving a revised version of a file, the save requestor occasionally reverts back to an earlier version unless you explicitly type/select the version you want to save in the dialog before the action.

As for ctrl-s, that has always saved the current version for me (qprompt 1.2 r6)

Then Elimar wrote:

to control the file version I created a version with a different name using "save as".... and the file remained open until the end of the work... I still made some changes and used ctrl+s, but after I created the new file even using ctrl+s the file remained with the first save time, when I used the save as option.
I didn't lose any information because I had created a copy in Word... but I was wondering why this happened

@Cuperino Cuperino added the bug Something isn't working label Nov 19, 2024
@Cuperino Cuperino added this to the 2.0 milestone Nov 19, 2024
@Cuperino Cuperino self-assigned this Nov 19, 2024
@Cuperino Cuperino added this to QPrompt Nov 19, 2024
@github-project-automation github-project-automation bot moved this to Uncategorized Issues in QPrompt Nov 19, 2024
@Cuperino
Copy link
Owner Author

This sounds as if the state of saving in QPrompt was incongruent with reality. I'm not sure how this could've happened, but renaming the file clearly had to do with this. You have uncovered an edge case that needs further inspection. This is probably related to the auto-reload feature, which is meant to detect external updates to the current file and trigger a re-load when that happens.

As for Ctrl+S not working, if QPrompt's state indicates the file has already been saved and there haven't been any new changes, saving is disabled until new changes are made. This is done intentionally to preserve the lifespan of the media you're saving to.

@Cuperino Cuperino moved this from Uncategorized Issues to File Management in QPrompt Nov 19, 2024
@Cuperino Cuperino moved this from File Management to Bugs in QPrompt Nov 19, 2024
@Cuperino Cuperino changed the title Save not working correctly after file is renamed Save broken Nov 21, 2024
@github-project-automation github-project-automation bot moved this from Bugs to Done in QPrompt Nov 21, 2024
Cuperino added a commit that referenced this issue Dec 1, 2024
Cuperino added a commit that referenced this issue Dec 1, 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
Status: Done
Development

No branches or pull requests

1 participant