SUMMARY If the user wants to create a new operation by using an existing operation as a start and forgets to click on add new operation and clicks somewhere else (another operation), Skrooge should warn the user. STEPS TO REPRODUCE 1. Click on an already existing operation as a start for creating a new operation 2. Modify the relevant entries 3. Click on another operation (without clicking on create new operation) OBSERVED RESULT All the inserted values are deleted. EXPECTED RESULT The system should ask the user whether the changed values should be dismissed, the modified operation should be changed or a new operation should be created. As this question might annoy some users, an option to (de)activate this feature might be useful. Operating System: Debian GNU/Linux 11 KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.10.0-5-amd64 ADDITIONAL INFORMATION
Hi, Just some questions to well understand your scenario and propose the better solution. In step 3, why did you click on another operation ? What is your intention ? If you want do modify this operation, this is normal to update the form with the new selection.
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!
(In reply to Stephane MANKOWSKI from comment #1) > Hi, > > Just some questions to well understand your scenario and propose the better > solution. > > In step 3, why did you click on another operation ? What is your intention ? > > If you want do modify this operation, this is normal to update the form with > the new selection. Yes, correct, step 3 is an error on my side. Typically in this situation I was sidetracked by some other issue and forget, but sometimes it's just that the click did not work for whatever reason (window wasn't active, cursor didn't match button position, clicking was not recognized, ...) I think it's pretty much the same as when you write a text in a text editor and (most often accidentally) click on close before saving. Then it's usual to have the text editor let the user confirm, that their text (modified state) would be deleted by presenting some options to go forward. I think it's always the same pattern with unsaved modified state, be it an HTML form or in a configuration dialog. Similarly when modifying an entry and forgetting to either create a new entry or overwrite the existing on, the user would again lose modified state and therefore Skrooge should be presenting some options to go forward (ideally disactivable for the future). I think this makes sense from a user friendliness point of view and would have saved some frustration on my side (like an e-mail you have to rewrite because it gone lost somehow during editing – it's not the sheer amount of additional work which is frustrating, but doing the very same thing again).