On Wed, 1 May 2019 at 13:00, Graeme Gill wrote:
>
> Erwin Burema wrote:
>
> Hi,
>
> > 1) Will always be a single solid color, so no need for the full
> > wl_buffer/wl_surface interface
>
> you don't know that, as it's up to the calibration and profiling
> application. It may well want to paint gui
Thanks Simon,
Ditto.
On Wed, May 1, 2019 at 3:00 PM Simon McVittie wrote:
>
> On Wed, 01 May 2019 at 14:30:52 +0300, Damian Ivanov wrote:
> > export WAYLAND_DISPLAY=wayland-1
> > GDK_BACKEND=x11 gedit //starts on wayland-0
>
> If you are using GDK_BACKEND=x11, then gedit is not acting as a native
Thank you for the great explanation Scott!
I needed to change:
DISPLAY=:2 to connect to wayland-1,
DISPLAY=:1 was connecting to wayland-0
and DISPLAY=:0 to nothing
On Wed, May 1, 2019 at 2:59 PM Scott Anderson
wrote:
>
> On 1/05/19 11:30 pm, Damian Ivanov wrote:
> > Hello,
> >
> > Is it somewh
On Wed, 01 May 2019 at 14:30:52 +0300, Damian Ivanov wrote:
> export WAYLAND_DISPLAY=wayland-1
> GDK_BACKEND=x11 gedit //starts on wayland-0
If you are using GDK_BACKEND=x11, then gedit is not acting as a native
Wayland app, so it will not look at WAYLAND_DISPLAY. Instead, it will be
acting as an
On 1/05/19 11:30 pm, Damian Ivanov wrote:
Hello,
Is it somewhere documented how Xwayland applications are choosing
which compositor to display on? e.g 2 compostiors (1 nested or on
another VT)
wayland-0 and wayland-1
export WAYLAND_DISPLAY=wayland-1
GDK_BACKEND=x11 gedit //starts on wayland-0
I
Hello,
Is it somewhere documented how Xwayland applications are choosing
which compositor to display on? e.g 2 compostiors (1 nested or on
another VT)
wayland-0 and wayland-1
export WAYLAND_DISPLAY=wayland-1
GDK_BACKEND=x11 gedit //starts on wayland-0
If it's not documented how to do it?
Thank yo
Erwin Burema wrote:
Hi,
> 1) Will always be a single solid color, so no need for the full
> wl_buffer/wl_surface interface
you don't know that, as it's up to the calibration and profiling
application. It may well want to paint guide graphics for the positioning
of the instrument. It could want t
On Wed, 1 May 2019 03:24:04 +0100
adlo wrote:
> > On 29 Oct 2018, at 09:33, Pekka Paalanen wrote:
> >
> > the only opinionated advice I can give you is don't do it. Instead, put
> > the GTK stuff in a separate process, let your compositor fork & exec
> > it, and talk to it through your own priv
---
unstable/xdg-output/xdg-output-unstable-v1.xml | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/unstable/xdg-output/xdg-output-unstable-v1.xml
b/unstable/xdg-output/xdg-output-unstable-v1.xml
index ccbfe1c..3176520 100644
--- a/unstable/xdg-output/xdg-output-unstable
On Wed, 24 Apr 2019 10:07:47 -0700
Chia-I Wu wrote:
> Hi,
>
> Can you commit this patch for me, if all looks good?
Hi Chia-I,
I was almost already pushing this, but Daniel said he wants to have
a good look first.
Thanks,
pq
> On Wed, Apr 17, 2019 at 9:41 AM Chia-I Wu wrote:
> >
> > I hope
10 matches
Mail list logo