Page 1 of 1
Where to focus in the notes list after editing
Posted: Fri Feb 01, 2013 4:17 pm
by Thomas Lohrum
Occassionally i scroll down the notes list and edit the one or the other note. The list is sorted after modification date. Because of saving the note, it will be moved to the top of the list, which is fine. However, it also has the focus. Now i have to scroll down the list again and try to find the position where i last edited. Leaving the focus on the last position doesn't seem to be right either. Maybe the refresh of the notes list shall not happen automatically, but only when a new search starts. What do you think?
Thomas
Re: Where to focus in the notes list after editing
Posted: Fri Feb 15, 2013 7:08 am
by CintaNotes Developer
I think that there can't be a one solution that will work in all cases. Sometimes you need to see the note that you've just edited, other time you don't. No automatic refresh means stale view which would cause other problems.
But it should be possible to work around the problem via focusing the next note in the list before saving the note in the editor.
I just checked and it doesn't work since the last edited note is auto-focused, which I think is actually a bug.
Re: Where to focus in the notes list after editing
Posted: Mon Feb 18, 2013 6:24 pm
by Thomas Lohrum
CintaNotes Developer wrote:I just checked and it doesn't work since the last edited note is auto-focused, which I think is actually a bug.
Do i need to create a post on this or did you add it to your bug-tracker? I am asking, because i had just hit the issue again.
Thomas
Re: Where to focus in the notes list after editing
Posted: Fri Feb 22, 2013 10:31 am
by CintaNotes Developer
Thomas Lohrum wrote:CintaNotes Developer wrote:I just checked and it doesn't work since the last edited note is auto-focused, which I think is actually a bug.
Do i need to create a post on this or did you add it to your bug-tracker? I am asking, because i had just hit the issue again.
Thomas
No need, I've added it to our tracker. Will include the fix in 2.0.4 on Monday.