-
-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AeroSpace moves CleanShot X's supplementary UI elements to primary monitor #221
Comments
Please try 0.11.0-Beta. 0.11.0-Beta has an improved "popup" detection (suspicious windows without close, minimize, and maximize buttons). Maybe CleanShot is detected as a popup in 0.11.0-Beta If it's not, please capture CleanShot window accessibility debug info with |
I have another bug with cleanshot X (I haven't tried using it with 2 monitors) my issue is when it's recording with CleanShot, there's a floating thing and a dropshadow over areas not recorded and a keyboard shortcut OSD on keyboard strokes. I guess you can the bug in the video I recorded to document another bug in this comment: #121 (comment) if you look closely, I had to press option+j twice to focus the other window, Aerospace is focusing one of CleanShot's "windows" I guess. I tried to reproduce today, it's still there but the menubar doesn't get empty as in the video, instead, it persists the most recent window items in these two or three ghost window switching attempts. The following the debug dump for me trying to move focus between Kitty Terminal and Arc browser with CleanShotX, and I experienced like 2 ghost attempts. debug-windows
|
My issue does not appear to be resolved after the update. However, I must say that your improvements feel significantly better across the application. Here are the logs: @nikitabobko Other noise from iterm
pl.maketheweb.cleanshotx.window.809 windowId: 809
pl.maketheweb.cleanshotx.window.809 workspace: 1
pl.maketheweb.cleanshotx.window.809 treeNodeParent: Workspace(name: '1', isVisible: 'true', isEffectivelyEmpty: 'false')
pl.maketheweb.cleanshotx.window.809 recognizedAsDialog: true
pl.maketheweb.cleanshotx.window.809 AXTitle: Optional()
pl.maketheweb.cleanshotx.window.809 AXRole: Optional(AXWindow)
pl.maketheweb.cleanshotx.window.809 AXSubrole: Optional(AXStandardWindow)
pl.maketheweb.cleanshotx.window.809 AXFocused: Optional(1)
pl.maketheweb.cleanshotx.window.809 AXFullScreen: Optional(0)
pl.maketheweb.cleanshotx.window.809 AXFrame: Optional(<AXValue 0x6000028f79c0> {value = x:0.000000 y:-76.000000 w:1800.000000 h:1169.000000 type = kAXValueCGRectType})
pl.maketheweb.cleanshotx.window.809 AXPosition: Optional(<AXValue 0x6000033c2a30> {value = x:0.000000 y:-76.000000 type = kAXValueCGPointType})
pl.maketheweb.cleanshotx.window.809 AXGrowArea: nil
pl.maketheweb.cleanshotx.window.809 AXMinimizeButton: nil
pl.maketheweb.cleanshotx.window.809 AXDocument: nil
pl.maketheweb.cleanshotx.window.809 AXSections: [
pl.maketheweb.cleanshotx.window.809 ]
pl.maketheweb.cleanshotx.window.809 AXCloseButton: nil
pl.maketheweb.cleanshotx.window.809 AXMain: Optional(1)
pl.maketheweb.cleanshotx.window.809 AXActivationPoint: Optional(<AXValue 0x6000033c2a30> {value = x:-1.000000 y:2629.000000 type = kAXValueCGPointType})
pl.maketheweb.cleanshotx.window.809 AXFullScreenButton: nil
pl.maketheweb.cleanshotx.window.809 AXProxy: nil
pl.maketheweb.cleanshotx.window.809 AXDefaultButton: nil
pl.maketheweb.cleanshotx.window.809 AXMinimized: Optional(0)
pl.maketheweb.cleanshotx.window.809 AXParent: Optional(<AXUIElement Application 0x6000033c2a30> {pid=889})
pl.maketheweb.cleanshotx.window.809 AXTitleUIElement: nil
pl.maketheweb.cleanshotx.window.809 AXCancelButton: nil
pl.maketheweb.cleanshotx.window.809 AXModal: Optional(0)
pl.maketheweb.cleanshotx.window.809 AXZoomButton: nil
pl.maketheweb.cleanshotx.window.809 AXSize: Optional(<AXValue 0x6000033c2a30> {value = w:1800.000000 h:1169.000000 type = kAXValueCGSizeType})
pl.maketheweb.cleanshotx.window.809 AXToolbarButton: nil
pl.maketheweb.cleanshotx.window.809 Ignored: AXChildrenInNavigationOrder, AXChildren, AXRoleDescription
pl.maketheweb.cleanshotx AXRole: Optional(AXApplication)
pl.maketheweb.cleanshotx AXTitle: Optional(CleanShot X)
pl.maketheweb.cleanshotx AXFunctionRowTopLevelElements: [
pl.maketheweb.cleanshotx ]
pl.maketheweb.cleanshotx AXFrame: nil
pl.maketheweb.cleanshotx AXFocusedUIElement: AXUIElement(windowId=809, title="", role="AXWindow", subrole="AXStandardWindow")
pl.maketheweb.cleanshotx AXFrontmost: Optional(1)
pl.maketheweb.cleanshotx AXExtrasMenuBar: Optional(<AXUIElement 0x60000336e850> {pid=889})
pl.maketheweb.cleanshotx AXMainWindow: AXUIElement(windowId=809, title="", role="AXWindow", subrole="AXStandardWindow")
pl.maketheweb.cleanshotx AXFocusedWindow: AXUIElement(windowId=809, title="", role="AXWindow", subrole="AXStandardWindow")
pl.maketheweb.cleanshotx AXMenuBar: Optional(<AXUIElement 0x6000033c2a30> {pid=889})
pl.maketheweb.cleanshotx AXWindows: [
pl.maketheweb.cleanshotx AXUIElement(windowId=810, title="", role="AXWindow", subrole="AXStandardWindow"),
pl.maketheweb.cleanshotx AXUIElement(windowId=809, title="", role="AXWindow", subrole="AXStandardWindow"),
pl.maketheweb.cleanshotx AXUIElement(windowId=808, title="", role="AXWindow", subrole="AXStandardWindow"),
pl.maketheweb.cleanshotx AXUIElement(windowId=807, title="", role="AXWindow", subrole="AXStandardWindow")
pl.maketheweb.cleanshotx ]
pl.maketheweb.cleanshotx AXSize: nil
pl.maketheweb.cleanshotx AXPosition: nil
pl.maketheweb.cleanshotx Ignored: AXChildren, AXChildrenInNavigationOrder, AXEnhancedUserInterface, AXPreferredLanguage, AXRoleDescription, AXHidden
!!! DISCLAIMER !!!
!!! 'debug-windows' command is not stable API. Please don't rely on the command existence and output format !!!
!!! The only intended use case is to report bugs about incorrect windows handling !!!
Debug session finished |
Hi @nikitabobko! This app is amazing! I'd like to ask for insight on this bug
CleanShot 2024-05-08 at 21 34 08@2x (click me)
I experience an issue on CleanShot X where their UI for selecting a monitor is captured and grabbed by AeroSpace and moved to the current focused monitor.
Here's what I think is happening:
The supplementary "Drag to select capture area." button is placed on my secondary display. CleanShot X can notify me that I can optionally use my secondary display. Aerospace recognizes this and moves the button to my primary display, as I just saw it open.
I initially thought this config ↓ would help me, but it does not seem to work for that floating window from the CleanShot UI.
Do you know how to better select this?
The text was updated successfully, but these errors were encountered: