It is happening when using a remote, which I interpret as equivalent to the keyboard.Can you confirm that you don't see the issue if you just use the keyboard to navigate?
So no immediate solution. No problemIt seems like a more general issue with the focus handling in MP2 and is going to take a bit of thought to fix properly...
I'm pretty sure it is a focus issue. If you click a button in MP2 and it causes a screen switch, MP2 keeps a reference to the underlying item and restores the focus on that item when navigating back. This works fine when clicking a tile or an entry in a media item list for example because the underlying menu items don't change. The difference with the CP button is that it comes from the menu model (this is the same model that handles the entries in the hidden menus, etc) and the menu model rebuilds its list every time the screen changes (because different actions become visible, e.g. showing the filter and sort entries in media views). This means that the focus can't be restored because the references are no longer equal because the list has been rebuilt. Consequently MP2 gives the focus to the first focusable item in the visual tree, which happens to be the home button.I don't think it's related to the focus handling in general. If it would be the focus handling it should have happened in both cases I think.
I'm struggling to see how my commit could have made it worse, it literally just stops the CP button doing anything if you are already on the CP screen, before if you clicked it it would try and execute the action which caused a menu update, rebuilding the group menu and causing the focus to jump. It should not change any behaviour when navigating back, forward or between groups. I have tested this with a build pre my commits and didn't see any change in behaviour, can you try a build from before my commits and verify that there is actually a change?As the focus was jumping by selecting the CP button at first and now also for other buttons after your first commit,
Not sure, if I understood correctly. I did following in Win10 theme (easier to see than BV due to focus frame)EDIT: Can you also test that if you move the focus outside the group menu on the CP screen, e.g. focus one of the tab buttons, then press back/ESC that the focus doesn't jump back to the home button?
Thanks that's what I was after, I think my previous explanation is not 100% correct, it seems that only if the focus is in the group menu in the CP screen when pressing back it defaults to the first group menu item (i.e. the home button) but this is not always consistent.I'm back in audio item screen and nothing is focused
Sure.I still don't fully understand what you mean by the focus jumping back to home when using the other group buttons though, can you give a step by step on how to reproduce?