Skip to content
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

"visible" is set to 1 for hidden apps #616

Closed
d-miketa opened this issue Jul 19, 2020 · 1 comment
Closed

"visible" is set to 1 for hidden apps #616

d-miketa opened this issue Jul 19, 2020 · 1 comment
Labels
bug Something isn't working

Comments

@d-miketa
Copy link

On Mac OS one can either minimise a window (Cmd+M by default) or hide the application altogether (Cmd+H). Whereas yabai -m query --windows --space [n] shows if a window is minimised, it seems to be agnostic about whether the app is hidden or not (which, in this case, it is):

{
        "id":11256,
        "pid":8062,
        "app":"WhatsApp",
        "title":"WhatsApp",
        "frame":{
                "x":15.0000,
                "y":576.0000,
                "w":856.0000,
                "h":529.0000
        },
        "level":0,
        "role":"AXWindow",
        "subrole":"AXStandardWindow",
        "movable":1,
        "resizable":1,
        "display":1,
        "space":1,
        "visible":1,
        "focused":0,
        "split":"none",
        "floating":0,
        "sticky":0,
        "minimized":0,
        "topmost":0,
        "opacity":0.9000,
        "shadow":1,
        "border":1,
        "zoom-parent":0,
        "zoom-fullscreen":0,
        "native-fullscreen":0
}

Here visible=1 simply indicates that the space (2) is visible on its associated display (1). I think it'd make more sense if visible=0 if the app is hidden; failing that, there should be a hidden key.

The following Applescript snippet works as I'd expect:

target_app="WhatsApp"
osascript -e "tell application \"System Events\" to get visible of first process whose name is \"${target_app}\" "
false
@koekeishiya
Copy link
Owner

I am aware of this inconsistency, but waiting to fix it until I revise the output of the query system.

@koekeishiya koekeishiya added the bug Something isn't working label Jul 22, 2020
@koekeishiya koekeishiya added the addressed on master; not released Fixed upstream, but not yet released label Feb 14, 2021
@koekeishiya koekeishiya added the-future I never think of the future - it comes soon enough. and removed addressed on master; not released Fixed upstream, but not yet released labels May 6, 2021
@koekeishiya koekeishiya added the addressed on master; not released Fixed upstream, but not yet released label Nov 18, 2021
@koekeishiya koekeishiya removed addressed on master; not released Fixed upstream, but not yet released the-future I never think of the future - it comes soon enough. labels Mar 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants