View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0021196 | MMW 5 | Main Panel | public | 2024-09-09 18:55 | 2024-11-20 02:31 |
Reporter | Ludek | Assigned To | |||
Priority | urgent | Severity | major | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Product Version | 5.1 | ||||
Target Version | 5.1 | Fixed in Version | 5.1 | ||
Summary | 0021196: MediaMonkey does not get focus on startup (regression) | ||||
Description | Started with builds 3044 - 3051: 1) Start MediaMonkey => window does not get focus until it is clicked | ||||
Tags | No tags attached. | ||||
Fixed in build | 3055 | ||||
related to | 0020967 | assigned | michal | Issue with tab key when popup is opened in grid |
related to | 0021195 | assigned | rusty | Further improvements to TAB order / Keyboard-only usage of MMW |
related to | 0020933 | closed | michal | Issues with TAB order and Keyboard-only usage of MM 2024 |
related to | 0021345 | resolved | petr | In certain evironments, upgraded MM installations interfere with Windows Explorer and other apps (regression) |
related to | 0021364 | assigned | petr | MMW (debug) often fails to respond to TAB key on launch |
related to | 0021370 | closed | michal | Focus : MM doesn't respond to ARROW keys on startup if multiple TABs are open |
|
Fixed |
|
FYI: This was not merged to 5.1 SVN branch.. |
|
Merged |
|
Verified 3052. |
|
This doesn't seem to be working as expected in 3054 for keyboard-only users: 1 Click Music [Browser] collection node/view 2 Restart MMW 3 Press Right-Arrow or TAB to view what's in focus / change focus --> UI doesn't respond! |
|
Fixed |
|
Verified on 3055, both tab and right key work as expected when Collection node is selected element on close. |
|
Although the TAB key is working correctly on startup, I'm still having issues when using the ARROW key. e.g. 1 Click Music [Browser] collection node/view 2 Restart MMW 3 Press Right-Arrow to view what's in focus / change focus --> UI never responds (even when I try left, up, down arrows, there's no focus shown in the browser view at all!!) 4 Press TAB --> Seekbar comes into focus as expected 5 Press SHIFT + TAB --> Focus shifts back to the Browser view (even though at step 3 there was no indication that it was actually in focus) Note: this also occurs for the Music > All files view (and I suspect for other views as well). It would be a relatively minor issue if focus would initially be on the tree node (in which case the user could TAB 2x to get to the tracklist (instead of TAB and then SHIFT+TAB as is currently the case). |
|
I cannot reproduce. For me focus is always on Media Tree after point 2) and arrow down shows key-focused state of Media Tree node. Could you record video? Maybe there is some detail which is causing this. Btw. default focus change key is TAB, arrows will work only on some controls. |
|
hmm... not sure why but I can no longer replicate this. Closing for now and will re-open if I see it again. |
|
This issue again a regression in build 3079: 1 launch MediaMonkey --> MM window appears 2 Press TAB or Arrow keys --> MM isn't in focus! |
|
Re-resolving. It turns out that this is actually a distinct bug: when MM is launched into certain nodes (e.g. Playlists > PlaylistName) focus switching using TAB doesn't work consistently. Tracking separately. |
|
Re-opening. I retested 3078 and it really is a regression in 3079 (the bug never occurs in 3078). In 3079, whether the issue occurs appears to be related to a combination of the node that MM launches into and timing of pressing the TAB key: - Pressing the TAB key immediately after launching MM --> the issue always occurs - Pressing the TAB key a few seconds after the UI renders --> the bug may or may not occur depending on the node (it seems to be more likely to occur for nodes such as Music > All files [list] that contain a lot of tracks Note: the issue seems much more likely to occur when dbgview isn't running. Shared debug log/video. |
|
Re-resolving. The issue wasn't occurring in 3078 because dbgview was running. When dbgview isn't running I'm able to replicate in 3078 as well. Tracking at 0021364 |
|
Aside from the fact that MM sometimes fails to respond to TAB keys in recent debug builds (tracked at 0021364), build 3080 experiences a failure to respond to ARROW keys on launch in both debug and regular builds! This occurs whether launching into browser, list, or grid views. Note: - it occurs for me (running Windows 11), but not for Petr (on Windows 10). - when I do a clean install, MM launches with focus on the tree, and it works correctly. But on my regular install, focus rests somewhere in between the tracklist and the Playing list, which may be the root of why it fails to work properly. |
|
So I think I've discovered one way of triggering problem: 1 Do a clean install of MM and scan 500 files 2 Restart MM 3 Use the ARROW keys --> the bug doesn't occur 4 Initiate playback of some tracks and stop playback after a few tracks 5 Restart MM 6 Press the TAB key --> the bug occurs! So perhaps the existence of multiple highlighted items in the UI can somehow cause this? Note: there's more to the story though, since if I delete the Playing list from my regular (non-clean) installation, and restart MM, the bug still occurs :-( EDIT: Michal found the root cause--multiple Tabs! |
|
Moved the multi-tab issue to 0021370. |
|
Reverified 3081. |