A bit of an irritant involving adding to collection and other actions while browsing

[UserEric 0]

Hi Luke

Its still happening. When browsing my library, it suddenly jumps back to start. Any fix on the way? Thanks

 

[Gilgamesh_48 1240]

2 hours ago, UserEric said:

Hi Luke

Its still happening. When browsing my library, it suddenly jumps back to start. Any fix on the way? Thanks

 

Just to add a bit to the info in this thread.

I have noticed that I get the jump to start when, as an example, I choose to edit a particular movie by say changing the poster. After changing the poster the main screen does not update with the new poster (but it will in the next few minutes) I then scroll down the library further.

I believe that, when the update actually happens, that is when the screen resets to the first item.

I have seen the behavior at other times but the refresh after an update that changes the main screen is the only one where I am pretty sure what is happening.

[Luke 42078]

Yes there are some things that need to be reworked here. As collections are part of media metadata now, adding something to a collection updates that something, and that update in turn causes the list to refresh itself to stay up to date. So we need to make our realtime updates a little more granular so that the UI knows what has changed and can skip refreshing the entire list when it's possible to do so.

[Gilgamesh_48 1240]

1 hour ago, Luke said:

Yes there are some things that need to be reworked here. As collections are part of media metadata now, adding something to a collection updates that something, and that update in turn causes the list to refresh itself to stay up to date. So we need to make our realtime updates a little more granular so that the UI knows what has changed and can skip refreshing the entire list when it's possible to do so.

Or do it as you are doing now but temporally store the current location and then, after the refresh, jump to the stored location. 

I do not know how the code actually works but that seems to be the easiest and fastest fix. Clearly the number of objects might change on any refresh so the stored info should be more than just the current location but rather the "name or id" should be stored and the jump should be to that "name or id" or, if the name does not still exist in the list, the jump should be to the position just before or after where that name would normally be.

There are other issues on the fix, like if multiple media files are selected, but it seems that the name or id of where you want to get to after the refresh is the key not the position in the list. Also that allows you to do the full refresh as you are doing now and still return the user to pretty much where he/she/it was before the refresh.

There are a lot of other times where a refresh happens, like sometimes when editing metadata, and most of those could use the same logic to prevent a reset to the top of the list.

I am just an old programmer/developer so what I suggest may be more difficult that I think it is. After all I started with FORTRAN, COBOL, Assembler, FORTH, Pascal, early C and even lisp. The most modern language I have worked in is C++ and the tools today may well be more flexible and more limited.

It is not trivial but it does seen doable from the point of view of this old fool.

Edited July 26, 2021 by Gilgamesh_48

[Luke 42078]

Quote

Or do it as you are doing now but temporally store the current location and then, after the refresh, jump to the stored location. 

We already do this.

[Gilgamesh_48 1240]

7 minutes ago, Luke said:

We already do this.

Then there is a bug because it does not always work. In fact my experience is that when most any update happens, particularly after adding an item to a collection, the "current" position gets lost and you are taken to the top of the list.

Maybe that is because when an item gets added to a collection and you have show collections enabled the item does not exist in the list any more.

[UserEric 0]

I agree. Its a bug. Other Emby users i know, are reporting the same problem. 

[Luke 42078]

We're looking into improving it. Thanks for the feedback.

[UserEric 0]

Hi Luke

Any progress?

 

[Luke 42078]

On 9/13/2021 at 5:34 PM, UserEric said:

Hi Luke

Any progress?