On 17/08/17 05:10 PM, Pekka Paalanen wrote:
> On Mon, 7 Aug 2017 19:00:40 +0300
> Alexandros Frantzis wrote:
>
>> +
>> + > + summary="high 32 bits of the seconds part of the new
>> presentation timebase"/>
>> + > + summary="low 32 bits of the seconds part of
Hi,
I noticed that the documentation for wl_shm_format doesn't specify whether
formats use premultiplied alpha or not. Is that intentional or an oversight?
Regards,
Fredrik
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://list
On Fri, 2017-08-04 at 22:04 +0200, jana...@gmail.com wrote:
> On Sat, 2017-06-24 at 16:03 -0500, Joshua Watt wrote:
> > Previously, the hide_input_panel and show_input_panel messages for
> > the text
> > input protocol were limited to specific cases, such as showing the
> > panel on
> > activation,
On Wed, Jul 27, 2016 at 9:54 AM, Jonas Ådahl wrote:
> xdg-foreign is a protocol meant to enable setting up inter surface
> relationships across clients. Potential use cases are out-of-process
> dialogs, such as file dialogs, meant to be used by sandboxed processes
> that may not have the access it
On Thu, Aug 10, 2017 at 3:47 AM, Jonas Ådahl wrote:
>
> Anyhow, "export_surface" or maybe even "export_toplevel" (as that is the only
> thing we allow exporting anyway) seems fine to me. The "import" request
> should be renamed in a similar manner as well then.
here attached a patch to rename the
On Thu, Aug 17, 2017 at 11:10:12AM +0300, Pekka Paalanen wrote:
> On Mon, 7 Aug 2017 19:00:40 +0300
> Alexandros Frantzis wrote:
>
> > The presentation.timing request creates an object that informs the
> > client about the presentation timing of an wl_output in a precise and
> > low-overhead way
Dear All,
I am observing crash with following callstack. Is this known issue to
anyone here and fixed with latest version? How should one debug such
issues? Any inputs, comments or suggestion to debug and fix this issue
would be very helpful.
I am suspecting it is related to bug
https://bugs.free
On Mon, 7 Aug 2017 19:00:40 +0300
Alexandros Frantzis wrote:
> The presentation.timing request creates an object that informs the
> client about the presentation timing of an wl_output in a precise and
> low-overhead way, without the need to submit any surface content updates.
Hi Alf,
the last
