fefe8e7c8c
win32: Actually check for IPrintDialogCallback in configure
2011-11-10 17:41:08 +01:00
06a20d207a
Fix build by adding include
...
build failed with a GTK_IS_VIEWPORT link error
2011-11-10 17:40:46 +01:00
96bae6ad08
Add include to fix the build
2011-11-10 17:25:02 +01:00
24b9599af7
a11y: Get rid of gtk.h includes in headers
...
This way, we can include them without accidentally including deprecated
code. Which means we can still use the recently added turning-off tricks
for deprecation warnings.
2011-11-10 17:10:04 +01:00
2d3c36a021
a11y: Fix gcc warning
2011-11-10 17:10:04 +01:00
1c96b0b838
a11y: It's not a bug if there's no row at some point
...
In that case, there's just nothing there.
2011-11-10 17:10:04 +01:00
c30d313afc
gtk: Fix parsing of accelerators with keycodes
...
GDK_KEY_VoidSymbol is not the same as keycode 0. This fixes
keycodes such as "0xb3" being parsed as "VoidSymbol" keysyms.
https://bugzilla.gnome.org/show_bug.cgi?id=663761
2011-11-10 14:33:28 +00:00
d69c7f4776
gtk: Fix GtkCellRenderer ignoring keycodes
...
We should use the new helper code rather than invent our own
functions again.
https://bugzilla.gnome.org/show_bug.cgi?id=663761
2011-11-10 14:33:28 +00:00
fb97c28bca
gtktreeviewaccessible: use a value_destroy_func with the cell_info_by_index hash
...
This ensures that we don't leak any GtkTreeViewAccessibleCellInfo when
re-inserting a new one with the same key.
https://bugzilla.gnome.org/show_bug.cgi?id=663694
2011-11-10 14:49:30 +01:00
22807d8469
gtktreeviewaccessible: factor out cell_info_free()
...
https://bugzilla.gnome.org/show_bug.cgi?id=663694
2011-11-10 14:49:30 +01:00
f711da3d1b
uimanager: Work around deprecations
2011-11-09 23:45:58 -05:00
a7958f06e3
treeview: Work around deprecations
2011-11-09 23:42:11 -05:00
190c271986
Add a missing include
2011-11-09 22:03:10 -05:00
a78ab0cfa1
Drop use of GDK_DISABLE_DEPRECATED guards in gtk
...
We now use function attributes for deprecation so the build-breaking
guards are no longer needed.
2011-11-09 22:02:42 -05:00
91ae19768e
Bug 661997 - Gtk crashes when changing the TreeView model while ...
...
Simply stopping rubber banding in gtk_tree_view_set_model() eliminates
the crash. Reported by Thomas Perl.
2011-11-09 08:45:34 +01:00
7e22a5350c
Don't implement GApplication mainloop
...
Let the default GApplication implementation take care of it.
https://bugzilla.gnome.org/show_bug.cgi?id=658805
2011-11-09 00:22:52 -05:00
2783158f8d
treeview: Do a simple replace for gdk_window_get_pointer()
...
Replace it with the equivalent gdk_window_get_device_position() with the
core pointer.
2011-11-09 03:23:43 +01:00
439b9a3b1d
queryimmodules: Actually fix deprecation warnings
...
The previous patch still caused warnings. Ooops. That's what you get for
not compiling with -Werror.
2011-11-09 03:23:43 +01:00
28d3d6e039
treeview: Remove unused crack code
...
No, querying the pointer position in a draw callback is not a good idea.
No, setting FOCUSSED based on that position is not a good idea either.
2011-11-08 21:14:06 +01:00
fd93e08a7c
widget: Don't use deprecated symbols
...
Not even in deprecated functions!
2011-11-08 21:14:06 +01:00
d41732b729
widget: Deprecate gtk_widget_get_pointer ()
2011-11-08 21:14:06 +01:00
a1fb2c863b
treeview: Remove call to gtk_widget_get_pointer()
2011-11-08 21:14:06 +01:00
28d0403f17
paned: Pass x/y position to update_drag()
...
This way we get the coordinates from the right device instead of using
any random device.
2011-11-08 21:14:06 +01:00
80a23a2f2b
paned: Remove MOTION_HINT_MASK
...
It's not needed anymore. GDK does culling of events for us.
2011-11-08 21:14:06 +01:00
68bc011507
menuitem: WOrk around deprecation warnings
2011-11-08 21:14:06 +01:00
a12e12a56d
queryimmodules: Disable deprecaion warnings for deprecated header
2011-11-08 21:14:06 +01:00
40db65a85b
settings: Disable deprecaion warnings for deprecated header
2011-11-08 21:14:06 +01:00
c9b1e00c30
layout: Work around deprecation warnings
2011-11-08 21:14:05 +01:00
f9c664c69b
immodule: Disable deprecations before including deprecated header
2011-11-08 21:14:05 +01:00
e1f4bd6495
gtk: Empty gtkimmodule.h
...
Move the remaining struct definition into gtkimcontextinfo.h and include
that header in gtk.h. gtkimmodule.h is now an empty header. We should
probably deprecate it somehow.
This is also necessary so headers used in gtk .c files don't include
gtk.h which in turn includes all the deprecated headers which we want to
avoid so we can include them with deprecation warnings turned off.
2011-11-08 21:14:05 +01:00
ba05093fe7
build: Don't append to an accidentally existing file
2011-11-08 21:14:05 +01:00
c2da143aa6
immodule: Move private functions to a private header
2011-11-08 21:14:05 +01:00
bd97127e6c
immodule: Fix includes
...
Make includes not rely on gtkimmodule.h including gtk.h. This will be
important once we remove gtkimmodule from the include files.
That way, we can achieve not pulling deprecated headers automatically.
2011-11-08 21:14:05 +01:00
1c22053baf
window: Fix cast warnings
2011-11-08 21:14:05 +01:00
1425ecbc52
treeview: Fix warnings from fixing warnings
...
Warnings introdcued by fixing deprecation warnings in
2ead4c6038
2011-11-08 21:14:05 +01:00
adcd136f1e
icontheme: Get rid of deprecation warnings
...
Before including deprecated headers, disable deprecation warnings.
2011-11-08 21:14:05 +01:00
7cfe9051cc
cellrendererspinner: Ignore deprecation warnings
...
The cell renderer relies on deprecated functionality, so we need to
disable deprecations for included deprecated headers.
2011-11-08 21:14:05 +01:00
8f8269ad30
cellrendererspinner: Include correct header
2011-11-08 21:14:05 +01:00
9aa7e9f050
button: Don't call deprecated functions
2011-11-08 21:14:05 +01:00
a9134de5d3
assistant: Work around deprecation warnings
2011-11-08 21:14:05 +01:00
70f87b8bd5
gtk: Add a GTK_STATE_FLAG_WINDOW_UNFOCUSED widget state flag
...
This allows themes to style widgets differently according to whether the
toplevel window they are in is presented as focused.
https://bugzilla.gnome.org/show_bug.cgi?id=661428
2011-11-08 19:33:22 +00:00
f9d16f3923
themingengine: set the cairo extend to PAD when we're stretching bg
...
This avoids artifacts around the borders due to bilinear filtering cairo
applies to the surface pattern when stretching it.
https://bugzilla.gnome.org/show_bug.cgi?id=663522
2011-11-08 12:41:28 -05:00
3b436eec6d
css: start background-repeat
...
By default, a background image is stretched. Instead, it is worth to
have a tiled background.
This patch allows background surfaces to be repeated or not, and should
be compatible with future extensions and CSS.
https://bugzilla.gnome.org/show_bug.cgi?id=663522
2011-11-08 11:10:44 -05:00
ee7ac4fa44
Rename s/GtkCssRepeatStyle/GtkCssBorderRepeatStyle/g
...
https://bugzilla.gnome.org/show_bug.cgi?id=663522
2011-11-08 11:10:41 -05:00
085b98f470
[Quartz Bug 663182] NSImage throws an exception from _gtk_quartz_create_image_from_pixbuf()"
...
If a zero-sized NSImage calls lockfocus it throws an exception. Make sure that the image isn't zero-sized before calling lockfocus, and log a warning and return NULL if it is zero-sized.
Have the quartz version of gtk_drag_begin_idle return FALSE if the returned image is NULL.
2011-11-07 14:25:08 -08:00
42656dde57
Revert "[Quartz Bug 663182] NSImage throws an exception from _gtk_quartz_create_image_from_pixbuf()". Utterly screwed up. Sorry.
...
This reverts commit 8216324e4b3243e6955c
2011-11-07 13:57:10 -08:00
3243e6955c
Fix accidental paste error in 8216324
2011-11-07 13:18:14 -08:00
8216324e4b
[Quartz Bug 663182] NSImage throws an exception from _gtk_quartz_create_image_from_pixbuf()
...
If _gtk_quartz_create_image_from_pixbuf is given a pixbuf with size 0, 0
or which produces an NSImage with size 0.0, 0.0, it throws an exception
which Gtk doesn't handle.
your changes. Lines starting
2011-11-07 13:11:18 -08:00
d80953666e
Print preview: make cancel work
...
This makes cancels of a print preview work in the same way it
works for non-previews, i.e., the operation stops at the next
page boundary.
https://bugzilla.gnome.org/show_bug.cgi?id=662160
2011-11-07 13:10:24 -05:00
4ef61e2311
gtk: add annotations for some GtkRadio* constructors
...
Since constructors like gtk_radio_button_new_from_widget take an
instance of their type as the first argument, the gi scanner interprets
them as methods.
https://bugzilla.gnome.org/show_bug.cgi?id=661858
2011-11-06 16:50:57 +01:00
