On 9 November 2015 at 14:39, Auke Booij wrote:
> and it was a mistake
Sorry, let me retract this - that was maybe a bit harsh, since I don't
know the exact history.
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
On 9 November 2015 at 11:54, Nils Chr. Brause wrote:
> Hi,
>
> On Mon, Nov 9, 2015 at 12:04 PM, Pekka Paalanen wrote:
>> On Fri, 6 Nov 2015 16:05:10 +0100
>> "Nils Chr. Brause" wrote:
>>
>>> Hi,
>>>
>>> On Fri, Nov 6, 2015
On Mon, 9 Nov 2015 12:54:00 +0100
"Nils Chr. Brause" wrote:
> Hi,
>
> On Mon, Nov 9, 2015 at 12:04 PM, Pekka Paalanen wrote:
> > On Fri, 6 Nov 2015 16:05:10 +0100
> > "Nils Chr. Brause" wrote:
> >
> >> Hi,
> >>
> >> On
On 9 November 2015 at 11:41, Pekka Paalanen wrote:
> I believe comments are enough. I suppose the DTD error message from
> wayland-scanner could refer to built-in DTD, that would be a small
> change and make it obvious. Just add one word in the warning message.
Okay, your
On Fri, Nov 06, 2015 at 01:31:06PM +0100, Mads wrote:
Hi!
Using xf86-input-libinput 0.15.0 and libinput 1.1.0, are there any way
to
tweak the size of the scrolling deadspot? That is, how many pixels of
movement libinput ignores before starting a scroll event (e.g. two
fingers
vertical
On Fri, 6 Nov 2015 12:55:19 -0600
Derek Foreman wrote:
> wl_surface.damage uses surface local co-ordinates.
>
> Buffer scale and buffer transforms came along, and EGL surfaces
> have no understanding of them.
>
> Theoretically, clients pass damage rectangles - in
On Sat, 7 Nov 2015 09:49:21 -0800
"Jasper St. Pierre" wrote:
> So we fix the bug by adding wl_surface.buffer_damage, since it's
> impossible for Mesa to know about buffer transformations... and then
> what?
Be happy.
> The only way we can properly interpret the
Hi,
On Mon, Nov 9, 2015 at 2:49 PM, Pekka Paalanen wrote:
> On Mon, 9 Nov 2015 12:54:00 +0100
> "Nils Chr. Brause" wrote:
>
>> Hi,
>>
>> On Mon, Nov 9, 2015 at 12:04 PM, Pekka Paalanen wrote:
>> > On Fri, 6 Nov 2015 16:05:10
DPI is read from the X server, not Xresources.
You can probably adjust DPI by the scale factor in X emulation, Or not
scale emulated X windows as suggested.
Thanks
Michal
On 9 November 2015 at 19:42, Bill Spitzak wrote:
> Have the X emulator assume the client set the scale
On Mon, Nov 09, 2015 at 11:14:32AM -0600, Derek Foreman wrote:
> On 08/11/15 09:58 PM, Peter Hutterer wrote:
> > The scanner parses CDATA in but lets it disappear otherwise. To have
> > descriptive text associated with the , we need a tag -
> > and that must have a summary attribute. The current
On Mon, Nov 09, 2015 at 02:33:39PM -0800, Jason Gerecke wrote:
> On Fri, Nov 6, 2015 at 4:11 PM, Bill Spitzak wrote:
> > Having read this more carefully, the cursor scheme absolutely will not work.
> >
> > The main problem is that the client may want to choose a cursor for a
Making the transform into a bitfield allows bitfield tests for useful
facts: it can see if it is a mirror image by testing the flip bit, and
check for transposition of the axes by checking the 90 degree bit. I
believe this is the reason behind the desire to declare it a bitfield and I
agree this
Have the X emulator assume the client set the scale to the one determined
from the dpi in the .Xresources?
On Sun, Nov 8, 2015 at 6:10 PM, Jonas Ådahl wrote:
> On Sat, Nov 07, 2015 at 09:48:59PM +0100, Michael Stapelberg wrote:
> > Hey,
> >
> > I just got around to trying
Is there no way to just make the scanner use the text without adding extra
nesting?
On Mon, Nov 9, 2015 at 9:14 AM, Derek Foreman
wrote:
> On 08/11/15 09:58 PM, Peter Hutterer wrote:
> > The scanner parses CDATA in but lets it disappear otherwise. To
> have
> >
I believe wl_surface.damage should be defined as "the same as
w_surface.buffer_damage if the only transforms are due to an integer buffer
scale and the 8 possible buffer transforms". This means it is undefined if
the wl_scalar proposal is used, and avoids the need to define it for any
future
Hi,
On Mon, Nov 9, 2015 at 3:39 PM, Auke Booij wrote:
> On 9 November 2015 at 11:54, Nils Chr. Brause wrote:
>> Hi,
>>
>> On Mon, Nov 9, 2015 at 12:04 PM, Pekka Paalanen wrote:
>>> On Fri, 6 Nov 2015 16:05:10 +0100
>>> "Nils Chr.
On Mon, 9 Nov 2015 15:38:22 +0100
"Nils Chr. Brause" wrote:
> Hi,
>
> On Mon, Nov 9, 2015 at 2:49 PM, Pekka Paalanen wrote:
> > On Mon, 9 Nov 2015 12:54:00 +0100
> > "Nils Chr. Brause" wrote:
> >
> >> Hi,
> >>
> >> On Mon,
Hi,
On Mon, Nov 9, 2015 at 4:35 PM, Pekka Paalanen wrote:
> On Mon, 9 Nov 2015 15:38:22 +0100
> "Nils Chr. Brause" wrote:
>
>> Hi,
>>
>> On Mon, Nov 9, 2015 at 2:49 PM, Pekka Paalanen wrote:
>> > On Mon, 9 Nov 2015 12:54:00
On 08/11/15 09:58 PM, Peter Hutterer wrote:
> The scanner parses CDATA in but lets it disappear otherwise. To have
> descriptive text associated with the , we need a tag -
> and that must have a summary attribute. The current scanner doesn't handle
> however, so to get the summary printed in
On Mon, 9 Nov 2015 10:28:13 -0800
Bill Spitzak wrote:
> I believe wl_surface.damage should be defined as "the same as
> w_surface.buffer_damage if the only transforms are due to an integer buffer
> scale and the 8 possible buffer transforms". This means it is undefined if
>
On Mon, 9 Nov 2015 23:41:44 +
Auke Booij wrote:
> On 9 November 2015 at 23:34, Peter Hutterer wrote:
> > See 851614fa78862499e016c5718e730fefbb8e3b73
> >
> > Signed-off-by: Peter Hutterer
>
> Reviewed-by: Auke Booij
On 9/11/2015 20:39 , Auke Booij wrote:
On 6 November 2015 at 11:26, Pekka Paalanen wrote:
On Fri, 6 Nov 2015 09:47:03 +1000
Peter Hutterer wrote:
On Thu, Nov 05, 2015 at 04:58:09PM +0200, Pekka Paalanen wrote:
On Mon, 19 Oct 2015 11:30:47
On Fri, 6 Nov 2015 16:05:10 +0100
"Nils Chr. Brause" wrote:
> Hi,
>
> On Fri, Nov 6, 2015 at 3:48 PM, Auke Booij wrote:
> > On 6 November 2015 at 13:03, Nils Christopher Brause
> > wrote:
> >> The enumeration
On 9 November 2015 at 10:54, Peter Hutterer wrote:
> On 9/11/2015 20:39 , Auke Booij wrote:
>>
>> On 6 November 2015 at 11:26, Pekka Paalanen wrote:
>>>
>>> On Fri, 6 Nov 2015 09:47:03 +1000
>>> Peter Hutterer wrote:
>>>
On Fri, Nov 6, 2015 at 4:11 PM, Bill Spitzak wrote:
> Having read this more carefully, the cursor scheme absolutely will not work.
>
> The main problem is that the client may want to choose a cursor for a tool
> based on the location at which it came into proximity. It cannot
See 851614fa78862499e016c5718e730fefbb8e3b73
Signed-off-by: Peter Hutterer
---
protocol/wayland.dtd | 2 ++
1 file changed, 2 insertions(+)
diff --git a/protocol/wayland.dtd b/protocol/wayland.dtd
index e28dbc0..15f20ab 100644
--- a/protocol/wayland.dtd
+++
Hi Damien,
I just noticed that from this patch series of three, only 1/3 shows up
in Patchwork as http://patchwork.freedesktop.org/patch/64191/ .
The rest are:
http://lists.freedesktop.org/archives/wayland-devel/2015-November/025336.html
On Wed, 4 Nov 2015 15:03:12 -0800
Bryce Harrington wrote:
> On Sat, Oct 24, 2015 at 12:07:46PM +0100, Auke Booij wrote:
> > There has been plenty of discussion regarding the introduction of new XML
> > attributes. This series of patches improves on my earlier attempt to
On 6 November 2015 at 11:26, Pekka Paalanen wrote:
> On Fri, 6 Nov 2015 09:47:03 +1000
> Peter Hutterer wrote:
>
>> On Thu, Nov 05, 2015 at 04:58:09PM +0200, Pekka Paalanen wrote:
>> > On Mon, 19 Oct 2015 11:30:47 +1000
>> > Peter Hutterer
On 9 November 2015 at 04:14, Peter Hutterer wrote:
> This reverts commit 06fb8bd371403d43bc192577abd6b0a0c8b29c59.
>
> Having a DTD hooked up gives an indication of what we expect the protocol to
> be, which is a clearer documentation than the current "whatever scanner.c
On 9 November 2015 at 23:34, Peter Hutterer wrote:
> See 851614fa78862499e016c5718e730fefbb8e3b73
>
> Signed-off-by: Peter Hutterer
Reviewed-by: Auke Booij
___
wayland-devel mailing
Embed the wayland.dtd protocol data into the scanner binary so we can validate
external protocol files without requiring makefile changes. Hat-tip to Pekka
Paalanen for the embedding trick.
The embedding trick doesn't work well if the to-be-embedded file is in a
different location than the source
Hi,
On 09-11-15 07:40, Peter Hutterer wrote:
At least on the t440, this is enough to trigger correct detection between
swipe and scroll 90% of the time.
s/swipe/pinch/
> Since scrolling is significantly more
prevalent than gesturing, erring on the side of scrolling at the cost of
On Mon, 9 Nov 2015 14:15:01 +1000
Peter Hutterer wrote:
> Embed the wayland.dtd protocol data into the scanner binary so we can validate
> external protocol files without requiring makefile changes. Hat-tip to Pekka
> Paalanen for the embedding trick.
> The embedding
On Mon, 9 Nov 2015 14:15:00 +1000
Peter Hutterer wrote:
> The scanner parses this already, it doesn't do anything with it though.
>
> The DTD requires the order to be copyright, description, then the interfaces.
> That's largely a DTD limitation, the scanner doesn't
On Mon, 9 Nov 2015 14:14:59 +1000
Peter Hutterer wrote:
> This reverts commit 06fb8bd371403d43bc192577abd6b0a0c8b29c59.
>
> Having a DTD hooked up gives an indication of what we expect the protocol to
> be, which is a clearer documentation than the current "whatever
On Mon, 9 Nov 2015 11:16:09 +
Auke Booij wrote:
> On 9 November 2015 at 10:54, Peter Hutterer wrote:
> > On 9/11/2015 20:39 , Auke Booij wrote:
> >>
> >> On 6 November 2015 at 11:26, Pekka Paalanen wrote:
> >>> Would it be
Hi,
On Mon, Nov 9, 2015 at 12:04 PM, Pekka Paalanen wrote:
> On Fri, 6 Nov 2015 16:05:10 +0100
> "Nils Chr. Brause" wrote:
>
>> Hi,
>>
>> On Fri, Nov 6, 2015 at 3:48 PM, Auke Booij wrote:
>> > On 6 November 2015 at 13:03, Nils
38 matches
Mail list logo