When I open satty to take screenshots with walker's menu open, walker always stays above it, how to prevent that?

[nickjj]

Steps to reproduce:

• Launch walker and leave the menu open
• Launch satty with a global hotkey to take an interactive screenshot by dragging a region (I am using niri)
  • Technically the hotkey runs a script that uses grim and slurp to grab the region but it gets piped to satty

Satty's editor will come up behind walker but satty is still focused because if I hit escape it will close satty. I can also hit CTRL+c to copy the image.

The expectation is satty would be overlayed on top of walker's menu so it can be used.

[abenz1267]

No idea. Walker is a layershell tool and renders on the overlay-layer. I dunno what satty does or how you'd "avoid" that. If it's a script you'd just force-close walker before opening satty via walker -q.

[nickjj]

Is there something I can do to debug or provide more information on why it happens?

This is what I see when I launch Walker and then take a screenshot of a region with grim. The app in the back is satty:

Satty has focus, it's just blocked by Walker.

[abenz1267]

You dont seem to understand: this works just like intended. Again: walker is a layer-shell application, just like f.e. a bar.

And because it's on the overlay layer, it will behave like that: overlay.

[nickjj]

That might be true but it creates a user experience that doesn't feel intended.

Currently walker blocks an application from being seen when an application opens in a way that wasn't invoked by a key press or mouse click. Usually walker would hide itself if you hit typical keys to launch something so this doesn't happen a lot.

The workaround is to click satty with the mouse, at that point walker disappears.

[abenz1267]

This is nothing Walker has control over. At all.

[nickjj]

Ok thanks, I wasn't sure if it was, that's why I asked.