3 ms·
This seems like issues that just shouldn't be allowed to happen. An unresponsive extension, a network drive not answering etc should never need to block the UI
by alkonaut 6y ago
This seems like issues that just shouldn't be allowed to happen. An unresponsive extension, a network drive not answering etc should never need to block the UI - yet it always did in Windows. They really really need to make all such things async and simply show the context menus without the extensions, or show a spinner when explorer wants to show a slow network location.
That the message pump of the explorer windows stop because a server in another country is down must be a design that is extremely hard to change in windows explorer - because they have surely seen this problem.
- gruez 6y ago>They really really need to make all such things async and simply show the context menus without the extensions but then you have another problem: if the system load is high (eg. hard drive is busy), then context menu items would randomly disappear. That's arguably worse than before, because it happens randomly. >or show a spinner you mean this? https://en.wikipedia.org/wiki/Windows_wait_cursor https://en.wikipedia.org/wiki/Windows_wait_cursor
- wtetzner 6y agoI think they meant show a spinner in place of the blocking entry.