Removed delay from taskbar location monitoring

The taskbar location detection process was taking way too long when clicking on the 'view current display' button on the display window. Do I have had to disable the taskbar location detection logic for now until I can work out  way of doing it without waiting for registry changes (as it is done now). This was required in order to be able to detect the taskbar location registry settings so that we could store them to use them later.

This taskbar registry detection doesn't work at present as it is highly unreliable, and it delays the user experience for the other 99% of the time. Its just not worth the effort right now, so parking this for now.

To temporarily disable this being used, I've simply forced the WindowsLibrary fastscan mode to be enabled (fastscan being on means it won't do taskbar location scanning).
This commit is contained in:
Terry MacDonald 2023-01-03 10:07:41 +13:00
parent 181b3b8a9a
commit c641bce5a1
2 changed files with 6 additions and 2 deletions

View File

@ -26,8 +26,8 @@ using System.Resources;
[assembly: Guid("e4ceaf5e-ad01-4695-b179-31168eb74c48")]
// Version information
[assembly: AssemblyVersion("2.5.0.337")]
[assembly: AssemblyFileVersion("2.5.0.337")]
[assembly: AssemblyVersion("2.5.0.338")]
[assembly: AssemblyFileVersion("2.5.0.338")]
[assembly: NeutralResourcesLanguageAttribute( "en" )]
[assembly: CLSCompliant(true)]

View File

@ -500,6 +500,10 @@ namespace DisplayMagicianShared.Windows
private WINDOWS_DISPLAY_CONFIG GetWindowsDisplayConfig(QDC selector = QDC.QDC_ONLY_ACTIVE_PATHS, bool fastScan = true)
{
// Forcing fastscan to stop the taskbar location scanning delaying the user experience
// TODO: Find a replacement method of doing the taskbar location detection. Microsoft may have made things easier in Windows 11 by now....
fastScan = true;
// Prepare the empty windows display config
WINDOWS_DISPLAY_CONFIG windowsDisplayConfig = CreateDefaultConfig();