Using Quick Find via keyboard shortcut permanently activates multi select mode

[Noodlefy]

Describe the bug
After using Quick Find via keyboard shortcut (Ctrl+F), I find myself stuck in multi-select mode. I.e., when left-clicking a task (to enter single task focus mode), the task gets selected instead and can only be edited by right-clicking and choosing 'edit'. Multi-select-mode then persists switching projects and editing tasks, and can neither be exited by using Quick Find again, nor by manually activating and then exiting multi-select mode via the three-dot-menu. The only way to fix it seems to be an app restart. This does not happen when clicking the magnifying glass icon, but only when using the keyboard shortcut.
Thank you for this awesome app!

To Reproduce
Steps to reproduce the behavior:

1. Go to any project or pane
2. Use Ctrl+F to enter Quick Find mode
3. Search for keywords, or don't, and then exit Quick Find mode (via Esc or by clicking a search result)
4. Click on any task
5. Task gets selected instead of opened/focused; the multi-selection checkboxes appear on all other tasks of the project, mode can't be aborted

Expected behavior
Left-clicking a task should open it in edit- or single-task-focus mode after using Quick Find via keyboard shortcut, just like when using it via clicking the search icon.

Screenshots
(don't seem necessary)

Desktop:

• OS or DE: Fedora Workstation 43, GNOME 49
• Version 4.17.0 (via Flatpak)

Additional information:
Possibly related to #2116?

[pgrit]

This seems to be indeed the same issue as #2116 Did some digging and found the root cause:

planify/src/MainWindow.vala

Lines 433 to 437 in 1344b5c

	key_controller.key_released.connect ((keyval, keycode, state) => {
	if (keyval == Gdk.Key.Control_L || keyval == Gdk.Key.Control_R) {
	Services.EventBus.get_default ().ctrl_key_pressed = false;
	}
	});

This never triggers if a shortcut involving Ctrl opens a dialog. (Quick find, preferences, and ctrl-v to add a task)
Pressing and releasing Ctrl again, while the main window has focus, resolves the incorrect state (until the next shortcut opens a dialog, of course).

I suppose a quick and dirty fix is to simply react to this event in all dialogs. But maybe there is a more elegant solution?