Cursor memory

I noticed, in Edit mode, that the software doesn’t remember the cursor’s prevoius position. For example, when I place the cursor in the Matrix Side A field and then go to Personal | Notes (where that info is) copy the text I need and return to the Tracks tab, the cursor is no longer in the Matrix Side A field. Is that very difficult to implement? (I know, I need to get a life!)

I’ll put it on the feature request list. Thank you.

(it’s possible, just not sure if we want this, I don’t want it to become confusing, not everyone might be in that “flow” so to say).

No need to get a life! (wait can you say that).

Agree, if you open a tab and you do set the cursor position, it should be the first field. I “complain” :slight_smile: all the time about better keyboard support, and putting a cursor randomly in a field is not contributing to that I think.

Where a cursor pops up, tab index, etc should always follow the general guidelines about accessibility.

I think the CLZ mobile and webapps also have to comply with recent requirements from the EU. WCAG 2.1 AA if I am not mistaken.

Well not random, it would be the first, unless during that specific Edit session you are in a different field, for which I think that might be cool.

Say you put your cursor in Matrix Side A, on the “Tracks” tab, then switch to “Personal” to just check the notes, or copy something, then click the “Tracks” tab again, it would be cool perhaps to have it in the Side A field still.

But if you were to cancel/save and edit a different album, it wouldn’t remember that of course (don’t want that indeed).

1 Like

A similar thing is already happening when your cursor is in a specific field and you go to the next (in my case) movie. Then the cursor already stays in the same edit field. I would like to keep that, it is very useful. If I think about it, indeed it is very nice if a specific field is stored per Tab. So it even works when you go to the next movie within the edit screen. So it saved the cursor position per tab.

If you look at the accessibility stuff I think it is helping and will not make it worse when you for example only use the keyboard.