feat: Allow Mouse to Follow Cursor onto Empty Workspace and Simulate Mouse Click to Facilitate Launching Flow Launcher Search #557
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Investigating exception being thrown when coming out of the lock screen. Looks like |
…nContainerCommand and simulate Mouse Click when this is the case Update the .where() and .subscribe() to allow Workspace containers and logic for invoking SimulateMouseClickOnContainerCommand Removed SimulateMouseClickOnContainer and moved logic into CenterCursorOnContainerHandler with type check for Workspace Reverted .Subscribe back to original state. Removed empty lines that were added.
blampewpew
force-pushed
the
add-simulate-mouse-click-empty-workspace
branch
from
4dce4b6
to
f609e58
Compare
|
I was running an old build where I didn't add the check in the It's good. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Here's my attempt to address Issue #554 which allows Flow Launcher to launch search on an empty workspace as well as other programs that do not like that funky state of a Workspace that has been focused but not clicked (e.g., Windows Screenshot Tool).
I'm an avid user of i3 and am very happy that this project exists which allows me to have nearly the same experience on my Windows machine. Thanks and kudos to the devs who started this!
Overview of Changes:
FocusedContaineris aGlazeWM.Domains.Workspaces.Workspacetype container. I modified the.Where()on WmStartup.cs:123 to also invoke theCenterCursorOnContainerCommandwhen this happens. This allows for the cursor to follow onto an empty workspace.(I can't even initiate the Windows Screenshot tool (WIN+SHIFT+S) to get a full screenshot of the highlighted workspace number and the title of the last window on my polybar when in this state so it's not just Flow Launcher that's having issues.)
When I click on the empty workspace, that seems to effectively focus the workspace and the polybar title is cleared and I can launch Flow Launcher (and the Windows Screenshot tool).
SendInputalong with the required structs for Mouse Input and added that to theCenterCursorOnContainerHandlerwith a check that the container is of typeWorkspace.