Reply to thread

Message

This seem to happen only occasingly for some users. I never saw it for example with my windows 10 system. As you said it doesn't cause any mis-functionality, it is just annoying. It's on the bugfix agenda for next MP2.4 release.

That's correct, there are two options: Using the navigation buttons or the mouse wheel. It's also described in the WIKI for WMC skin here.
Generally it could be helpful to take a quick look into this document to understand the structure incl. navigation.

I tried to reproduce the steps exactly as you described and I think I found the potential issue. I never realized, because I use my mouse wheel and never clicked more than once on the arrows.
Once the navigation arrow is clicked, the vertical main menu scrolls, but the locus is lost from that navigation arrow (you see that from the brightness). So clicking a second time without slightly mousing the mouse to get the focus on the arrow again results into the result you described.

This is definitely not intended behaviour, so I'll take a look to see how this can be improved. Of course the focus should remain on the element.
Meanwhile you need just the slightly move the mouse until the highlight on the arrow is back.

Edit: I checked the code behind and see the difficulty. When the arrow is selected Command="{Command Source={StaticResource HomeMenuModel},Path=MovePrevious}" is executed and sets the focus on the next menu item (in the rectangle focus frame). In that moment the mouse position is ignored. To get the focus back on the arrow, the mouse needs to be moved at least for a few pixel.
Maybe [USER=48291]@Brownard[/USER] has an idea. I could only imagine one solution, that "MovePrevious" sets the focus back on the upper arrow button and "MoveNext" on the lower arrow button by code (is MouseIsUsed = True).

<blockquote data-quote="ge2301" data-source="post: 1285896" data-attributes="member: 145639">This seem to happen only occasingly for some users. I never saw it for example with my windows 10 system. As you said it doesn't cause any mis-functionality, it is just annoying. It's on the bugfix agenda for next MP2.4 release.That's correct, there are two options: Using the navigation buttons or the mouse wheel. It's also described in the WIKI for WMC skin <a href="https://www.team-mediaportal.com/wiki/display/MediaPortal2/WMC" target="_blank">here</a>.Generally it could be helpful to take a quick look into this document to understand the structure incl. navigation.I tried to reproduce the steps exactly as you described and I think I found the potential issue. I never realized, because I use my mouse wheel and never clicked more than once on the arrows.Once the navigation arrow is clicked, the vertical main menu scrolls, but the locus is lost from that navigation arrow (you see that from the brightness). So clicking a second time without slightly mousing the mouse to get the focus on the arrow again results into the result you described.This is definitely not intended behaviour, so I'll take a look to see how this can be improved. Of course the focus should remain on the element.Meanwhile you need just the slightly move the mouse until the highlight on the arrow is back.Edit: I checked the code behind and see the difficulty. When the arrow is selected Command=&quot;{Command Source={StaticResource HomeMenuModel},Path=MovePrevious}&quot; is executed and sets the focus on the next menu item (in the rectangle focus frame). In that moment the mouse position is ignored. To get the focus back on the arrow, the mouse needs to be moved at least for a few pixel.Maybe [USER=48291]@Brownard[/USER] has an idea. I could only imagine one solution, that &quot;MovePrevious&quot; sets the focus back on the upper arrow button and &quot;MoveNext&quot; on the lower arrow button by code (is MouseIsUsed = True).</blockquote>

[QUOTE="ge2301, post: 1285896, member: 145639"] This seem to happen only occasingly for some users. I never saw it for example with my windows 10 system. As you said it doesn't cause any mis-functionality, it is just annoying. It's on the bugfix agenda for next MP2.4 release. That's correct, there are two options: Using the navigation buttons or the mouse wheel. It's also described in the WIKI for WMC skin [URL='https://www.team-mediaportal.com/wiki/display/MediaPortal2/WMC']here[/URL]. Generally it could be helpful to take a quick look into this document to understand the structure incl. navigation. I tried to reproduce the steps exactly as you described and I think I found the potential issue. I never realized, because I use my mouse wheel and never clicked more than once on the arrows. Once the navigation arrow is clicked, the vertical main menu scrolls, but the locus is lost from that navigation arrow (you see that from the brightness). So clicking a second time without slightly mousing the mouse to get the focus on the arrow again results into the result you described. This is definitely not intended behaviour, so I'll take a look to see how this can be improved. Of course the focus should remain on the element. Meanwhile you need just the slightly move the mouse until the highlight on the arrow is back. Edit: I checked the code behind and see the difficulty. When the arrow is selected Command="{Command Source={StaticResource HomeMenuModel},Path=MovePrevious}" is executed and sets the focus on the next menu item (in the rectangle focus frame). In that moment the mouse position is ignored. To get the focus back on the arrow, the mouse needs to be moved at least for a few pixel. Maybe [USER=48291]@Brownard[/USER] has an idea. I could only imagine one solution, that "MovePrevious" sets the focus back on the upper arrow button and "MoveNext" on the lower arrow button by code (is MouseIsUsed = True). [/QUOTE]