[Start11v2] Let us adjust context menu animation time or make it shorter

Since my upgrade to Start11v2 was installed, during opening of any context menu on start panel (right click and choose Task manager, or powerbutton and select Shut down for example) takes the rolll out animation way too longer time and its super anoying. Please let us either turn this animation completely off or make it shorter as it was in Start11v1.  My ideal would be the same time as the context menu takes in Windows in general. 

 

Thank you considerating and thanks once again for this software.

6,634 views 12 replies
Reply #1 Top

Hello,
Sorry to hear you are having issues. But, need to know few things:

  1. Windows full version numbers. Use Winver.exe
  2. Start11 v2 version number.
  3. Which Start11 v2 style you're using?

Thank you,

Basj,
Stardock Community Assistant

Reply #2 Top

I use 

  1.  Windows 11 22H2 (build 22621.2861) Czech language
  2.  Start11 version 2.03 
  3.  Style Windows 10

Since the upgrade to v2 the app seems more laggy and to be honest, I dont really see any improvement or inovation since version 1.42.

The best solution for me would be ability to turn off various animations like the roll up, smooth scrolling etc. just via regedit, nothing fancy. For people that use Windows for work and not for gaming are these things really unnecessary.

Thanks in advance.

Reply #3 Top

Have you tried turn off the "Animate the menu when opening it" in Start Menu->Configuration->Visual appearance?

Thank you,

Basj,
Stardock Community Assistant

Reply #4 Top

Thats very curious as the animations on the menus are quicker in 2.x than they were in 1.x and should be identical to the OS ones.  Note that the desktop menu in Win11 is for some reason not animated at all.

If you create a registry value here HKEY_CURRENT_USER\SOFTWARE\Stardock\Start8\Start8.ini\Start8 called "S11_NoMenuAnimations" of type String and give it a value of "1" and then sign out and in again those animations will be disabled entirely.

In terms of changes there are a huge number of enhancements over 1.4 with 2.0.  Multiple new menu styles, support for tabs, lots of new options for groups, inclusion of filtered folders as groups, new taskbar pins etc.  It should also be noticeably quicker in use.

+1 Loading…
Reply #5 Top

I didn't really notice this before, but the Registry setting above is well received. It really speeds up the Context Menu appearance.

Thank you,

pelaird

Reply #6 Top

Hi, the registry value by Neil Banfield did exactly what I was looking for.

I checked also the menu tip by basj (sorry, its in Czech language) but the animation of context menus was turned off whole time and it didn't have any effect, so thats probably a bug.

 

Also, the roll effect on jumplist selection when clicked on application icon remains, but that's probably handled by Windows itseft so its not a problem of Start11.

Thanks for help.

 

 

Reply #7 Top

Maybe I have found another bug.

If I rightclick the taskbar, it automaticaly highlights the top item although I haven't moved the cursor anywhere yet.

 

Reply #8 Top

I believe that's a Windows 11 default. If you right click the desktop, you will see the top item selected.

Reply #9 Top

No, I have not the first item automatically selected. I have just checked that. This is definitely a bug.

Reply #10 Top

This is what I get when I right click the desktop. As you can see, View is selected which is the top item in the menu. If you have customized the OS to open the "Classic" context menu, then no items will be selected when invoked.

Reply #12 Top

It could be the language difference, but your screen shot is in English. It could also be that I'm running Windows 11 - 22635.2915.

I think the reason for having something selected in the context menu is so you can navigate the options with the keyboard instead of a mouse.

Shift+F10 is the keyboard shortcut to open the context menu for any app that is in focus, and then you can navigate with the arrow keys or the letter shortcuts positioned by the choices.

I really don't think this is a bug, but maybe someone in development could chime in here?