On Thu, 29 Aug 2013 20:59:44 +0900 Kim Shinwoo said:
self-resolved issue. yay!
> i'm sorry.. the case (_canvas_event_feed_multi_up_internal(); could be
> called even though evas->pointer.downs) is not invalid. please ignore
> previous message. thank you.
>
> cordially,
> shinwoo kim.
>
>
> On
i'm sorry.. the case (_canvas_event_feed_multi_up_internal(); could be
called even though evas->pointer.downs) is not invalid. please ignore
previous message. thank you.
cordially,
shinwoo kim.
On Thu, Aug 29, 2013 at 7:15 PM, Kim Shinwoo wrote:
> dear all, hello.
>
> this message could be dup
dear all, hello.
this message could be duplicated. anyhow..
is it possible to change as below?
the _canvas_event_feed_multi_up_internal(); could be called event though
evas->pointer.downs is equal to '1'. in this case, the multi_up is invalid.
please let me know your opinion. thank you.
diff --
On Mon, 20 Oct 2003 20:53:24 -0700 Stafford Horne <[EMAIL PROTECTED]> babbled:
> Hi,
>
> looks like this is an error.
>
> diff -u -3 -r1.13 evas_events.c
> --- evas_events.c 18 Oct 2003 03:34:00 - 1.13
> +++ evas_events.c 21 Oct 2003 03:51:07
Hi,
looks like this is an error.
diff -u -3 -r1.13 evas_events.c
--- evas_events.c 18 Oct 2003 03:34:00 - 1.13
+++ evas_events.c 21 Oct 2003 03:51:07 -
@@ -305,7 +305,7 @@
e->pointer.x = x;
e->pointer.y = y;
e->pointer.canvas_x = evas_coord_screen_x_
