-
Notifications
You must be signed in to change notification settings - Fork 38
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
Can't delete notes from search dialog #313
Comments
+1 from me. |
Yes, I firmly agree. I look for that capability myself sometimes ! Should be there in the next release, a beta for the brave not too far away. Davo |
OK, I have just released a beta that addresses this issue. Reasonably well tested and probably quite safe to use. Thanks for your report and helping to make tomboy-ng a better product. Davo |
When I delete a note that is currently open from the search dialog, the note disappears from the list in the search dialog but remains open. |
Wow, thats a good one uwemock ! I did not even think of that possibility. How you you react ? Should we just close the note first and then continue deleting OR, because the user has that note open, maybe its a mistake, decline to delete it ? Or refer the user to the open note where they can delete it directly ? Davo |
When the user requests the note to be deleted, ist should be deleted (and the open window should close). |
Hi, version 0.41 of tomboy-ng is now available. I believe it solves the issue you reported here. |
I have over 350 notes and need to do some house cleaning. In the original Tomboy, I could delete any note (or many notes) from the search dialog. With Tomboy-ng, I can only select a note to view it. I cannot select more than one note and I cannot delete any notes. I have to open the notes individually and delete them. This is the biggest PITA I have experienced in a LOOOOOONG time.
Please make it so that notes (one or more) can be selected in the search dialog and they can be deleted.
For now, I am going back to the original Tomboy.
The text was updated successfully, but these errors were encountered: