Hi!,
On Wed, Apr 11, 2018 at 8:52 PM, Weng Xuetian wrote:
> (forgot to reply to the list)
>
> On Wednesday, 11 April 2018 11:35:58 PDT Dorota Czaplejewicz wrote:
>> On Wed, 11 Apr 2018 11:26:22 -0700
>>
>> Weng Xuetian wrote:
>> > On Monday, 9 April 2018
Hi!,
Thanks for picking up on this Dorota, and sorry for catching up late,
initial discussion started on days off, and I still have a big pile of
"to go through" email.
On Wed, Apr 11, 2018 at 3:03 PM, Dorota Czaplejewicz
wrote:
> This new protocol description is a
On 03/24/2018 08:08 PM, Simon Ser wrote:
> This adds a new protocol to negotiate server-side rendering of window
> decorations for xdg-toplevels. This allows compositors that want to draw
> decorations themselves to send their preference to clients, and clients that
> prefer server-side
(forgot to reply to the list)
On Wednesday, 11 April 2018 11:35:58 PDT Dorota Czaplejewicz wrote:
> On Wed, 11 Apr 2018 11:26:22 -0700
>
> Weng Xuetian wrote:
> > On Monday, 9 April 2018 07:20:53 PDT Dorota Czaplejewicz wrote:
> > > On Sun, 11 Mar 2018 20:30:14 +0100
> > >
>
On Wed, 11 Apr 2018 11:26:22 -0700
Weng Xuetian wrote:
> On Monday, 9 April 2018 07:20:53 PDT Dorota Czaplejewicz wrote:
> > On Sun, 11 Mar 2018 20:30:14 +0100
> >
> > Carlos Garnacho wrote:
> > > This new protocol description is a vast simplification
On Monday, 9 April 2018 07:20:53 PDT Dorota Czaplejewicz wrote:
> On Sun, 11 Mar 2018 20:30:14 +0100
>
> Carlos Garnacho wrote:
> > This new protocol description is a vast simplification over v2, highlights
> > are:
> > - All pre-edit text styling is gone, the protocol doesn't
On Wed, Apr 11, 2018 at 03:03:58PM +0200, Dorota Czaplejewicz wrote:
> This new protocol description is a simplification over v2.
>
> - All pre-edit text styling is gone.
> - No events regarding input panel (OSK) state nor covered rectangle.
> Compositors are still free to handle situations
On Wed, Apr 11, 2018 at 06:04:26PM +0100, Emmanuele Bassi wrote:
> Hi Jonas;
>
> On 11 April 2018 at 17:45, Jonas Ådahl wrote:
>
> > FWIW, I did something similar, here:
> > https://lists.freedesktop.org/archives/wayland-devel/2017-
> > October/035399.html
> > because I wanted
Hi Jonas;
On 11 April 2018 at 17:45, Jonas Ådahl wrote:
> FWIW, I did something similar, here:
> https://lists.freedesktop.org/archives/wayland-devel/2017-
> October/035399.html
> because I wanted to add build tests. IIRC there is some bug that I only
> fixed locally.
>
>
Yes,
FWIW, I did something similar, here:
https://lists.freedesktop.org/archives/wayland-devel/2017-October/035399.html
because I wanted to add build tests. IIRC there is some bug that I only
fixed locally.
Jonas
On Wed, Apr 11, 2018 at 05:27:49PM +0100, Emmanuele Bassi wrote:
> From: Emmanuele
From: Emmanuele Bassi
Meson is a next generation build system, and various projects in the
larger Linux ecosystem already moved to it — for instance:
- the X11 server
- the X11 protocols repository
- Mesa
- libdrm
The added benefit for adding Meson support is that
Sorry to ask such basic questions, but I was unable to find details on:
When you minimize an application window in Weston, where does it go to? How do
you get it back?
Is it possible to change the date/time format in the top right hand corner of
the display?
More good questions.
On 2018-04-11 11:02 AM, Pekka Paalanen wrote:
> There is still the corner-case of: can removing wl_output global A
> cause the name for wl_output global B to change, but I suppose that
> falls to common sense to not do so strange things.
I suppose I can add a note about this
On 2018-04-11 9:17 AM, Philipp Kerling wrote:
> maybe I missed it at some point in the discussion (sorry if that is the
> case), but what is your use case for the "name?" What are clients
> expected to use it for?
This is ideally combined with other protocols. Some example use-cases:
- A client
On Wed, 11 Apr 2018 10:16:46 +1000
Peter Hutterer wrote:
> On Tue, Apr 10, 2018 at 02:01:10PM +0300, Pekka Paalanen wrote:
> > On Mon, 9 Apr 2018 12:54:43 +1000
> > Peter Hutterer wrote:
> >
> > > On Fri, Mar 23, 2018 at 02:01:01PM +0200,
> > > Using mesa-18.0.0, Wayland-1.14 and Weston 3.0.0 I get a blank
> > > screen on a machine with intel hd4400 graphics when staring with:
> > >
> > > WAYLAND_DEBUG=1 EGL_LOG_LEVEL=debug XDG_RUNTIME_DIR=/run/user/$(id
> > > -u) weston-launch >weston.log 2>&1
> > >
> > > X works fine and, a
On Wed, 11 Apr 2018 08:35:22 +
John Frankish wrote:
> > Using mesa-18.0.0, Wayland-1.14 and Weston 3.0.0 I get a blank screen on a
> > machine with intel
> > hd4400 graphics when staring with:
> >
> > WAYLAND_DEBUG=1 EGL_LOG_LEVEL=debug
> Using mesa-18.0.0, Wayland-1.14 and Weston 3.0.0 I get a blank screen on a
> machine with intel
> hd4400 graphics when staring with:
>
> WAYLAND_DEBUG=1 EGL_LOG_LEVEL=debug XDG_RUNTIME_DIR=/run/user/$(id -u)
> weston-launch >weston.log 2>&1
>
> X works fine and, a couple of mesa upgrades
On Tue, 10 Apr 2018 20:27:55 -0400
Drew DeVault wrote:
> Signed-off-by: Drew DeVault
> Reviewed-by: Simon Ser
> ---
> This version clarifies the uniqueness constraint, mapping of names to
> wl_outputs, and persistence between sessions.
>
>
On Tue, 10 Apr 2018 10:27:40 -0400
Drew DeVault wrote:
> Will it address your concerns if I:
>
> 1. Add a statement clarifying that the names are unique across all
>living wl_outputs and may be reused if the corresponding wl_output
>global is removed
> 2. Add a statement
Hi,
maybe I missed it at some point in the discussion (sorry if that is the
case), but what is your use case for the "name?" What are clients
expected to use it for?
The description mentions "similar behaviors", but it is unclear to me
what you are referring to.
Regards,
Philipp
2018-04-10 (火)
Hi Emre Ucan,
Thanks a lot for your quick response. I am able to show same surface on two
layers now. I have taken following two commit to weston 1.11.0. Attached
here same as patch to weston 1.11.0.
"5e8d55da698e58"
"67bd21232fa549"
However if I use any of the below commands to analyze then
22 matches
Mail list logo