On Mon, 06 Oct 2014 11:43:56 +0300
Rémi Denis-Courmont wrote:
> Le 2014-10-06 11:26, Pekka Paalanen a écrit :
> >> > 4 or higher as a wl_surface version 3? If not, I cannot rely on
> >> > 'wl_proxy_get_version(surface) >= 2'...
> >>
> >> Changing the semantics[5] of wl_surface.damage is a good ex
On Mon, 06 Oct 2014 13:09:05 +0300
Rémi Denis-Courmont wrote:
> Le 2014-10-06 12:52, Pekka Paalanen a écrit :
> > Could this be solved (completely?) by saying that libraries that take
> > existing wl_proxy objects such that they
> > a) set up listeners, or
> > b) create new wl_proxies from it and
On Oct 6, 2014 12:45 AM, "Pekka Paalanen" wrote:
>
> Re-adding CCs and some more...
>
> On Mon, 06 Oct 2014 09:17:41 +0300
> Rémi Denis-Courmont wrote:
>
> > Hello,
> >
> > Le 2014-10-06 03:29, Jason Ekstrand a écrit :
> > > Remi,
> > > While this would probably be nice, your approach isnt go
Le 2014-10-06 12:52, Pekka Paalanen a écrit :
Could this be solved (completely?) by saying that libraries that take
existing wl_proxy objects such that they
a) set up listeners, or
b) create new wl_proxies from it and set their listeners;
need to also offer API to tell which versions of the passe
Le 2014-10-06 11:26, Pekka Paalanen a écrit :
> 4 or higher as a wl_surface version 3? If not, I cannot rely on
> 'wl_proxy_get_version(surface) >= 2'...
Changing the semantics[5] of wl_surface.damage is a good example
where
this would fail indeed. If a library only knows up to version 3, but
On Mon, 6 Oct 2014 10:45:14 +0300
Pekka Paalanen wrote:
> Re-adding CCs and some more...
>
> On Mon, 06 Oct 2014 09:17:41 +0300
> Rémi Denis-Courmont wrote:
>
> > Hello,
> >
> > Le 2014-10-06 03:29, Jason Ekstrand a écrit :
> > > Remi,
> > > While this would probably be nice, your approac
Re-adding CCs and some more...
On Mon, 06 Oct 2014 09:17:41 +0300
Rémi Denis-Courmont wrote:
> Hello,
>
> Le 2014-10-06 03:29, Jason Ekstrand a écrit :
> > Remi,
> > While this would probably be nice, your approach isnt going to work.
>
> Yeah, I figured that much after I submitted the pa
Hello,
Le 2014-10-06 03:29, Jason Ekstrand a écrit :
Remi,
While this would probably be nice, your approach isnt going to work.
Yeah, I figured that much after I submitted the patch. And then I
rediscovered that the client library does not actually know the version
of the project objects
Remi,
While this would probably be nice, your approach isn't going to work. The
version provided in wl_interface is the version that was compiled into
libwayland, not the version requested when the global was bound. In order
to get this correct, it requires a bit more tracking. I did implement t
Nevermind, that gets the version number of the client protocol library, not
the version actually instantiated for the object :-(
--
Rémi Denis-Courmont
http://www.remlab.net/
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
http://li
In some scenarii, a component will obtain a reference to a proxy
object created by another component. It may then be necessary to
check the interface version of the proxy object at run-time to
determine if a certain interface request is supported by the proxy
object.
For instance, a media player G
11 matches
Mail list logo
