Alexander Courtis

That's fantastic! There are a few options available: * separate executables communicating via IPC * wdisplays (maybe way-displays-gui?) and way-displays are separately distributed * distributed together * completely merged using...

wdisplays allows addition of custom modes. This functionality could be added to way-displays.

Hello @redtide thank you for your recent work and interest! > it's a great thing to make them a single project Yes. We don't have to make any decisions immediately;...

> I was talking about from "wdisplays" POV, where the "UI" part is interactive, but I don't have a clear view of the situation with the two merged. There are...

Some interop options: * way-displays / wdisplays one process * separate processes communicating via * `cfg.yaml` read/write * IPC

I think all the pieces are there, we just need people time to build it.

See https://github.com/artizirk/wdisplays/issues/21

> `WARNING: 2560x1440@60Hz (59,951mHz) already specified for 'DP-3', ignoring 2560x1440@240Hz (239,950mHz) (preferred)` This one is "harmless", merely indicating that the monitor advertised two preferred modes. The warning message is misleading...

way-displays was indeed getting stuck after cancellation, with the get kicking it into action. I'd be most grateful if you could test a fix, which retries after a cancellation, a...

Well, that looks pretty good, thanks for testing. The last cancellation: was the position change correctly applied? FYI: you can disable VRR setting for known monitor that don't support it...