[krita] [Bug 443648] "Load previous session" and "Save session when Krita closes" requires the user to manually create a session before showing any effect
https://bugs.kde.org/show_bug.cgi?id=443648 Dmitry Kazakov changed: What|Removed |Added Keywords|triaged | --- Comment #7 from Dmitry Kazakov --- Remove triaged keyword from CONFIRMED bugs -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 443648] "Load previous session" and "Save session when Krita closes" requires the user to manually create a session before showing any effect
https://bugs.kde.org/show_bug.cgi?id=443648 wolthera changed: What|Removed |Added CC||[email protected] Keywords||triaged Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #6 from wolthera --- Hey. I can confirm with the Krita Version: 5.2.0-prealpha (git 5c98a72) Appimage with Qt 5.15.7 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 443648] "Load previous session" and "Save session when Krita closes" requires the user to manually create a session before showing any effect
https://bugs.kde.org/show_bug.cgi?id=443648 [email protected] changed: What|Removed |Added Resolution|WORKSFORME |--- Status|RESOLVED|REPORTED --- Comment #5 from [email protected] --- Sorry for the late response. The expected behavior you describe sounds fine. There should only be one autosaved session with some name like AutosavedSession.ksn. It doesn't really make sense for autosaved sessions to make use of backups, unless there were like only one or two backups. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 443648] "Load previous session" and "Save session when Krita closes" requires the user to manually create a session before showing any effect
https://bugs.kde.org/show_bug.cgi?id=443648 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 443648] "Load previous session" and "Save session when Krita closes" requires the user to manually create a session before showing any effect
https://bugs.kde.org/show_bug.cgi?id=443648 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 443648] "Load previous session" and "Save session when Krita closes" requires the user to manually create a session before showing any effect
https://bugs.kde.org/show_bug.cgi?id=443648 Tiar changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||[email protected] Resolution|--- |WAITINGFORINFO --- Comment #2 from Tiar --- Would this behaviour be the expected one: 1. Krita closes with "Save session on close" enabled, but there is no session in use. 2. Krita creates a new/default session file in the resources folder and saves its name to the configuration. 3. Next time when Krita opens, it's the same session being used if "Load previous session" is enabled. I have a few questions: 1. Should it always be the same session file (so overwriting over the previous session file when you repeat steps 1-3 multiple times)? Or a new one created every time the user closes Krita? (That could create way too many of them, tbh, I think the first option might be more universally useful). 2. If yes, what name should it be? I guess something that the user wouldn't use themselves? Something like "AutosavedSession.ksn"? 3. If no, I guess something like "AutosavedSession_[date-and-time].ksn"? Note that it will appear in the Sessions dialog. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 443648] "Load previous session" and "Save session when Krita closes" requires the user to manually create a session before showing any effect
https://bugs.kde.org/show_bug.cgi?id=443648 [email protected] changed: What|Removed |Added Version|5.0.0-beta2 |4.4.7 --- Comment #1 from [email protected] --- Actually only observed in Krita 4 so far as https://bugs.kde.org/show_bug.cgi?id=443652 technically makes observing this bug in Krita 5 impossible. I guess I got confused while testing various versions. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 443648] "Load previous session" and "Save session when Krita closes" requires the user to manually create a session before showing any effect
https://bugs.kde.org/show_bug.cgi?id=443648 [email protected] changed: What|Removed |Added Summary|"Load previous session" and |"Load previous session" and |"Save when Krita closes"|"Save session when Krita |requires the user to|closes" requires the user |manually create a session |to manually create a |before showing any effect |session before showing any ||effect -- You are receiving this mail because: You are watching all bug changes.
