orgzly / orgzly-android

Outliner for taking notes and managing to-do lists
https://www.orgzly.com
GNU General Public License v3.0
2.7k stars 306 forks source link

Make the new quick menu less ambiguous #1015

Open anotherboringuser opened 1 year ago

anotherboringuser commented 1 year ago

Hello, In 1.8.10, the quick menu that can be accessed by swiping from the side of a note was replaced with four or five circular icons that appear wherever you swipe. For me, this makes it harder to tell which note the actions refer to. I use this feature all the time to delete notes, but I accidentally deleted the note above or below the desired note multiple times since the change was made, because I couldn’t clearly see which note I was deleting. There are some ways this could be avoided:

  1. Add an undo button of some sort to undo accidental deletions
  2. Highlight the note that’s about to be deleted while its swipe menu is active or at least while the deletion confirmation dialogue shows up
  3. Display the circles in the same location relative to the note every time, no matter where the swipe gesture was detected
  4. Switch back to the old way of showing the bar below the note

I’d be very grateful if someone found the time to implement one of the proposals. Thanks for this amazing app!

rcheetah commented 1 year ago

I highly agree with that request, and was about to open a similar issue.

  1. Use the same or a similar highlight for the selected note as for the multi selection view, when the popup menu is active. This way the user will know what the popup menu is referring to.

  2. A modal window a la "Do you really want to delete this note" is completely senseless, when there is not enough context, what you really are deleting. So add the name of the note into the modal dialog. A la "Do your really want to delete the note 'my highly important note?"

Thank you for the work on this app. Sadly I can't contribute myself, as I am not familiar with android apps.

rcheetah commented 1 year ago

To be honest, I would upgrade this from a 'feature request' to a 'usability bug'