| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
- Split out a common function
- Implement hfw properly.
|
|
|
|
| |
This was accidently lost when merging baseline support.
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=698433
|
|
|
|
|
|
|
|
|
|
|
|
| |
This replaces the previously hardcoded calls to gdk_window_set_user_data,
and also lets us track which windows are a part of a widget. Old code
should continue working as is, but new features that require the
windows may not work perfectly.
We need this for the transparent widget support to work, as we need
to specially mark the windows of child widgets.
https://bugzilla.gnome.org/show_bug.cgi?id=687842
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A button is highlighted if the private variable in_button is TRUE.
This variable is set when the pointer is over the button and cleared when
it left the button. When a button is hidden while there is the pointer over
it, GTK generates a leave notification event, in_button is set to FALSE.
But when a button is removed from a container but not destroyed, it is
unrealized and loose its window. It cannot receive the leave notification
event and in_button stay TRUE. So when the button get a new parent it is still
highlighted.
https://bugzilla.gnome.org/show_bug.cgi?id=676890
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=676429
|
|
|
|
|
| |
All buttons use the same paint function these days. States are managed
correctly so this was just leftovers from GTK 1 or GTK 2.
|
|
|
|
| |
Don't just conditionally set it on buttons.
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Just set the property unconditionally.
https://bugzilla.gnome.org/show_bug.cgi?id=667394
|
|
|
|
|
|
|
|
| |
This should have been called _create_observer
https://bugzilla.gnome.org/show_bug.cgi?id=667394
Fixup switch
|
|
|
|
|
|
|
| |
Setting state flags is actually needed here since this function is called by
GtkButton subclasses which add their specific state flags as a parameter.
This reverts commit e868b8d6ea04af6e31d7075d09508689873c0df5.
|
|
|
|
|
|
| |
Only allow one of 'action-name' or 'related-action' to be set.
https://bugzilla.gnome.org/show_bug.cgi?id=667394
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is the interface for GtkWidgets that can be associated with an
action on a GtkAppicationWindow or associated GtkApplication.
It essentially features 'action-name' and 'action-target' properties
with some associated convenience API.
This interface is implemented by GtkButton and GtkToolButton.
https://bugzilla.gnome.org/show_bug.cgi?id=667394
|
|
|
|
|
|
|
|
| |
Since we allocate the standard CSS border to the button now, and center
the child accordingly, there's no need for an additional inner-border
style property. Deprecate it and ignore its values.
https://bugzilla.gnome.org/show_bug.cgi?id=666600
|
|
|
|
|
|
| |
And allocate the button children according to it as well.
https://bugzilla.gnome.org/show_bug.cgi?id=666600
|
|
|
|
|
|
| |
We'll use it later to compute the child offsets.
https://bugzilla.gnome.org/show_bug.cgi?id=666600
|
| |
|
| |
|
|
|
|
|
| |
Mostly making sure that return values and varargs don't loose
their docs.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit introduces a new setting, gtk-visible-focus, backed
by the Gtk/VisibleFocus X setting. Its three values control how
focus rectangles are displayed.
'always' is equivalent to the traditional GTK+ behaviour of always
rendering focus rectangles.
'never' does what it says, and is intended for keyboardless
situations, e.g. tablets.
'automatic' hides focus rectangles initially, until the user
interacts with the keyboard, at which point focus rectangles
become visible.
https://bugzilla.gnome.org/show_bug.cgi?id=649567
|
|
|
|
|
|
| |
This drops the AtkText implementation, and also strips handling
of children out. Instead of listening for enter/leave/press/released,
just listen for state changes on the widget.
|
| |
|
| |
|
|
|
|
|
|
|
| |
Use the GtkStyleContext accessors for boxed properties where possible,
to reduce allocations.
https://bugzilla.gnome.org/show_bug.cgi?id=650420
|
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=650382, spotted
by Alexander Larsson.
|
|
|
|
|
|
| |
It's wrong, and makes it impossible to theme the button properly.
https://bugzilla.gnome.org/show_bug.cgi?id=646882
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=646882
|
|
|
|
| |
Mostly correcting it's to its and changing some , to .
|
|
|
|
|
| |
This was not handled consistently, but the default handler
does useful things, so we should always chain up.
|
|
|
|
|
| |
gcc 4.6.0 has started to warn about set-but-unused variables.
So don't do that, then.
|
|
|
|
|
| |
Partly fixes bug #640282, noticed by Christian Persch. buttons were
clobbering the insensitive flag when updating their state.
|
|
|
|
|
|
|
|
|
|
|
| |
event is available
Buttons may also be activated at any time from gtk_widget_activate()
or related functions. In that case, just do the 'show the button
as pushed for a short amount of time' trick, but don't actually
try to grab the keyboard device.
Signed-off-by: Federico Mena Quintero <federico@gnome.org>
|
| |
|
|
|
|
|
|
| |
This change does not introduce any functionality change, mostly
cosmtic cleanups, like re-linebreak when introduced annotations messed
up indentation or whitespace errors fixes.
|
|
|
|
|
|
| |
The detail strings weren't in use anymore, and the state
argument is now a GtkStateFlags. GtkToggleButton has been
updated as well.
|
|
|
|
|
|
| |
Based on patches by Javier Jardón.
https://bugzilla.gnome.org/show_bug.cgi?id=629955
|
|
|
|
| |
Mostly replaces gtk_widget_style_get with gtk_style_context_get_style
|
|
|
|
|
|
|
|
|
| |
All current users of this CSS property have been updated to deal
with a GtkBorder.
Also a 0 border width has been set in the default CSS to ensure
GtkStyleContext and GtkThemingEngine always provide a non-NULL
pointer for this property.
|
|
|
|
|
| |
There is now code to handle this for one-item widgets (such as GtkButton)
in gtk_widget_set_state_flags()
|
| |
|
| |
|
| |
|