]> Pileus Git - ~andy/gtk/log
~andy/gtk
12 years agogdk: Add delta_x/y to scroll events
Michael Natterer [Mon, 23 Jan 2012 22:37:44 +0000 (23:37 +0100)]
gdk: Add delta_x/y to scroll events

gdk_event_get_scroll_deltas() can be used to retrieve those
values on smooth scroll events.

12 years agogdk: Add GDK_SCROLL_SMOOTH to GdkScrollDirection
Carlos Garnacho [Mon, 23 Jan 2012 22:45:26 +0000 (23:45 +0100)]
gdk: Add GDK_SCROLL_SMOOTH to GdkScrollDirection

This value will be used for smooth scroll events, as they'll
express the scrolling direction in terms of dx/dy.

12 years agogdk: Get the right event window for pointer emulated events
Carlos Garnacho [Mon, 27 Feb 2012 12:09:59 +0000 (13:09 +0100)]
gdk: Get the right event window for pointer emulated events

get_event_window() just checked on GDK_TOUCH_MASK, including for emulated
pointer events, so at the very least those should also match evmasks with
no touch events whatsoever

12 years agogdk: Set correct GdkModifierType on pointer emulated events
Carlos Garnacho [Mon, 27 Feb 2012 12:08:38 +0000 (13:08 +0100)]
gdk: Set correct GdkModifierType on pointer emulated events

12 years agogdk: translate correctly from touch events into emulated pointer events
Carlos Garnacho [Mon, 27 Feb 2012 11:32:01 +0000 (12:32 +0100)]
gdk: translate correctly from touch events into emulated pointer events

12 years agogdk: Don't treat touch events as button events
Matthias Clasen [Sun, 26 Feb 2012 05:04:39 +0000 (00:04 -0500)]
gdk: Don't treat touch events as button events

One more place where we assumed that touch events have a button
field.

12 years agogdk: Use the last alive grab in order to get the event window
Matthias Clasen [Thu, 1 Mar 2012 15:44:10 +0000 (10:44 -0500)]
gdk: Use the last alive grab in order to get the event window

If an active grab kicks in on a different window, _gdk_display_has_device_grab()
would still find the former implicit grab for the window below the pointer, thus
sending events to an unrelated place.

12 years agogdk: Don't mutate pointer events to touch events just because a grab says so
Carlos Garnacho [Tue, 21 Feb 2012 10:22:49 +0000 (11:22 +0100)]
gdk: Don't mutate pointer events to touch events just because a grab says so

If a grab with GDK_TOUCH_MASK kicks in due to a touch sequence emulating pointer
events, don't mutate the sequence into emitting touch events right away.

12 years agogdk: Let implicit touch grabs coexist with an implicit pointer grab
Carlos Garnacho [Tue, 21 Feb 2012 02:27:51 +0000 (03:27 +0100)]
gdk: Let implicit touch grabs coexist with an implicit pointer grab

Create the backing GdkTouchGrabInfo for touches even if the pointer
emulating touch sequence is already holding an implicit grab on a
window that didn't select for touch events.

12 years agogdk: Don't fully destroy the implicit touch grab on ::grab-broken
Carlos Garnacho [Tue, 21 Feb 2012 02:12:10 +0000 (03:12 +0100)]
gdk: Don't fully destroy the implicit touch grab on ::grab-broken

the backing GdkTouchGrabInfo will be needed if the overriding device
grab finishes before the touch does in order to send events back to
the implicit grab window. Instead, wait until the touch is physically
finished before removing the matching GdkTouchGrabInfo

12 years agogdk: Listen to touch events by default on the native window
Carlos Garnacho [Thu, 5 Jan 2012 00:04:15 +0000 (01:04 +0100)]
gdk: Listen to touch events by default on the native window

GDK will only receive touch events when dealing with a multitouch
device, so these must be transformed to pointer events if the
client-side window receiving the event doesn't listen to touch
events, and the touch sequence the event is from does emulate
the pointer.

If a sequence emulates pointer events, it will result in a
button-press, N motions with GDK_BUTTON1_MASK set and a
button-release event, and it will deliver crossing events
as specified by the current device grab.

12 years agogdk: Only trigger motion hints machinery on motion events
Carlos Garnacho [Thu, 5 Jan 2012 00:00:19 +0000 (01:00 +0100)]
gdk: Only trigger motion hints machinery on motion events

Touch events have no need for it, plus the concept behind
gdk_event_request_motions() doesn't wrap around multiple
touches within a device.

12 years agogdk: Have touch grabs behave like the implicit grab wrt crossing events
Carlos Garnacho [Wed, 4 Jan 2012 23:51:32 +0000 (00:51 +0100)]
gdk: Have touch grabs behave like the implicit grab wrt crossing events

These are equivalent to an implicit grab (with !owner_events), so
if the touch leaves or enters the grab window, the other window
won't receive the corresponding counter-event.

12 years agogdk: handle implicit touch grabs
Carlos Garnacho [Wed, 28 Dec 2011 23:06:45 +0000 (00:06 +0100)]
gdk: handle implicit touch grabs

If the touch sequence happens on a window with GDK_TOUCH_MASK set,
a GdkTouchGrabInfo is created to back it up. Else a device grab is
only created if the sequence emulates the pointer.

If both a device and a touch grab are present on a window, the later
of them both is obeyed, Any grab on the device happening after a
touch grab generates grab-broken on all the windows an implicit
touch grab was going on.

12 years agogdk: Add internal API to deal with touch implicit grabs
Carlos Garnacho [Wed, 28 Dec 2011 01:14:18 +0000 (02:14 +0100)]
gdk: Add internal API to deal with touch implicit grabs

The necessary information about a touch implicit grab is stored in
GdkTouchGrabInfo structs, these are meant to be transient to the
touch sequence.

12 years agogdk: Don't change window_under_pointer for pure touch events
Carlos Garnacho [Wed, 28 Dec 2011 01:09:59 +0000 (02:09 +0100)]
gdk: Don't change window_under_pointer for pure touch events

Only touch events that emulate the pointer do change it.

12 years agobutton: Handle touch events
Carlos Garnacho [Wed, 4 Jan 2012 23:35:04 +0000 (00:35 +0100)]
button: Handle touch events

Touch events don't generate crossing events themselves, so
do not rely on these to determine whether the button release
happened within the event window.

12 years agorange: Have slider jump to the pointer coordinates on touch devices
Carlos Garnacho [Wed, 4 Jan 2012 23:21:36 +0000 (00:21 +0100)]
range: Have slider jump to the pointer coordinates on touch devices

This widget is too narrow to make touch interaction tricky enough, so
don't add the penalty of having the slider run farther from the touch
coordinates if it happens to miss the slider.

12 years agomenus: Don't popdown submenus on button release for touch devices
Carlos Garnacho [Mon, 12 Dec 2011 19:07:57 +0000 (20:07 +0100)]
menus: Don't popdown submenus on button release for touch devices

This is so submenus stay open as the parent menu item is
pressed/released, since the user would typically lift the
finger in order to select a submenu item.

12 years agosettings: Deprecate gtk-touchscreen-mode
Carlos Garnacho [Mon, 12 Dec 2011 18:19:03 +0000 (19:19 +0100)]
settings: Deprecate gtk-touchscreen-mode

It's not used anywhere in GTK+ anymore.

12 years agorange: Remove gtk-touchscreen-mode usage
Carlos Garnacho [Mon, 12 Dec 2011 18:14:43 +0000 (19:14 +0100)]
range: Remove gtk-touchscreen-mode usage

Emulated crossing events with mode GDK_CROSSING_TOUCH_PRESS/RELEASE
already cater dynamically for the "don't prelight on touch devices"
usecase.

12 years agotogglebutton: Remove gtk-touchcreen-mode usage
Carlos Garnacho [Mon, 12 Dec 2011 18:11:41 +0000 (19:11 +0100)]
togglebutton: Remove gtk-touchcreen-mode usage

Emulated crossing events with mode GDK_CROSSING_TOUCH_PRESS/RELEASE
already cater dynamically for the "don't prelight on touch devices"
usecase.

12 years agomenushell: Remove gtk-touchscreen-mode usage
Carlos Garnacho [Mon, 12 Dec 2011 18:06:35 +0000 (19:06 +0100)]
menushell: Remove gtk-touchscreen-mode usage

This usage in a keybinding signal is hardly related to touchscreens,
so just remove it.

12 years agomenus: Remove gtk-touchscreen-mode from scrolling code
Carlos Garnacho [Mon, 12 Dec 2011 17:48:30 +0000 (18:48 +0100)]
menus: Remove gtk-touchscreen-mode from scrolling code

Scrolling is handled via ::captured-event dynamically, so remove
this now unused code.

12 years agomenus: Select the first item for touch devices
Carlos Garnacho [Mon, 12 Dec 2011 17:21:40 +0000 (18:21 +0100)]
menus: Select the first item for touch devices

This was done through gtk-touchscreen-mode. Now it is handled
dynamically on the current event source device.

12 years agomenus: Implement scrolling through event capture for touch devices
Carlos Garnacho [Mon, 12 Dec 2011 17:11:57 +0000 (18:11 +0100)]
menus: Implement scrolling through event capture for touch devices

This makes overflown menus scrollable via direct manipulation.
Once past the threshold, the item below the pointer is unselected
and scrolling starts.

12 years agomenus: Handle item selection for touch devices dynamically
Carlos Garnacho [Sun, 11 Dec 2011 17:46:50 +0000 (18:46 +0100)]
menus: Handle item selection for touch devices dynamically

Instead of using gtk-touchscreen-mode, the behavior changes depending
on the source device in use.

12 years agotooltips: Use the source device instead of gtk-touchscreen-mode
Carlos Garnacho [Sat, 26 Nov 2011 19:28:53 +0000 (20:28 +0100)]
tooltips: Use the source device instead of gtk-touchscreen-mode

This makes tooltips behavior dynamic based on the interacting device.

12 years agotests: Add new test for kinetic scrolling
Carlos Garcia Campos [Fri, 11 Feb 2011 12:46:35 +0000 (13:46 +0100)]
tests: Add new test for kinetic scrolling

12 years agotests: Add checkbox to enable kinetic scrolling in scrolled window test
Carlos Garcia Campos [Fri, 11 Feb 2011 12:45:21 +0000 (13:45 +0100)]
tests: Add checkbox to enable kinetic scrolling in scrolled window test

12 years agoviewport: select for touch events
Matthias Clasen [Thu, 1 Mar 2012 01:08:03 +0000 (20:08 -0500)]
viewport: select for touch events

This makes kinetic scrolling work with viewports where the
content does not otherwise select for button or touch events,
such as testscrolledwindow's label.

12 years agoscrolledwindow: Kinetic scrolling support
Carlos Garcia Campos [Fri, 11 Feb 2011 12:43:56 +0000 (13:43 +0100)]
scrolledwindow: Kinetic scrolling support

Kinetic scrolling is only done on touch devices, since it is
sort of meaningless on pointer devices, besides it implies
a different input event handling on child widgets that is
unnecessary there.

If the scrolling doesn't start after a long press, the scrolling is
cancelled and events are handled by child widgets normally.

When clicked again close to the previous button press location
(assuming it had ~0 movement), the scrolled window will allow
the child to handle the events immediately.

This is so the user doesn't have to wait to the press-and-hold
timeout in order to operate on the scrolledwindow child.

The innermost scrolled window always gets to capture the events, all
scrolled windows above it just let the event go through. Ideally
reaching a limit on the innermost scrolled window would propagate
the dragging up the hierarchy in order to keep following the touch
coords, although that'd involve rather evil hacks just to cater
for broken UIs.

12 years agogdk: Generate crossing events around touch devices' press/release
Carlos Garnacho [Sat, 3 Dec 2011 14:11:08 +0000 (15:11 +0100)]
gdk: Generate crossing events around touch devices' press/release

Anytime a touch device interacts, the crossing events generation
will change to a touch mode where only events with mode
GDK_CROSSING_TOUCH_BEGIN/END are handled, and those are sent
around touch begin/end. Those are virtual as the master
device may still stay on the window.

Whenever there is a switch of slave device (the user starts
using another non-touch device), a crossing event with mode
GDK_CROSSING_DEVICE_SWITCH may generated if needed, and the normal
crossing event handling is resumed.

12 years agogtk: Add a way to do event capture
Carlos Garcia Campos [Tue, 8 Feb 2011 13:49:31 +0000 (14:49 +0100)]
gtk: Add a way to do event capture

This patch adds a capture phase to GTK+'s event propagation
model. Events are first propagated from the toplevel (or the
grab widget, if a grab is in place) down to the target widget
 and then back up. The second phase is using the existing
::event signal, the new capture phase is using a private
API instead of a public signal for now.

This mechanism can be used in many places where we currently
have to prevent child widgets from getting events by putting
an input-only window over them. It will also be used to implement
kinetic scrolling in subsequent patches.

http://bugzilla.gnome.org/show_bug.cgi?id=641836

We automatically request more motion events in behalf of
the original widget if it listens to motion hints. So
the capturing widget doesn't need to handle such
implementation details.

We are not making event capture part of the public API for 3.4,
which is why there is no ::captured-event signal.

12 years agogtk: translate unhandled touch events to button events
Matthias Clasen [Sun, 26 Feb 2012 16:19:29 +0000 (11:19 -0500)]
gtk: translate unhandled touch events to button events

We don't want to fallback for 'random' touch sequences, since
that could lead to all kinds of pairedness and other violations.
Since the X server already tells us what touch events it would
have used for emulating pointer events, we just use that information
here.

12 years agogtk: Add a separate ::touch-event signal
Matthias Clasen [Fri, 24 Feb 2012 15:19:59 +0000 (10:19 -0500)]
gtk: Add a separate ::touch-event signal

12 years agogdk: Add some debug output for touch events and devices
Matthias Clasen [Wed, 29 Feb 2012 05:44:51 +0000 (00:44 -0500)]
gdk: Add some debug output for touch events and devices

12 years agoxi2: Translate touch events
Matthias Clasen [Thu, 1 Mar 2012 05:56:51 +0000 (00:56 -0500)]
xi2: Translate touch events

Translate XI_TouchBegin/Update/End to GDK_TOUCH_BEGIN/UPDATE/END
events.

At the same time,
set pointer-emulated flags on button events with XIPointerEmulated
and on touch events emulating the pointer.

12 years agogdk: Add touch event types and mask
Carlos Garnacho [Mon, 28 Feb 2011 19:53:42 +0000 (20:53 +0100)]
gdk: Add touch event types and mask

This commit introduces GDK_TOUCH_BEGIN/UPDATE/END/CANCEL
and a separate GdkEventTouch struct that they use. This
is closer to the touch event API of other platforms and
matches the xi2 events closely, too.

12 years agogdk: Add internal API to set "pointer emulated" flag on events
Carlos Garnacho [Wed, 28 Dec 2011 00:37:01 +0000 (01:37 +0100)]
gdk: Add internal API to set "pointer emulated" flag on events

This flag will be used for non-pointer events that are emulated
from eg. touch events, or pointer events being emulated.

12 years agogdk: Add GdkEventSequence
Carlos Garnacho [Tue, 1 Mar 2011 07:36:54 +0000 (08:36 +0100)]
gdk: Add GdkEventSequence

GdkEventSequence is an opaque pointer type that is used
to identify sequences of touch events that belong together.

12 years agoxi2: Use the new device types for touch-capable devices
Matthias Clasen [Thu, 1 Mar 2012 03:00:18 +0000 (22:00 -0500)]
xi2: Use the new device types for touch-capable devices

Any device with a XITouchClassInfo with num_touches > 0
qualifies as multitouch.

12 years agogdk: Add device types for touch-capable devices
Matthias Clasen [Thu, 1 Mar 2012 02:58:36 +0000 (21:58 -0500)]
gdk: Add device types for touch-capable devices

We introduce GDK_SOURCE_TOUCHSCREEN and GDK_SOURCE_TOUCHPAD
for direct and indirect touch devices, respecively. These
correspond to XIDirectTouch and XIDependentTouch in XI2.

12 years agoconfigure: Detect XInput 2.2
Carlos Garnacho [Mon, 28 Feb 2011 19:43:03 +0000 (20:43 +0100)]
configure: Detect XInput 2.2

12 years agoxi2: Add major/minor properties to XI2 device manager
Carlos Garnacho [Sat, 24 Dec 2011 13:33:24 +0000 (14:33 +0100)]
xi2: Add major/minor properties to XI2 device manager

This may be used to turn on/off the features that are added to
new XInput2 revisions.

12 years agobutton: don't be active when holding the mouse button outside the bounds
Cosimo Cecchi [Tue, 17 Jan 2012 22:14:23 +0000 (17:14 -0500)]
button: don't be active when holding the mouse button outside the bounds

GtkButton currently draws itself as active (pressed down) in case we're
pressing and holding the mouse pointer outside its bounds; this is
misleading though, since we won't activate the button unless the mouse
is released inside the button itself.
Fix this by only setting the ACTIVE state flag when the button is
actually pressed down.

https://bugzilla.gnome.org/show_bug.cgi?id=668141

12 years ago[l10n] Updated Estonian translation
Mattias Põldaru [Thu, 1 Mar 2012 17:20:22 +0000 (19:20 +0200)]
[l10n] Updated Estonian translation

12 years agobitmask: Don't allocate memory for small bitmasks
Neil Roberts [Thu, 9 Feb 2012 03:53:43 +0000 (04:53 +0100)]
bitmask: Don't allocate memory for small bitmasks

Code taken more or less verbatim from CoglBitmask.

12 years agobitmask: Split bitmask code into two
Benjamin Otte [Thu, 9 Feb 2012 00:44:59 +0000 (01:44 +0100)]
bitmask: Split bitmask code into two

This does nothing but turn all GtkBitmask functions into static inline
functions that call the gtk_allocated_bitmask_*() equivalent.

The implementation of the static functions has also been put into a
private header, to not scare people who want to see how things are
implemented.

12 years agobitmask: Allocate GtkBitmap data inline, not using GArray
Alexander Larsson [Thu, 9 Feb 2012 00:15:20 +0000 (01:15 +0100)]
bitmask: Allocate GtkBitmap data inline, not using GArray

This alone saves ~240k of GtkBitmap data after just starting up
nautilus.

12 years agobitmask: Make setters return a new value
Benjamin Otte [Wed, 8 Feb 2012 18:19:59 +0000 (19:19 +0100)]
bitmask: Make setters return a new value

(Actually, it's not a real 'new' value yet, but will be soon.

This is the first step to make bitmasks immutable.

12 years agotestgtk: Fix compiler warnings
Benjamin Otte [Thu, 1 Mar 2012 14:05:00 +0000 (15:05 +0100)]
testgtk: Fix compiler warnings

12 years agoFix up rendering of non-double-buffered overlays
Alexander Larsson [Thu, 1 Mar 2012 13:14:33 +0000 (14:14 +0100)]
Fix up rendering of non-double-buffered overlays

My previous fix for this broke the progress bar in epiphany. This fix
makes it work again, and keeps the gimp bug fixed.

Basically, whenever we do a non-double-buffered rendering we have to
flush the entire window as it might be drawn outside the double
buffering machinery.

12 years agocss: Fix variable
Benjamin Otte [Thu, 1 Mar 2012 12:46:11 +0000 (13:46 +0100)]
css: Fix variable

And you'd think I'd test my code...

12 years agoUpdated Telugu Translations
Krishnababu Krothapalli [Thu, 1 Mar 2012 09:22:58 +0000 (14:52 +0530)]
Updated Telugu Translations

12 years agocssprovider: Redo styles as an array
Benjamin Otte [Thu, 1 Mar 2012 05:40:15 +0000 (06:40 +0100)]
cssprovider: Redo styles as an array

Saves even more memory and avoids an extra copy during assigning.

12 years agocss: Fix fallout
Benjamin Otte [Thu, 1 Mar 2012 04:28:41 +0000 (05:28 +0100)]
css: Fix fallout

.. from carelessly merging 85b1b9b77816198040d9437ea2e1231c47e41e68

12 years agox11: Mark unused variables as such
Benjamin Otte [Thu, 1 Mar 2012 04:16:04 +0000 (05:16 +0100)]
x11: Mark unused variables as such

We cannot get rid of the variables because they are assigned in a macro
inside Xlib. And this causes a warning in the xlib from Fedora 17
onwards.

12 years agogtk-demo: Fix gcc warnings
Benjamin Otte [Thu, 1 Mar 2012 04:32:09 +0000 (05:32 +0100)]
gtk-demo: Fix gcc warnings

12 years agoDon't use hashtables for storing css rule properties
Alexander Larsson [Wed, 15 Feb 2012 16:06:30 +0000 (17:06 +0100)]
Don't use hashtables for storing css rule properties

This saves a lot of memory

12 years agotests: add a test for GtkOverlay position style classes
Cosimo Cecchi [Mon, 6 Feb 2012 16:26:57 +0000 (11:26 -0500)]
tests: add a test for GtkOverlay position style classes

https://bugzilla.gnome.org/show_bug.cgi?id=669342

12 years agooverlay: add left/right/top/bottom style classes to overlay children
Cosimo Cecchi [Fri, 3 Feb 2012 20:33:30 +0000 (15:33 -0500)]
overlay: add left/right/top/bottom style classes to overlay children

When we're allocating children of GtkOverlay, compare their allocation
with the overlay one, and set left/right/top/bottom style classes if the
overlaid widget touches one or more of the overlay edges.

https://bugzilla.gnome.org/show_bug.cgi?id=669342

12 years agooverlay: do not to set uninitialized values in the main allocation
Cosimo Cecchi [Wed, 29 Feb 2012 17:21:59 +0000 (12:21 -0500)]
overlay: do not to set uninitialized values in the main allocation

gtk_widget_translate_coordinates() can fail in case the widget is not
realized or there's no common ancestor. Don't use the x/y values
returned by that method in that case, since their value is undefined.

12 years agooverlay: factor out gtk_overlay_get_main_widget_allocation
Cosimo Cecchi [Wed, 29 Feb 2012 17:20:25 +0000 (12:20 -0500)]
overlay: factor out gtk_overlay_get_main_widget_allocation

This will be used later in a subsequent commit.

12 years agoscrolledwindow: draw a box in the junction between the two scrollbars
Cosimo Cecchi [Fri, 3 Feb 2012 19:03:52 +0000 (14:03 -0500)]
scrolledwindow: draw a box in the junction between the two scrollbars

If there's a junction between the two scrollbars (i.e. they're both
visible), draw a background with a style class there, so the theme can
style it.

https://bugzilla.gnome.org/show_bug.cgi?id=669335

12 years agostylecontext: add a "scrollbars-junction" style class
Cosimo Cecchi [Fri, 3 Feb 2012 19:03:28 +0000 (14:03 -0500)]
stylecontext: add a "scrollbars-junction" style class

It will be used in the following commit.

https://bugzilla.gnome.org/show_bug.cgi?id=669335

12 years agoUpdated Spanish translation
Daniel Mustieles [Wed, 29 Feb 2012 13:11:30 +0000 (14:11 +0100)]
Updated Spanish translation

12 years agoUpdated Brazilian Portuguese translation
Jonh Wendell [Wed, 29 Feb 2012 12:32:51 +0000 (09:32 -0300)]
Updated Brazilian Portuguese translation

12 years agomenu: Deactivate the menu if the GdkWindow is withdrawn
Rob Bradford [Mon, 27 Feb 2012 12:35:25 +0000 (12:35 +0000)]
menu: Deactivate the menu if the GdkWindow is withdrawn

If the display server or GDK hides the window - fire the "deactivate" signal
to ensure that the internal state is consistent.

This patch also ensures that the "deactivate" signal will not be fired for a
menu that is not active.

Bug: https://bugzilla.gnome.org/show_bug.cgi?id=670881

12 years agoUpdated Swedish translation
Daniel Nylander [Wed, 29 Feb 2012 07:21:38 +0000 (08:21 +0100)]
Updated Swedish translation

12 years agoUpdated Swedish translation
Daniel Nylander [Wed, 29 Feb 2012 07:06:50 +0000 (08:06 +0100)]
Updated Swedish translation

12 years agoUpdated Brazilian Portuguese translation
Jonh Wendell [Tue, 28 Feb 2012 20:45:35 +0000 (17:45 -0300)]
Updated Brazilian Portuguese translation

12 years agocellrendereraccel: override get_preferred_width, not get_size
Cosimo Cecchi [Tue, 28 Feb 2012 20:04:31 +0000 (15:04 -0500)]
cellrendereraccel: override get_preferred_width, not get_size

Since GtkCellRendererText moved to WFH requests, our get_size
implementation is ignored. We should override get_preferred_width
instead. This fixes the accel renderer being clipped to a wrong size
when trying to edit its shortcut.

12 years agocellrendereraccel: override background on the event box, not the label
Cosimo Cecchi [Tue, 28 Feb 2012 20:03:02 +0000 (15:03 -0500)]
cellrendereraccel: override background on the event box, not the label

Since that's what renders the background. Otherwise the event box will
get the regular window background and will look bad.

12 years agoFix typo in Finnish translation
Tommi Vainikainen [Tue, 28 Feb 2012 05:39:37 +0000 (07:39 +0200)]
Fix typo in Finnish translation

12 years agowayland: Categorise menus, popups and combo boxes as Wayland popup windows
Rob Bradford [Mon, 27 Feb 2012 14:30:58 +0000 (14:30 +0000)]
wayland: Categorise menus, popups and combo boxes as Wayland popup windows

Once we've made them popup windows we must also implement the popup_done event
handler on the shell surface listener. The best we can currently do is to hide
the window. This will then signal up to GTK which could then deactivate the
appropriate menu (see https://bugzilla.gnome.org/show_bug.cgi?id=670881)

12 years agowayland: Store the device that does a grab for a window on the window
Rob Bradford [Mon, 27 Feb 2012 14:06:22 +0000 (14:06 +0000)]
wayland: Store the device that does a grab for a window on the window

This allows us to get the device if we need to make the window a popup. This
relies on the side effect that GTK calls into GDK to take a grab before the
popup window is shown.

12 years agowayland: Call wl_shell_surface_set_{popup,transient,toplevel} before attach
Rob Bradford [Mon, 27 Feb 2012 12:55:25 +0000 (12:55 +0000)]
wayland: Call wl_shell_surface_set_{popup,transient,toplevel} before attach

The requests only have an effect if you call them before the buffer is
attached to the surface.

12 years agoChange FSF Address
Javier Jardón [Mon, 27 Feb 2012 13:01:10 +0000 (13:01 +0000)]
Change FSF Address

12 years agogtk/gtkapplication.c: Do not use gtk_dialog_run()
Javier Jardón [Mon, 27 Feb 2012 11:09:03 +0000 (11:09 +0000)]
gtk/gtkapplication.c: Do not use gtk_dialog_run()

12 years agodemos/gtk-demo/infobar.c: Do not use gtk_dialog_run()
Javier Jardón [Mon, 27 Feb 2012 11:07:08 +0000 (11:07 +0000)]
demos/gtk-demo/infobar.c: Do not use gtk_dialog_run()

12 years agodemos/gtk-demo/colorsel.c: Do not use gtk_dialog_run()
Javier Jardón [Mon, 27 Feb 2012 10:59:41 +0000 (10:59 +0000)]
demos/gtk-demo/colorsel.c: Do not use gtk_dialog_run()

12 years agoAdd a deprecation mark to draw_insertion_cursor
Paolo Borelli [Mon, 27 Feb 2012 16:35:57 +0000 (17:35 +0100)]
Add a deprecation mark to draw_insertion_cursor

This function has been replaced with gtk_render_insertion_cursor, but we
forgot to mark it as deprecated.

12 years agogdk: don't install gdkversionmacros.h twice
Cosimo Cecchi [Mon, 27 Feb 2012 16:45:12 +0000 (11:45 -0500)]
gdk: don't install gdkversionmacros.h twice

Since it's generated, we install the header by putting it into
gdkinclude_HEADERS, so it's wrong to put it again into
gdk_public_h_sources.
This fixes the build.

12 years agoUpdated Spanish translation
Daniel Mustieles [Mon, 27 Feb 2012 16:10:55 +0000 (17:10 +0100)]
Updated Spanish translation

12 years agoAdd some documentation around deprecations
Matthias Clasen [Mon, 27 Feb 2012 12:56:29 +0000 (07:56 -0500)]
Add some documentation around deprecations

12 years agogtk: Use versioned deprecations
Matthias Clasen [Mon, 27 Feb 2012 12:10:59 +0000 (07:10 -0500)]
gtk: Use versioned deprecations

This patch changes all uses of GDK_DEPRECATED(_FOR) in gtk headers
by the versioned variants, GDK_DEPRECATED_IN_3_x(_FOR). At the same
time, we add GDK_AVAILABLE_IN_3_x annotations for all API additions
in 3.2 and 3.4.

12 years agogdk: correct a 'Since' note in the docs
Matthias Clasen [Mon, 27 Feb 2012 12:09:29 +0000 (07:09 -0500)]
gdk: correct a 'Since' note in the docs

gdk_keymap_get_modifier_state was only introduced in 3.4, not 3.2.

12 years agogdk: Use versioned deprecations
Matthias Clasen [Mon, 27 Feb 2012 12:07:48 +0000 (07:07 -0500)]
gdk: Use versioned deprecations

This patch changes all uses of GDK_DEPRECATED(_FOR) in gdk headers
by the versioned variants, GDK_DEPRECATED_IN_3_x(_FOR). At the same
time, we add GDK_AVAILABLE_IN_3_x annotations for all API additions
in 3.2 and 3.4.

12 years agoAdd versioned deprecation macros
Matthias Clasen [Mon, 27 Feb 2012 12:04:30 +0000 (07:04 -0500)]
Add versioned deprecation macros

These macros follow the recent changes in GLibs deprecation
setup. We now annotate deprecated functions with the version
they were deprecated in, and you can define the macro
GDK_VERSION_MIN_REQUIRED to cut off deprecation warnings for
'recent' deprecations.

At the same time, we introduce version annotations for new API
and allow you to avoid 'recent' API additions by defining
GDK_VERSION_MAX_ALLOWED.

12 years ago[l10n] Updated Kazakh translation
Baurzhan Muftakhidinov [Mon, 27 Feb 2012 08:18:51 +0000 (14:18 +0600)]
[l10n] Updated Kazakh translation

12 years agoCorrect Since: tag for gtk-application-prefer-dark-theme
Matthias Clasen [Mon, 27 Feb 2012 01:48:34 +0000 (20:48 -0500)]
Correct Since: tag for gtk-application-prefer-dark-theme

This setting was available since 2.90.x, so give it a 3.0 tag.

https://bugzilla.gnome.org/show_bug.cgi?id=670832

12 years agoupdate Punjabi Translation
A S Alam [Sun, 26 Feb 2012 10:23:07 +0000 (15:53 +0530)]
update Punjabi Translation

12 years agoupdate Punjabi Translation
A S Alam [Sun, 26 Feb 2012 10:20:48 +0000 (15:50 +0530)]
update Punjabi Translation

12 years agoUpdated Belarusian translation.
Kasia Bondarava [Sun, 26 Feb 2012 09:51:50 +0000 (12:51 +0300)]
Updated Belarusian translation.

12 years agoUpdated Persian Translation
Arash Mousavi [Fri, 24 Feb 2012 18:22:41 +0000 (21:52 +0330)]
Updated Persian Translation

12 years agoUpdated POTFILES.skip
Piotr Drąg [Fri, 24 Feb 2012 18:26:18 +0000 (19:26 +0100)]
Updated POTFILES.skip

12 years agogdk: pull more precondition checks into the generic gdkscreen.c
Michael Natterer [Fri, 24 Feb 2012 15:44:44 +0000 (16:44 +0100)]
gdk: pull more precondition checks into the generic gdkscreen.c

12 years agoSet infobar css classes permanently
Paolo Borelli [Tue, 21 Feb 2012 22:42:39 +0000 (23:42 +0100)]
Set infobar css classes permanently

The message-type css classes must be in the widget context all the time,
not only when drawing, otherwise they are not propagated to the
children, for instance a label in the InfoBar must inherit the
color. Add a corresponding reftest.

https://bugzilla.gnome.org/show_bug.cgi?id=670555

12 years agoInit the InfoBar message_type to GTK_MESSAGE_OTHER
Paolo Borelli [Thu, 23 Feb 2012 23:16:33 +0000 (00:16 +0100)]
Init the InfoBar message_type to GTK_MESSAGE_OTHER

In this way the the code executed when the message_type property is set
to its default value (which is 0) gets actually run.