On Wed, 2017-02-08 at 13:20 -0500, Olivier Fourdan wrote:
> Yeah... It's all confusing! Sorry!
>
> Those are the two patches:
>
> https://patchwork.freedesktop.org/patch/137446/
> https://patchwork.freedesktop.org/patch/137635/
Merged:
remote: I: patch #137446 updated using rev
Hey Adam,
- Original Message -
> On Wed, 2017-02-08 at 09:23 +0100, Olivier Fourdan wrote:
> > Previously, we would swap the width/height of the Xwayland output based
> > on the output rotation, so that the overall screen size would match the
> > actual rotation of each output.
>
> This
On Wed, 2017-02-08 at 09:23 +0100, Olivier Fourdan wrote:
> Previously, we would swap the width/height of the Xwayland output based
> on the output rotation, so that the overall screen size would match the
> actual rotation of each output.
This series makes sense, but I'm a little lost on which
Previously, we would swap the width/height of the Xwayland output based
on the output rotation, so that the overall screen size would match the
actual rotation of each output.
Problem is the RandR's ConstrainCursorHarder() handler will also apply
the output rotation, meaning that when the output
