Ferdinand Bachmann

> as mentioned in the referenced comment in [#64](https://github.com/Ferdi265/wl-mirror/issues/64) above, a similar issue seems to also sometimes occur in River. The other user who had a similar bug on River...

> [3788555.297] {Display Queue} wl_display#1.delete_id(34) this is the last line showing when it hangs sometimes the number in the far right brackets is 35 or 30 and its almost always...

> > > [3788555.297] {Display Queue} wl_display#1.delete_id(34) this is the last line showing when it hangs sometimes the number in the far right brackets is 35 or 30 and its...

Looking at the code I have a hunch that the render timing in wl-mirror is wrong. That's not the core issue here though, since that only impacts performance usually and...

> I agree wholeheartedly. This is why I am a bit concerned about the implementation of this as a _sway_ project. To my understanding this should rather be a _wayland_...

> I've delved into this rabbit hole before, from my experience implementing this into the wayland side has the downside that clients are not aware of this split, meaning that...

> I think a main challenge here is to completely override any access to physical screen sizes and also consider what possible trade-offs are in this case. > > For...

> Changing resolution via `wlr-output-management` would then need to be implemented accordingly as well, not sure how to do this properly. Looking at wlr-output-management, this should probably work fine if...

Thanks for implementing that. Please note that the way you implemented this (just taking the libusb device serial number) is not extremely useful for flashing: Case 1: Two picos are...

TL;DR: if `-f` is fixed to work with `--serial`, I'm 100% in favor of this PR being merged ASAP. This is a much simpler solution to mine, and makes serial...