bkabinashak47 / ardesia

Automatically exported from code.google.com/p/ardesia
0 stars 0 forks source link

Annotation starting after leave_notify_event #7

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Start the ardesia
2. paint
3. try to click an ardesia button inside the bar

What is the expected output? What do you see instead?
I expect to push the button but the pointe is locked

I have investigate on the problem and this is cause

The new code that use the leave_notify_event
from the ardesia bar such as signal
to become to paint does not work
in my machine

I have debugged the code and in this machine
a lot of leave_notify_event are generated 
even if the pointer is inside the bar

To workaround this problem that can caused by a wrong use
of the windows or by a gtk bug
I have reputted the wait_out_bar code in annotate.c

Than we have two scenarios
1) The machine emit rightly
   the leave_notify_event
   the annotate.c check that
   the position is right
   and start to annotate

2) The machine emit worongly
   an leave_notify_event
   and ask to annotate.c
   to grab, but annotate.c
   see that the pointer is
   inside the bar and continue
   to loop waiting for the
   moment in which the pointer
   will be outside the bar
   Only at this moment will start
   to annotate

In any case is important investigate
about the strange behave of
the leave_notify_event because it can depend
on a wrong window handling

This is only a workaround to solve
fastly the problem

Original issue reported on code.google.com by al...@paranoici.org on 25 Nov 2009 at 10:27

GoogleCodeExporter commented 9 years ago
This issue was closed by revision r241.

Original comment by al...@paranoici.org on 25 Nov 2009 at 4:30

GoogleCodeExporter commented 9 years ago

Original comment by al...@paranoici.org on 17 Sep 2012 at 5:12