3 ms·
I assume the two-level design was the only way to speed up the context menu without breaking compatibility with some existing shell extensions. Specifically, t
by jasomill 3y ago
I assume the two-level design was the only way to speed up the context menu without breaking compatibility with some existing shell extensions.
Specifically, the older design allows shell extensions to register callbacks that must run — in some cases synchronously, on the UI thread — before a context menu displays.
In Windows 11, these "legacy" shell extension context menu callbacks need never run unless "Show more options" is chosen.
The "more options" menu duplicates items in the first because it's identical to the Windows 10 context menu (again, I assume, because compatibility).
- 6510 3y agoI appreciate that they chose to make everything backwards compatible. What you describe actually makes it worse. The new menu takes over 2 seconds to open on my laptop. Enough to load a billion rows and perform calculations on them. It should to take 1 frame. I don't have any windows applications with context menus that even come close to being this slow. If you cant change it the new menu should have the same look as the old one. If clicking "more options" duplicates the same functionality highlight the new options. Have a configuration icon so that you can monitor how much people hate your new design. Anyway, the new design is so bad they might as well put contextual advertisement in it.