Context menu and edit path delay/lag

[Łukasz Samek]

Anyone experiences delay with these elements?

1. Edit path takes few seconds to load up every time

2. Context menu shows loading circle just before loading up - this looks kind of clunky. There's also 0.5-1 sec delay. I've disabled every extra menu item but no avail.

[Milos Paripovic]

There is a lag for Path Edit and it will be rewritten soon. It shouldn't lag as there isn't anything CPU heavy going on there so I need to investigate

Context menu lags the most on the first right-click in a session (all functions of dotnet programs run faster after the first time they are used after each start).

It is faster when Settings>Other>Wait for all items before showing context menu is off

Did you disable extra menu items in OC or in Windows using ShellMenuView https://www.nirsoft.net/utils/shell_menu_view.html

In OC it is just hiding them but they still contribute on loading times and it is all up to items to respond - I have some PCs where menu shows up instantly or a one from 2011 where it takes 3s because I have 200 programs on it.

In v2 there was a custom menu that was showing instantly regardless, because it didn't show additional 3rd party context menu items. Something like what Windows 11 is trying to do, hiding all in "Show more" menu, but people didn't like it. The only other way is being at mercy of the system and all the badly written extensions programs put in there

[Łukasz Samek]

I've disabled everything but it's still not instant. That loading circle probably contribute to the perception of the lag, even if it shows in a split of a second. It's not such a big deal, it's just triggers 
 my OCD a little. 

[Milos Paripovic]

The menu is invoked by system and it shows also the loading cursor (I think I can't remove that). My future plans are rewriting the menu, and if that doesn't improve things enough even for that machine with 200 programs, then add an additional menu type that wouldn't rely on Windows and it will open instantly - that one will be optional because it will have the same issues as the one in Windows 11 where it hides non-native items in an additional submenu so I already know it won't be suitable for large percentage of users.