Re: appId title / Iconic dock launchers

2020-04-12 Thread Damian Ivanov
Hello David, Thanks for the response. >You do have the pid from the client. From that you have the path to >the "actual binary" already. Ah yes, this would probably solve that. >X11 startup notifications. I am not really that familiar with those and they do not seem to be available on wayland.

appId title / Iconic dock launchers

2020-04-12 Thread Damian Ivanov
Hello, Below appears to affect all wayland compositors / environments (and X), respectively any panel / dock that has the ability to pin an application for quick launching when all it's surfaces are closed. wayland api provides the appId / title (IIRC this is the xdg-shell protocol) X api

Re: [question] can multiple compositor share surfaces

2019-05-23 Thread Damian Ivanov
Thank you for the info & link. On Wed, May 22, 2019 at 9:11 AM Simon Ser wrote: > > On Tuesday, May 21, 2019 6:56 PM, Damian Ivanov > wrote: > > Hello Simon, > > > > I imagine many possible usecases for example: > > Two compositors, one crashes

Re: [question] can multiple compositor share surfaces

2019-05-21 Thread Damian Ivanov
be an alternative approach for remote control. Is two compositors sharing surfaces currently technical possible with wayland? On Tue, May 21, 2019 at 4:06 PM Simon Ser wrote: > > On Tuesday, May 21, 2019 2:44 PM, Damian Ivanov > wrote: > > Hello, > > > > Is it possible f

[question] can multiple compositor share surfaces

2019-05-21 Thread Damian Ivanov
Hello, Is it possible for two separate compositors to share the same list of surfaces or connect to the other compositor and receive the surfaces or connect to the wayland-0 file and receive new surfaces as well? Thanks in advance. ___ wayland-devel

Re: xwayland display variable

2019-05-01 Thread Damian Ivanov
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,

Fwd: xwayland display variable

2019-05-01 Thread Damian Ivanov
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: >

xwayland display variable

2019-05-01 Thread Damian Ivanov
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

wayland color depth 256 / 16 / 24 /32

2015-01-07 Thread Damian Ivanov
Hi, What color depth works on wayland? I haven't seen any configuration hint on this one, it would be nice to have 256 possible too, if it's not a total hack or brings an enormous amount of code. Usecase would be, as soon as wine works native on wayland to run legacy 256 only apps. (There are a