Manuel,
Thanks for keeping this going. I don't have a whole lot of comments at the
moment as it's a pretty small protocol change. I would like to hear some
commentary from Jasper and some of the other desktop devs though.
The one comment I will make about the protocol is that you may want to
cha
On Mar 6, 2015 9:18 PM, "Max Jensen" wrote:
>
> Hi Jim,
>
> Thank you for your response, I am glad someone is working on this and I
will keep an eye on your blog. Sadly I can't help right now, because I am
still working on my bachelor thesis in games engineering (not VR related).
And while I am ve
More likely the problem is in the git commit message. There should be a
short one-liner followed by a blank line and then by a paragraph giving
more detail. Git uses the first paragraph as a brief patch description
in many places, including titling patch emails.
On 03/06/2015 12:29 PM, Lyude w
Just a nit-pick here, generally it's a good idea to keep the subject
line short, and have the majority of the description in the body of the
patch. Saw this while I was going through my e-mails and figured I might
as well point that out :).
Cheers,
Lyude
On Tue, 2015-03-03 at 13:49 +0100,
On 06/03/15 05:03 AM, Pekka Paalanen wrote:
> From: Pekka Paalanen
>
> Hi,
>
> this is a series of relatively small changes to the Pixman-renderer, with the
> major goals of a) clean up the draw_view/repaint_region machinery, and b)
> properly implement source clipping. This is a follow-up to
>
On 06/03/15 05:04 AM, Pekka Paalanen wrote:
> From: Pekka Paalanen
>
> Implement a way to do composition clipping with a region32 given in
> source image space.
>
> Pixman does not directly support this kind of operation at all. If you
> pixman_image_set_clip_region32() on a source image, it wil
On 06/03/15 05:04 AM, Pekka Paalanen wrote:
> From: Pekka Paalanen
>
> Move code from draw_view() into a new function draw_view_translated().
> This new function is correct only if
> view_transformation_is_translation().
>
> The functional change in this is that if view->alpha is not 1.0, we do
On 06/03/15 05:04 AM, Pekka Paalanen wrote:
> From: Pekka Paalanen
>
> Change the region argument types in repaint_region(), moving the
> final_region computation to the caller. The caller is in a better
> position deciding if source_clip is needed or if it can be intersected
> into the final_reg
On 06/03/15 05:03 AM, Pekka Paalanen wrote:
> From: Pekka Paalanen
>
> Move the long piece of code computing the end-to-end transformation from
> repaint_region() into a new function
> pixman_renderer_compute_transform().
>
> The code itself it not modified.
>
Nice refactor, but the transform
On 06/03/15 05:03 AM, Pekka Paalanen wrote:
> From: Pekka Paalanen
>
> This will be used by pixman-renderer.
>
> Signed-off-by: Pekka Paalanen
> ---
> src/compositor.c | 36
> src/compositor.h | 5 +
> 2 files changed, 41 insertions(+)
>
> diff --git
From: Pekka Paalanen
Move code into a new helper function. No changes.
Signed-off-by: Pekka Paalanen
---
src/pixman-renderer.c | 31 ++-
1 file changed, 18 insertions(+), 13 deletions(-)
diff --git a/src/pixman-renderer.c b/src/pixman-renderer.c
index 2769168..459b
From: Pekka Paalanen
Move the long piece of code computing the end-to-end transformation from
repaint_region() into a new function
pixman_renderer_compute_transform().
The code itself it not modified.
Because the number of moved lines is so big, git-diff will show the
changes in the context ins
From: Pekka Paalanen
Hi,
this is a series of relatively small changes to the Pixman-renderer, with the
major goals of a) clean up the draw_view/repaint_region machinery, and b)
properly implement source clipping. This is a follow-up to
http://lists.freedesktop.org/archives/wayland-devel/2015-Mar
From: Pekka Paalanen
This will be used by pixman-renderer.
Signed-off-by: Pekka Paalanen
---
src/compositor.c | 36
src/compositor.h | 5 +
2 files changed, 41 insertions(+)
diff --git a/src/compositor.c b/src/compositor.c
index 45e8f5c..1747c6f 10064
From: Pekka Paalanen
Move code from draw_view() into a new function draw_view_translated().
This new function is correct only if
view_transformation_is_translation().
The functional change in this is that if view->alpha is not 1.0, we do
not bother computing and painting the non-opaque and opaqu
From: Pekka Paalanen
Only needed in the source-clipped case, otherwise the boundingbox is
already doing the necessary clipping.
Signed-off-by: Pekka Paalanen
---
src/pixman-renderer.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/src/pixman-renderer.c b/src/pixman-renderer.c
index
From: Pekka Paalanen
A simple refactoring just to help readability.
Signed-off-by: Pekka Paalanen
---
src/pixman-renderer.c | 16 +---
1 file changed, 13 insertions(+), 3 deletions(-)
diff --git a/src/pixman-renderer.c b/src/pixman-renderer.c
index 459b20a..ecb4109 100644
--- a/sr
From: Pekka Paalanen
Implement a way to do composition clipping with a region32 given in
source image space.
Pixman does not directly support this kind of operation at all. If you
pixman_image_set_clip_region32() on a source image, it will be ignored
unless you also
pixman_image_set_sour
From: Pekka Paalanen
Change the region argument types in repaint_region(), moving the
final_region computation to the caller. The caller is in a better
position deciding if source_clip is needed or if it can be intersected
into the final_region via a simple translation. This avoids
surf_region/so
Hi,
On 06-03-15 06:44, Peter Hutterer wrote:
The previous setting of 10 wasn't 10 mm, it was used against the deltas
normalized to a 1000DPI mouse, i.e. closer to 4mm. It was also also per-event,
so a slow movement or a high-frequency touchpad can struggle to meet the
threshold.
Change the trig
Hi,
On 06-03-15 06:43, Peter Hutterer wrote:
Signed-off-by: Peter Hutterer
Looks good:
Reviewed-by: Hans de Goede
Regards,
Hans
---
src/evdev-mt-touchpad.h | 39 ---
1 file changed, 20 insertions(+), 19 deletions(-)
diff --git a/src/evdev-mt-touch
Hi,
On 06-03-15 11:38, Hans de Goede wrote:
Hi,
On 06-03-15 06:41, Peter Hutterer wrote:
Ideally we want to specify various thresholds in mm, but not all touchpads
set the hardware resolutions. Rather than conditions to check for resolutions
everywhere, use a macro to give us a normalized valu
Hi,
On 06-03-15 06:42, Peter Hutterer wrote:
Previous code used a device coordinate threshold of 300 which won't work on
Elantech touchpads (1280 vs the ~4000 that synaptics has).
Convert to normalized DPI and reduce the threshold to 3mm.
https://bugs.freedesktop.org/show_bug.cgi?id=89206
[not
Hi,
On 06-03-15 06:41, Peter Hutterer wrote:
Ideally we want to specify various thresholds in mm, but not all touchpads
set the hardware resolutions. Rather than conditions to check for resolutions
everywhere, use a macro to give us a normalized value that we use for motion
as well.
Signed-off-
Hi Peter,
Thanks for working on this. You're timing wrt MM_TO_DPI_NORMALIZED introduction
is excellent as I need something similar for my pinch gesture work.
I've a couple of remarks, so I'm going to reply to each patch separately.
On 05-03-15 22:45, Peter Hutterer wrote:
On a semi-mt device l
Hi,
On 05-03-15 22:45, Peter Hutterer wrote:
All callers except the tap motion threshold call
tp_get_delta() followed by tp_filter_motion() - the latter normalized it
before calling into the accleration code.
Move the normalization into tp_get_delta() so we don't deal with
device-specific coord
26 matches
Mail list logo