bdc08aae83
libgimp: move pixbuf functions from gimpui.def to gimp.def
2011-04-20 23:54:32 +02:00
058c0b2a0d
libgimp: s/GLIB_CFLAGS/GDK_PIXBUF_CFLAGS/ for libgimp in Makefile.am
...
and some formatting cleanup.
2011-04-20 23:38:49 +02:00
27d312b110
app: call gimp_tool_control_halt() early in transform_tool_button_release()
...
The generic shutdown triggered by shift-click executing copes with an
already halted tool, but we don't want to add checks to tons of
button_release functions.
2011-04-20 22:22:11 +02:00
c5b44f6bd0
More tooltips for tools options
...
Added previously missing tooltips for rectangular and region
selection based tools.
2011-04-21 00:17:31 +04:00
6354bc6ea1
update zh_CN translation of plugins
2011-04-21 03:09:04 +08:00
2068498b5c
app: fix a bug with smooth affecting spacing
2011-04-20 22:03:49 +03:00
316c9fdd45
Reworded the Increment's tooltip
...
The tooltip for Increment option has a better wording now
at Alexia's suggestion.
2011-04-20 22:47:54 +04:00
c406aad208
update zh_CN translation script-fu
2011-04-21 02:32:51 +08:00
3eee39c8fb
Terminology fixes and missing tooltips
...
Options of brush-based tools now have clearer names,
and the options themselves now have tooltips that
had been missing.
2011-04-20 22:24:19 +04:00
4a8fa1ab2a
app: make GimpSpinScale RTL aware
2011-04-20 20:12:21 +02:00
26bf2b0cd7
Make libgimp depend on GdkPixbuf
...
Move the pixbuf layer and image thumbnail function from libgimpui to
libgimp and move gimp_layer_new_from_pixbuf() to gimplayer.[ch] where
it belongs. Change gimp-2.0.pc accordingly, adapt plug-in Makefiles
and update devel-docs.
2011-04-20 20:04:35 +02:00
5d771014d4
GimpCageConfig: use a GArray to store cage's point, to make easier
...
further improvement
2011-04-20 18:50:17 +02:00
9b3e1c91fd
file-pdf-load: Don't use deprecated API (bug #646947 )
2011-04-20 18:55:44 +05:30
ae2ab1ff3b
Fixed a typo
...
The brush editor used to say "Spahe" instead of "Shape".
2011-04-20 13:20:42 +04:00
3edf0cb531
app: GimpSpinScale: don't create two cairo_t in expose()
2011-04-20 00:43:30 +02:00
59ea89234f
app: GimpRuler: clip position marker drawing to the ruler's allocation
...
so we don't overdraw when drawing out of expose.
2011-04-20 00:31:59 +02:00
3bf15d32e6
app: use GimpSpinScales in GimpBrushEditor
2011-04-18 22:27:43 +02:00
4d438a89de
app: restore brush size scale silder visible range to 1000
2011-04-18 22:56:45 +03:00
85509f4ffb
app: GimpScaleComboBox: don't derive from GtkComboBoxEntry
...
because it's deprecated. Derive from GtkComboBox directly, use the
"has-entry" property and move the setup code from init() to
constructed().
2011-04-18 21:49:23 +02:00
4d3e6b062d
app: limit the paint options' fade length scale to 1000
2011-04-18 21:35:41 +02:00
6dd463fb02
app: gimp_spin_scale_change_value(): remove "+ lower" from step calculation
...
It was never noticed because lower is 0.0 or 1.0 in all use cases.
2011-04-18 21:21:45 +02:00
6a3fe9f9c5
app: restore the original brush size upper limit of 10000
...
but restrict the tool options sclae to 500.
2011-04-18 21:10:47 +02:00
bfcecd2ef0
app: GimpBrushFactoryView: use a GimpSpinScale for spacing
...
and use the new scale_limits API to restrict the scale to 1..200 while
the actual range is 1..5000.
2011-04-18 21:04:05 +02:00
d300ec6556
app: add a "scale_limit" API to GimpSpinScale
...
which allows to restrict the scale to a range that is smaller than
that of the model GtkAdjustment. This way we can enter large values in
the entry or by dragging beyond the end of the scale, but keep a
reasonably usable scale range for "normal" values.
2011-04-18 21:01:48 +02:00
bc56060148
app: GimpLayerTreeView: use a GimpSpinScale for opacity
2011-04-18 20:41:02 +02:00
26d50b533b
app: gimp_item_tree_view_add_options(): allow NULL labels
...
and pack the options widget into the vbox directly.
2011-04-18 20:40:10 +02:00
36becbacc6
NEWS: start 2.7.3 section
2011-04-18 19:54:48 +02:00
5b14564d8e
app: GimpMotionBuffer: remove empty constructed()
...
and move buffer destruction from dispose() to finalize().
2011-04-18 15:54:03 +02:00
534b48cb0d
app: add gimp_motion_buffer_get_last_motion_time() and use it
...
The last poking into the buffer is gone now.
2011-04-18 13:13:51 +02:00
d305d000ff
app: struct GimpMotionBufferClass: parent_class had the wrong type
2011-04-18 11:35:51 +02:00
e028195cf3
app: rename process_stroke() and process_hover() to request_foo()
...
Because that's what we are doing by calling the functions: requesting
the emission of "stroke" and "hover" signals.
2011-04-18 11:32:10 +02:00
3fbbb9b333
app: GimpMotionBuffer API cleanup and refactoring
...
- start_stroke()/finih_stroke() -> begin_stroke()/end_stroke()
- process_event_queue() -> process_stroke()
- GimpMotionBuffer::motion() -> GimpMotionBuffer::stroke()
- add GimpMotionBuffer::hover() and process_hover()
- remove push_event_history() and pop_event_queue() from API
The thing works like this:
- Motion events are continuously fed into the buffer using motion_event()
- begin_stroke()/end_stroke() correspond to BUTTON_PRESS/BUTTON_RELEASE,
the period between them is a "stroke"
- If motion_event() returns TRUE, we request "stroke" signals by calling
process_stroke() and "hover" signals by calling process_hover()
2011-04-18 11:08:24 +02:00
d62cf65030
app: rename gimp_motion_buffer_eval_event() to motion_event()
...
because it's feeding it motion events.
2011-04-18 01:09:57 +02:00
6f865eda2b
app: add start_stroke() and finish_stroke() API to GimpMotionBuffer
...
where finish_stroke() is the former flush_event_queue() and
start_stroke() is used in BUTTON_PRESS instead of poking into the
motion buffer's internals. Also, call finish_stroke() also when the
tool is not active, so the event buffer is flushed (the "motion"
callback will ignore the events if the tool is not active).
2011-04-18 00:35:20 +02:00
99f5dc9f18
app: move GimpCagePoint from core-types.h to gegl/
...
and remove the orphaned GimpCagePreview typedef from gimp-gegl-types.h.
2011-04-18 00:09:06 +02:00
6a1b93be1c
app: don't include "libgimpmath/gimpvectors.h" in any header
...
It's types are generally known because it's already included
in core-types.h.
2011-04-17 23:44:45 +02:00
e3b1ed7728
app: remove the timeout in GObject::dispose()
2011-04-17 22:00:18 +02:00
e822fb0d95
app: separate the queue flushing function from the timeout function
...
and add g_return_if_fail() to all public functions.
2011-04-17 21:58:03 +02:00
334e4c5d71
app: move process_event_queue() and flush_event_queue() to GimpMotionBuffer
...
and emit the buffer's "motion" signal when a motion is supposed
to happen. In GimpDisplayShell, connect to GimpMotionBuffer::motion()
and call the tool.
2011-04-17 21:46:29 +02:00
d784ca0a59
app: don't PAUSE/RESUME the active tool around sending it motion events
...
That's most likely a very old artifact that was needed not even when
we used to do XOR, and these days it's even wrong because it makes
the tools think that something about the display has changed, like
zoom or scroll.
2011-04-17 21:12:02 +02:00
9f61a7d2a1
app: siplify gimp_display_shell_process_event_queue()
...
by using gimp_motion_buffer_pop_event_queue() here too.
2011-04-17 20:43:55 +02:00
fae0589767
app: minor cleanup gimp_motion_buffer_eval_event(), no logic change
2011-04-17 20:27:54 +02:00
bb3eac557d
app: add gimp_motion_buffer_pop_event_queue() and use it
...
instead of accessing and removing the queue's first element menually.
2011-04-17 20:20:18 +02:00
aa7c31b802
app: s/gdouble inertia_factor/gboolean event_fill/ in eval_event()
...
Also remove "gdouble max_coord_smooth" from GimpTool and simply use
the existing motion mode for deciding whether or not to fill in
events.
2011-04-17 19:59:31 +02:00
41b469fcf5
app: gimp_motion_buffer_eval_event(): always set last_read_motion_time
...
We need it for correctly requesting device history, so we must
remember it also when returning FALSE and ignoring the event.
2011-04-17 19:34:02 +02:00
7ab72eb54a
app: flush the event queue unconditionally on BUTTON_RELEASE
...
The flashing function checks for a non-empty queue by itself. Also
remove the timeout source explicitly in flush_event_queue() because it
might be called directly, and its FALSE return value has no effect on
the timeout source in that case.
2011-04-17 19:21:46 +02:00
2dbaf7f490
app: set "last_read_motion_time" in gimp_motion_buffer_eval_event()
...
because it is called whenever we process a newly received event.
2011-04-17 19:05:49 +02:00
e09520fb08
app: add GimpMotionBuffer class to swallow all the event smoothing code
...
This commit only adds the class and removes the members from
GimpDisplayShell, so everything looks more ugly than before, but
I wanted the member moving separate from any refactorings.
2011-04-17 18:53:42 +02:00
3d7e0f2fef
devel-docs: Add commit-rules.txt
2011-04-17 09:44:02 +02:00
139fb874a3
Fixed grammatical error in help text for gimp-context-set-feather-radius
2011-04-16 15:00:29 -04:00
Michael Natterer