by drakinite » Fri Nov 12, 2021 4:42 pm
That's a good question, and yes, it's difficult to view the HTML & CSS stylings for menus; but it's possible if you use the remote debugging feature in a browser (connect to localhost:9222).
http://files.drakinite.net/2021-11-12_16-38-23.mp4
You can force click events by using the devtools' screencast feature. As long as you don't click on the
real MediaMonkey window, the menus will persist, allowing you to examine them. It's sometimes difficult to get the clicks to register (as you can see with the delay in the screen recording), but you can get it with enough tries.
FYI: Each submenu is its own "window", and you can identify it by its "wndID" attribute in the main remote-debugging page. The first menu to display is the one with the lowest number before the underscore, and any subsequent menus are created as-needed, with higher subsequent IDs. Once you restore the real MediaMonkey window, the popup menus should disappear.
That's a good question, and yes, it's difficult to view the HTML & CSS stylings for menus; but it's possible if you use the remote debugging feature in a browser (connect to localhost:9222). http://files.drakinite.net/2021-11-12_16-38-23.mp4
You can force click events by using the devtools' screencast feature. As long as you don't click on the [i]real[/i] MediaMonkey window, the menus will persist, allowing you to examine them. It's sometimes difficult to get the clicks to register (as you can see with the delay in the screen recording), but you can get it with enough tries.
FYI: Each submenu is its own "window", and you can identify it by its "wndID" attribute in the main remote-debugging page. The first menu to display is the one with the lowest number before the underscore, and any subsequent menus are created as-needed, with higher subsequent IDs. Once you restore the real MediaMonkey window, the popup menus should disappear.