| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
| |
We are using a timeout in the mousemove events to avoid flood
with more events than the application can draw, but this can produce
get a move event after the method to finish the draw was executed.
As they draw in different canvas, the last part of the draw is lost.
This patch add a timeout a little bigger to the toolend call,
to avoid this situation.
Signed-off-by: Gonzalo Odiard <gonzalo@laptop.org>
|
| |
|
|
|
|
| |
To process more positions and draw better curves.
Signed-off-by: Gonzalo Odiard <gonzalo@laptop.org>
|
| |
|
|
|
|
|
|
|
|
| |
Important information about refcounting in python [1] and [2]
Te binaries for different architectures need be recompiled.
[1] http://docs.python.org/release/2.5.2/api/refcountDetails.html
[2] http://edcjones.tripod.com/refcount.html
Signed-off-by: Gonzalo Odiard <gonzalo@laptop.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The value obtained by read the pick color tool was wrong,
because the range is 0 to 255, and we use it between 0 and 65535
A similar problem is described here [1]
Aditionally, this patch set the right mouse cursor
for the case where the bucket do not fill anything,
because the selected color is the same to the color in the
point to fill. Previously the clock cursor was not removed,
and confused the user.
Signed-off-by: Gonzalo Odiard <gonzalo@laptop.org>
[1] http://old.nabble.com/-cairo--Getting-wrong-cairo-pixel-color.-td31256086.html
|
