aboutsummaryrefslogtreecommitdiffstats
path: root/libgnomecanvas/gnome-canvas.c
Commit message (Collapse)AuthorAgeFilesLines
* Bug 704459: GnomeCanvasItem: Implement all methodsMatthew Barnes2013-07-181-0/+46
| | | | So subclasses can safely chain up without checking for NULL.
* Add a GdkDevice parameter to gnome_canvas_item_grab().Matthew Barnes2012-11-301-14/+30
| | | | | GnomeCanvas will stash the GdkDevice and reuse it in the subsequent gnome_canvas_item_ungrab() call.
* Avoid using GdkEventButton directly in certain places.Matthew Barnes2012-11-301-41/+39
| | | | | | | | | | | | Prefer dealing with GdkEvent pointers and using accessor functions like gdk_event_get_button(). This is complicated by the fact that some GtkWidget method declarations still use GdkEventButton pointers, and synthesizing button events pretty much requires direct GdkEventButton access. But GDK seems to be nudging itself toward sealing the GdkEvent union. Likely to happen in GDK4. Mainly clean up signal handlers and leave method overrides alone for now.
* Coding style and whitespace cleanup.Matthew Barnes2012-11-111-7/+7
|
* Coding style and whitespace cleanup.Matthew Barnes2012-09-011-89/+120
|
* Remove all GDK threads usage.Matthew Barnes2012-08-061-4/+0
| | | | | | | | | | | | According to [1], we don't need to worry about GDK's global lock since we don't call gdk_threads_init() or gdk_threads_set_lock_functions(). The GDK threads API is being aggressively deprecated by GTK+ developers so let's just abandon it entirely. I've never really understood when you're supposed to use it or not use it anyway, so it's good to be rid of this confusion. [1] https://mail.gnome.org/archives/desktop-devel-list/2012-August/msg00005.html
* Use template files to generate GEnumClass types.Matthew Barnes2012-07-181-6/+2
|
* Reduce usage of g_type_class_peek_parent().Matthew Barnes2012-06-251-43/+37
| | | | G_DEFINE_TYPE macros define a static "parent_class" variable.
* Bug #671585 - Add support for smooth scrolling devicesMilan Crha2012-05-151-0/+1
|
* Coding style and whitespace cleanup.Matthew Barnes2012-02-201-117/+24
|
* Coding style and whitespace cleanup.Matthew Barnes2011-09-041-81/+151
|
* Invalidate region by one more pixel in width and heightMilan Crha2011-08-191-2/+2
|
* Bug 652629 - GnomeCanvas: Disregard synthesized crossing eventsMatthew Barnes2011-07-111-0/+7
| | | | | | | | | | | synth_crossing() in gtkwidget.c does not set valid pointer coordinates, but GnomeCanvas relies on these coordinates to figure out what canvas item the event applies to. Detect these synthesized GDK_ENTER_NOTIFY and GDK_LEAVE_NOTIFY events and disregard them. This was breaking drag-and-drop of EMinicards and probably elsewhere.
* Coding style and whitespace cleanups.Matthew Barnes2011-06-091-3/+8
|
* Bug #646109 - Fix use of include <config.h> to make sure translations workMilan Crha2011-05-271-0/+2
|
* Coding style and whitespace cleanup.Matthew Barnes2011-05-221-7/+12
|
* Coding style cleanups.Matthew Barnes2011-05-091-1/+1
|
* Whitespace and coding style cleanups.Matthew Barnes2011-05-081-3/+4
|
* Coding style and whitespace cleanup.Matthew Barnes2011-02-191-2/+2
|
* Remove NULL checks for GObject methods.Matthew Barnes2011-02-131-2/+2
| | | | | As of GLib 2.28 all GObject virtual methods, including constructed(), are safe to chain up to unconditionally. Remove unnecessary checks.
* Bug #641502 - Flickering while resizing the mail listMilan Crha2011-02-101-40/+42
|
* Bug 641756 - Fix warnings from GCC 4.6Kjartan Maraas2011-02-091-2/+0
| | | | GCC learned how to find dead assignments.
* Fix cairo-gobject.h include pathMilan Crha2011-02-041-1/+1
|
* More whitespace cleanup.Matthew Barnes2011-01-311-71/+71
|
* Coding style and whitespace cleanup.Matthew Barnes2011-01-301-4/+7
|
* Adapt GnomeCanvas to latest gtk+-3.0 API.Matthew Barnes2011-01-261-168/+158
|
* Drop backward-compatibility cruft.Matthew Barnes2011-01-251-3/+0
|
* Remove some unused gnome-canvas options.Matthew Barnes2011-01-161-172/+16
| | | | | | | | | | | | | Simplifies the drawing code a bit. Public API removed: GnomeCanvas.center_scroll_region (is always TRUE) GnomeCanvas.pixels_per_unit (is always 1.0) gnome_canvas_set_center_scroll_region() gnome_canvas_get_center_scroll_region() gnome_canvas_set_pixels_per_unit()
* Fudge GtkScrollable for gtk2.Matthew Barnes2011-01-151-36/+37
| | | | | | Yes, the GtkScrollable interface is implemented by more than just GtkLayout, but it turns out GtkLayout is the only thing Evolution uses the GtkScrollable API for on the gtk3 branch.
* Coding style and whitespace cleanup.Matthew Barnes2010-11-081-2/+2
|
* Rename GnomeCanvasItem.destroy() to dispose().Matthew Barnes2010-10-301-10/+10
| | | | | To clarify the semantics: the method may be called multiple times so pointers should be set to NULL after freeing or unreferencing.
* Fix gnome_canvas_item_w2i_matrix().Matthew Barnes2010-10-301-6/+5
| | | | Was returning an inverted matrix: i2w instead of w2i.
* gnome-canvas: Remove functions that allocate colorsBenjamin Otte2010-10-301-69/+0
| | | | | | Cairo doesn't need allocated colors. Yay, gnome-canvas now compiles with GDK_DISABLE_DEPRECATED.
* gnome-canvas: Port drawing to use cairoBenjamin Otte2010-10-301-26/+14
|
* gnome-canvas: Remove gnome_canvas_set_stipple_origin()Benjamin Otte2010-10-301-18/+0
|
* gnome-canvas: Simplify updating codeBenjamin Otte2010-10-301-310/+34
| | | | | Instead of keeping oour own invalid area, trust GDK to do the right thing.
* gnome-canvas: Remove gnome_canvas_w2c_affine()Benjamin Otte2010-10-301-26/+0
| | | | It's not necessary anymore. Use gnome_canvas_w2c_matrix() instead.
* gnome-canvas: Convert point tranformation functions to use cairoBenjamin Otte2010-10-301-25/+21
|
* gnome-canvas: Remove gnome_canvas_update_now()Benjamin Otte2010-10-301-24/+0
| | | | | 1) Don't ever force an update 2) There's GTK API to force an update if you need to. Use that.
* gnome-canvas: Convert canvas item transformation matrix to cairoBenjamin Otte2010-10-301-338/+72
| | | | | Also update the GnomeCanvasItem.update vfunc to take a cairo_matrix_t and no longer pass the clip_path (what was it used for anyway?).
* gnome-canvas: Rewrite GnomeCanvasShape to use CairoBenjamin Otte2010-10-301-4/+86
| | | | | Dashing properties were commented out in the process. They are not used inside Evolution.
* gnome-canvas: Change GnomeCanvasItem->point vfuncBenjamin Otte2010-10-301-47/+17
| | | | | | | | Previously the function returned the distance to the nearest item. Now it only returns an item that is hit. This slightly changes semantics (button events are no longer dispatched to the nearest item, but only to the item actually clicked on), but makes the code way simpler and actually does what one would expect.
* gnome-canvas: Remove close_enough memberBenjamin Otte2010-10-301-10/+3
| | | | It's never set, so just replace it with its default value 0 everywhere.
* gnome-canvas: Port GnomeCanvasLine to use Cairo for drawingBenjamin Otte2010-10-301-0/+30
|
* gnome-canvas: Remove GnomeCanvasItem->render vfuncBenjamin Otte2010-10-301-32/+0
| | | | It's unused now
* gnome-canvas: Remove aa codeBenjamin Otte2010-10-301-151/+25
| | | | The anti-aliased code was never used, so remove it.
* Bug #631870 - Memory leak in e_week_view after GtkObject removalMilan Crha2010-10-251-1/+1
|
* Bug #631320 - GtkObject is gone in GTK3Milan Crha2010-10-071-43/+34
|
* Use new GDK keysym names if available.Matthew Barnes2010-09-181-0/+1
| | | | | | | In GTK+ 2.21.8, the keysym names were renamed from GDK_* to GDK_KEY_*. I've added backward-compatibility macors to gtk-compat.h, which can be dumped as soon as we require GTK+ >= 2.22.0.
* Various memory leaksMilan Crha2010-09-081-2/+0
|
* Coding style and whitespace cleanup.Matthew Barnes2010-08-291-4/+4
|
* Bug 624525 - Variable name collision in gtk-compat macroMilan Crha2010-07-221-1/+1
|
* Coding style and whitespace cleanup.Matthew Barnes2010-06-201-213/+251
|
* Don't bother translating GnomeCanvas GObject properties.Matthew Barnes2010-06-201-6/+6
|
* Remove unused libart_lgpl API.Matthew Barnes2010-06-161-1/+0
| | | | According to CallCatcher.
* Fix all remaining GTK3 issues.Matthew Barnes2010-06-161-140/+311
| | | | | | | | | | | | Work around the issue of GnomeCanvasItem amending its own flags to GtkObject::flags (which is sealed) by giving it its own flags field. This breaks libgnomecanvas ABI and API, but I see no other way. This commit didn't work the first time because gnome-pilot libraries were still pulling in the system-wide libgnomecanvas, and that was interfereing with our bundled version which has a different ABI. But gnome-pilot integration was dropped in the previous commit, so everything is now using the bundled libgnomecanvas.
* Revert "Fix all remaining GTK3 issues."Matthew Barnes2010-06-151-311/+140
| | | | | | | This reverts commit fd8b55edaa88906b588aa07d9eadcacd34a7a774. Something in this commit seriously hosed ETable, making Evolution pretty much unusable. Reverting this until I can track down the problem.
* Fix all remaining GTK3 issues.Matthew Barnes2010-06-151-140/+311
| | | | | | Work around the issue of GnomeCanvasItem amending its own flags to GtkObject::flags (which is sealed) by giving it its own flags field. This breaks libgnomecanvas ABI and API, but I see no other way.
* Embed libart_lgpl and libgnomecanvas.Matthew Barnes2010-06-141-0/+4090
Both of these modules are deprecated and going away in GNOME 3 but we still rely heavily on them for GnomeCalendar and ETable. So, welcome to the island of unwanted libraries...
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-26 08:10:22 +0800