View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0018447 | MMW 5 | Main Panel: Toolbars & Menus | public | 2021-10-20 01:11 | 2021-11-15 17:12 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | reopened | ||
| Product Version | 5.0.2 | ||||
| Target Version | 5.0.2 | Fixed in Version | 5.0.2 | ||
| Summary | 0018447: Changing display causes Minimize/Maximize/Close buttons to stop working | ||||
| Description | Changing the display _and_ minimizing/maximizing via the toolbar causes the Minimize/Maximize/Close buttons to stop working. e.g. 1 Set laptop to display only on 'Second screen only' which is a very high resolution screen 2 Run MediaMonkey --> it runs on the second screen 3 WIN-P > Extend to cause the laptop to be the primary screen and the monitor to be the secondary screen --> MM appears on the laptop 4 WIN-P > Second screen only --> MM appears back on the laptop 5 Click 'Minimize' button --> It works as expected 6 Click the MediaMonkey taskbar icon to Maximize/Minimize/Maximize MediaMonkey --> It works as expected 7 Click the 'Minimize' button --> It no longer works (the tooltip displays, but the button doesn't highlight on hover and has no effect on click) | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 2514 | ||||
|
|
Fixed |
|
|
Tested 2513 and this still isn't fixed. i.e. perform step 6 to Maximize then Minimize then Maximize MediaMonkey by pressing the taskbar icon, and subsequent to that, the 'Minimize'/'Maximize'/'Close' buttons no longer work. This is consistently reproducible. |
|
|
Note also that the steps at 0016910 also trigger this issue (dragging and dropping the MM window between monitors after a few other steps). When doing this, not only do the buttons stop working, but the MM window cannot be dragged by the title bar. Also, fyi, while testing this, a few times MM crashed upon closing MM, though I'm not certain that this was the cause. I wasn't able to get a crashlog ID as numerous crash dialogs opened. |
|
|
I've made some changes. Please retest. |
|
|
Verified 2514. |
