On Mon, 3 Jun 2019 18:53:28 +0100
adlo wrote:
> > On 1 May 2019, at 10:34, Pekka Paalanen wrote:
> >
> > it is all just the normal Wayland protocol exchange but with a new
> > interface of your own design. I'm not sure if there is a really
> > minimal example, but I'll list at least some.
> >
> On 1 May 2019, at 10:34, Pekka Paalanen wrote:
>
> it is all just the normal Wayland protocol exchange but with a new
> interface of your own design. I'm not sure if there is a really
> minimal example, but I'll list at least some.
>
> One example of such private protocol extension is
> https:
On Mon, 03 Jun 2019 at 14:17:21 +0300, Pekka Paalanen wrote:
> For
> a test suite, you could use an environment variable to override the
> default search path, but for a manual launch that is a bit more
> inconvenient.
This is the solution that is generally recommended
in the GLib/GTK/GNOME stack
On Mon, 3 Jun 2019 08:38:12 +0100
adlo wrote:
> How do I ensure my client will still launch no matter what directory
> I run my compositor from? How do I get the absolute path of my client?
Hi,
you install the client to a specific path. You get the path from your
build system.
> Also, how do I
> On 1 May 2019, at 10:34, Pekka Paalanen wrote:
>
> On Wed, 1 May 2019 03:24:04 +0100
> adlo wrote:
>
> it is all just the normal Wayland protocol exchange but with a new
> interface of your own design. I'm not sure if there is a really
> minimal example, but I'll list at least some.
>
> One
> On 1 May 2019, at 10:34, Pekka Paalanen wrote:
>
> The privacy of the protocol extension, the installed wayland global
> really, is achieved in
> https://gitlab.freedesktop.org/wayland/weston/blob/master/desktop-shell/shell.c#L4366
>
>shell->child.client = weston_client_start(shell->compos
> On 17 May 2019, at 09:10, Pekka Paalanen wrote:
>
> Hi,
>
> you forgot to use 'name'.
>
Thanks, that's fixed it!
> you should not include that in a
> client program.
>
Guess what I did :p
Regards
adlo
___
wayland-devel mailing list
wayland-deve
On Fri, 17 May 2019 11:10:20 +0300
Pekka Paalanen wrote:
> On Fri, 17 May 2019 03:45:10 +0100
> adlo wrote:
>
> > On Thu, 2019-05-16 at 11:58 +0300, Pekka Paalanen wrote:
> > >
> > > you should run an actual event loop in the client, which will then
> > > flush your requests to the composito
On Fri, 17 May 2019 03:45:10 +0100
adlo wrote:
> On Thu, 2019-05-16 at 11:58 +0300, Pekka Paalanen wrote:
> >
> > you should run an actual event loop in the client, which will then
> > flush your requests to the compositor. Your issue seems to be a
> > missing
> > flush.
> >
> > See also https:
On Thu, 2019-05-16 at 11:58 +0300, Pekka Paalanen wrote:
>
> you should run an actual event loop in the client, which will then
> flush your requests to the compositor. Your issue seems to be a
> missing
> flush.
>
> See also https://wayland.freedesktop.org/extras.html "Protocol
> dumpers"
> and
On Thu, 16 May 2019 05:59:20 +0100
adlo wrote:
> On Wed, 2019-05-01 at 12:34 +0300, Pekka Paalanen wrote:
> >
> > it is all just the normal Wayland protocol exchange but with a new
> > interface of your own design. I'm not sure if there is a really
> > minimal example, but I'll list at least som
On Wed, 2019-05-01 at 12:34 +0300, Pekka Paalanen wrote:
>
> it is all just the normal Wayland protocol exchange but with a new
> interface of your own design. I'm not sure if there is a really
> minimal example, but I'll list at least some.
>
> One example of such private protocol extension is
>
> On 10 May 2019, at 08:48, adlo wrote:
>
> I put a call to weston_log() in my server-side bind function and then called
> wl_global_create() in my client. I was expecting to see my log entry printed
> to the screen but I got nothing.
>
> What could be going on?
I meant wl_registry_bind(), no
On 9 May 2019, at 10:43, adlo wrote:
>> On 1 May 2019, at 10:34, Pekka Paalanen wrote:
>>
>> it is all just the normal Wayland protocol exchange but with a new
>> interface of your own design. I'm not sure if there is a really
>> minimal example, but I'll list at least some.
>>
>> One example
> On 1 May 2019, at 10:34, Pekka Paalanen wrote:
>
> it is all just the normal Wayland protocol exchange but with a new
> interface of your own design. I'm not sure if there is a really
> minimal example, but I'll list at least some.
>
> One example of such private protocol extension is
> https:
On Wed, 2019-05-01 at 12:34 +0300, Pekka Paalanen wrote:
>
> it is all just the normal Wayland protocol exchange but with a new
> interface of your own design. I'm not sure if there is a really
> minimal example, but I'll list at least some.
>
> One example of such private protocol extension is
>
On Tue, 7 May 2019 05:24:19 +0100
adlo wrote:
> > On 1 May 2019, at 10:34, Pekka Paalanen wrote:
> >
> > Hi adlo,
> >
> > it is all just the normal Wayland protocol exchange but with a new
> > interface of your own design. I'm not sure if there is a really
> > minimal example, but I'll list at
> On 1 May 2019, at 10:34, Pekka Paalanen wrote:
>
> Hi adlo,
>
> it is all just the normal Wayland protocol exchange but with a new
> interface of your own design. I'm not sure if there is a really
> minimal example, but I'll list at least some.
>
> One example of such private protocol extensi
On Fri, 2019-05-03 at 11:02 +0100, adlo wrote:
> > On 3 May 2019, at 10:20, Pekka Paalanen
> > wrote:
> >
> > your Makefile.am needs the rules to generate the headers and .c
> > files.
> >
>
> I tried copying an edited Makefile.am from the wayland-protocols git
> repository, but it complained a
> On 3 May 2019, at 10:20, Pekka Paalanen wrote:
>
> your Makefile.am needs the rules to generate the headers and .c files.
>
>>
I tried copying an edited Makefile.am from the wayland-protocols git
repository, but it complained about GNU-isms. Is there anything else I need to
do other than j
On Fri, 03 May 2019 05:40:46 +0100
adlo wrote:
> On Wed, 2019-05-01 at 12:34 +0300, Pekka Paalanen wrote:
> >
> > it is all just the normal Wayland protocol exchange but with a new
> > interface of your own design. I'm not sure if there is a really
> > minimal example, but I'll list at least som
On Wed, 2019-05-01 at 12:34 +0300, Pekka Paalanen wrote:
>
> it is all just the normal Wayland protocol exchange but with a new
> interface of your own design. I'm not sure if there is a really
> minimal example, but I'll list at least some.
>
> One example of such private protocol extension is
>
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
> 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 private protocol extension for the
> special bits you need.
W
On Mon, 29 Oct 2018 04:46:02 +
adlo wrote:
> How do I run a GTK/GDK main loop from inside a libweston compositor?
> If I want to use functions such as gdk_display_get_default () to get
> my compositor's GdkDisplay, how do I guarantee that my compositor's
> display exists?
Hi,
the only opini
How do I run a GTK/GDK main loop from inside a libweston compositor? If I want
to use functions such as gdk_display_get_default () to get my compositor's
GdkDisplay, how do I guarantee that my compositor's display exists?
Regards
adlo
___
wayland-deve
26 matches
Mail list logo
