You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently it is impossible to recreate a specifically named HEADLESS display that has been destroyed with the unplug command. It would be very useful for sway to respect the naming of a created virtual display and not auto sequence the numbers up.
Use case: create virtual display with pre-defined resolution, location, and frame rate for remote gaming via sunshine/moonlight, and have the ability to destroy and recreate that specific output so it doesn't have to be left up all the time. As of now if I destroy a HEADLESS-1 output and then create a HEADLESS-1 output later it ignores my naming intentions and creates a HEADLESS-2 output.
The text was updated successfully, but these errors were encountered:
bl4ckb0ne
Could you explain reasoning behind this design?
I use sway's headless outputs in conjunction with wayvnc to use my second laptop as an external monitor. And the value increase breaks my waybar's and kanshi's configs whenever I recreate headless output.
Currently it is impossible to recreate a specifically named HEADLESS display that has been destroyed with the unplug command. It would be very useful for sway to respect the naming of a created virtual display and not auto sequence the numbers up.
Use case: create virtual display with pre-defined resolution, location, and frame rate for remote gaming via sunshine/moonlight, and have the ability to destroy and recreate that specific output so it doesn't have to be left up all the time. As of now if I destroy a HEADLESS-1 output and then create a HEADLESS-1 output later it ignores my naming intentions and creates a HEADLESS-2 output.
The text was updated successfully, but these errors were encountered: