mouse accessibility mode (which introduced issues with tools like
'Flower' and 'Fold' (which show previews) and 'Ripples' (which doesn't
involve any dragging)).
click/move/click (e.g., by clicking a tool, hitting a command key, or
leaving the window) in mouse accessibility mode.
NOTE: This currently 'undoes' any magic, and not just previews;
tools will need to 'register' the fact that they create previews.
* Adjustment of 'backlogged event queue' handling when dealing with mouse
motion. (Rather than stop listening to motion events after spinning in
the "while (SDL_PollEvent())" loop for 250ms, it now skips every few
events.)
This prevents circle-drawings from appearing as "D". Now, they start
appearing as polygon-like shapes.
(Will probably need to set up event handling in a separate thread so that
we can have an increased mouse motion event buffer, to avoid artifacts
when drawing/moving quickly. e.g., try to draw "O", but get a "D")
* Mouse accessibility doesn't get 'stuck' in click mode when other
actions are initiated (e.g., [Esc] or window close button to quit,
[Ctrl+P] to print, etc.), when Tux Paint loses focus, or when mouse
goes outside of the window.
Enabled fmemopen_alternative on Windows.
Rearranged calls to rsvg_init()/rsvg_term() so that they are only called
once at startup and shutdown. This was causing segfaults when opening SVG
files and apparently it's not just Tux Paint:
http://0pointer.de/blog/projects/beware-of-rsvg-term.html
Slightly hysterical, but a quick Google search reveals other projects with
the same problem/solution.
Builds and runs on Windows again.
even though our language MO files are installed, it will switch to C
locale (which is not UTF-8), and the language won't be used in Tux Paint.
Utilizing hack designed by Albert that sets LC_ALL to an arbitrary,
working UTF-8 locale (currently using en_US.UTF-8), and then setting
the LANGUAGE env. var. Seems to work! (I can use Fula (ff_SN.UTF-8)
on my Ubuntu 9.04 system that doesn't have Fula support.)
