FancyZones: improve windows and apps filtering

[bzoz]

Summary of the Pull Request

Unifies the way windows are considered "interesting" by FancyZone. Before the change, WinKey + arrows would use a different method than dragging. This PR makes both use the WinKey + arrows method.

Cleans up FancyZones Settings.cpp by removing m_configStrings variable. Contrary to its name it was used to create color picker control.

Adds a multiline option to the text input to settings. Uses this to provide the user with a way to exclude certain apps from snapping to zones.

PR Checklist

• Applies to PowerToys breaks GreenShot screenshotting software + workaround #531 SolidWorks Does Not Snap to Zones #515 Shift Drag Doesn't Work With Unreal Engine #500 Cisco webex windows don't snap to a zone. #496 FancyZones does not work for 1Password window while pressing SHIFT #479
• CLA signed. If not, go over here and sign the CLA

Validation Steps Performed

Manual

[enricogior]

@bzoz
I haven't done a full review yet, my first consideration is about a possible optimization for the new and more complex IsInterestingWindow().
I've noticed that IsInterestingWindow() it's called very frequently by this code:

PowerToys/src/modules/fancyzones/dll/dllmain.cpp

Lines 277 to 289 in c4fc673

	case EVENT_OBJECT_UNCLOAKED:
	case EVENT_OBJECT_SHOW:
	case EVENT_OBJECT_CREATE:
	{
	if (data->idObject == OBJID_WINDOW)
	{
	if (IsInterestingWindow(data->hwnd))
	{
	m_app.as<IFancyZonesCallback>()->WindowCreated(data->hwnd);
	}
	}
	}
	break;

and it's quite common that it is called multiple times in a row for the same HWND.
So what about caching the last HWND result?

[bzoz]

@enricogior I was thinking the same thing, but from a quick test, it looks like the performance impact is minimal. That said, I think we do need some caching.

My idea is to keep a cache of about 64 last HWNDs queries, but also check (using GetWindowThreadProcessId) if the HWND still belongs to the same process as when it was added to the cachce.

[enricogior]

@bzoz are you planning to add the caching in this PR or do you prefer to merge this one and add the caching later on?

[enricogior]

@bzoz
can you make the description text to not wrap at the multiline control size but extend to the full size of the window?

[enricogior]

This is a partial match, for example if the excluded app is notepad and the target app is notepad++.exe, it will disable fancyzones for notepad++.exe, this may generate confusion to the users.
We either force the users to add the application extension, like in notepad.exe, or handle it in the code.

[bzoz]

Requiring an exact match would also be confusing, the app binary file name does not really have match exactly the app name. The best solution would probably be if a user can click on a window to disable it, maybe by using the system menu hook from #677?

[enricogior]

At least we need to document how it works, so a user may try to use the extension in order to avoid partial matching.
The FancyZones readme is outdated anyway and requires to be updated.
So let's open an issue for the Readme update after this PR is merged.

[bzoz]

Fixed the label size and added caching of the HWNDs, PTAL

[bzoz]

Updated, PTAL

[enricogior]

Great work!