rain

> This workaround works fine for me: > > ``` > alt - l : yabai -m window --toggle topmost; yabai -m window --toggle topmost > ``` Can confirm this...

That works for pop ups from those apps themselves but causes other problems such as system pop ups (spotlight / autocorrect + autocomplete suggestions / mail notifications) forcing a window...

> This is now basically possible with multiple PIP windows (set to high priority, shadowless, title-less) as PIP windows now remember their location and can be auto-started as well. Still,...

> (note: virtual screens are also fully scriptable now - so it is quite easy to create a script that turns on virtual screens, sets main screen in the preferred...

Got the chance to try it out. With two displays, Left and Right, 16:9, this script automatically positions them on my real display side by side. ```sh #!/bin/sh REAL_DISPLAY=LS49AG95 VIRTUAL_DISPLAY_1=Left...

> Nice work! > > Hmm. I can add an additional option when the window level is set to absolute to make the PIP window click-thru (so the window itself...

> Regarding the changes to the XML model files, I would like to see verification using the [check_environments_match()](https://github.com/Farama-Foundation/Gymnasium/blob/main/gymnasium/utils/env_match.py) function, for multiple `mujoco` versions (100k steps per version should be enough)...

> In general it is best practice to have pull requests contain one type of change. And I'm sensitive to the changes to the XML model files as they can...

As requested, I added a higher-level script in my [xml-changes-verification](https://github.com/evangelos-ch/Metaworld/tree/xml-changes-verification) branch that runs the checking script for all MuJoCo versions between 2.2.0 and 2.3.7. The script passes for all 2.3.X...

Hi, thank you for looking into my issue! Indeed, in the minimal model I've provided there is just the robot arm because the rest of the objects (like the table...