On Thu, 2017-09-07 at 12:17 -0400, Olivier Fourdan wrote:
> But we dismissed that solution, having different X11 screens is not very
> practical, mutter does not support multiple screens for a start, and
> things like drag'n drop, copy/paste, root properties, etc. all would
> become quite complic
Hi all,
On Wed, Sep 6, 2017 at 1:09 PM, Daniel Stone wrote:
>
> I really wouldn't recommend doing this.
On Thu, Sep 7, 2017 at 10:05 AM, Pekka Paalanen wrote:
>
> I kind of wish I shared your optimism, but I'm thinking more of a death
> by a thousand papercuts kind of situation, not a single bi
Hi nerdopolis,
I'm mostly an outsider here, so just sharing some observations.
On 6 September 2017 at 13:17, nerdopolis wrote:
> I am resending as I messed up one of the commit messages, which resulted
> in a very long subject by mistake. These patches fix issues with Weston
> where it supports
Hi all,
For quite some time now [1] we've been trying to figure out a way to have
mixed DPI, both non-HiDPI capable X11 clients (e.g. xterm) and HiDPI aware
X11 clients coexists on Xwayland.
Typically, the compositor would scale the surface for xterm when on a HiDPI
monitor, but would leave anoth
Weston scales Xwayland surfaces by the output scale, meaning that an
X11 client mapping a window on size (W x H) will actually be:
(W x size) x (H x size)
However, Xwayland ignores the output scale factor when advertising the
monitor size and resolution meaning that an X11 client trying to siz
Hi,
This is actually the 3rd iteration of the xdg-output support patch for
Xwayland.
Changes in this iteration include obvious bug fixes (like binding to the
correct interface actually helps...) and other more important fixes like
waiting for both wl_output and xdg-output done events before actua
The xdg-output protocol aims at describing outputs in way which is
more in line with the concept of an output on desktop oriented systems.
For now it just features the position and logical size which describe
the output position and size in the global compositor space.
This is however much useful
When calibrating touchscreen with weston-calibrator, you can use the mouse to
click on the cross which is recorded as a touch event. This event is used to
compute the final calibration of the touchscreen which results in invalid
touchscreen calibration and broken touchscreen behaviour.
In order to
On Wed, 6 Sep 2017 21:05:33 +0200
Joseph Burt wrote:
> On Wed, Sep 6, 2017 at 4:45 PM, Pekka Paalanen wrote:
> > Popups (e.g. menus) in Wayland use protocol that provides the server
> > with:
> > - the relationship to the window which the popup is for, and
> > - the input event identity that tri
On Thu, Sep 7, 2017 at 9:43 AM, Carsten Haitzler wrote:
> It doesn't have to be specified in the protocol. It is what every compositor
> does because everyone agreed early on that CSD is the default. Weston did it
> then everyone else did it. To be compatible everyone stayed the same. They
> have
On Thu, 7 Sep 2017 08:17:29 +0200 Joseph Burt said:
> On Thu, Sep 7, 2017 at 1:17 AM, Carsten Haitzler wrote:
> >
> > It is CSD in Wayland for Wayland clients, unless somehow compositor and
> > client negotiate something else. In the default case, if a client does not
> > decorate it will not ge
libinput 1.8.2 is now available. Philip's two patches fix the build against
older kernel headers. The rest aren't anything specific to point out,
they're just fixes in various bits of libinput. The only change in
experience is that 2-slot touchpads (e.g. most Lenovos pre kernel 4.12) do
not support
12 matches
Mail list logo
