| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
The introduction of state broke some users which relied on
being able to set active in a notify::active handler.
https://bugzilla.gnome.org/show_bug.cgi?id=751754
|
|
|
|
|
|
|
| |
Instead of hardcoding an aspect ratio.
This will be replaced by min-height/max-height when we have them.
https://bugzilla.gnome.org/show_bug.cgi?id=751689
|
|
|
|
|
|
| |
It is deprecated and no longer needed, and,as observed in
https://bugzilla.gnome.org/show_bug.cgi?id=746253 it
interferes with turning off event compression.
|
|
|
|
|
|
| |
This file now uses round(), which was not available until C99, so include
fallback-c89.c instead of math.h, which includes math.h and does a fallback
implementation of round().
|
| |
|
|
|
|
|
|
|
|
| |
Make that variable go from 0.0 to 1.0 where 0.0 means inactive (slider
is on the left) and 1.0 means active (slider is on the right).
The math is simpler that way and most importantly the value is
independent of size.
|
|
|
|
| |
We can compute it on-demand whereever we need it.
|
| |
|
|
|
|
| |
This allows animating the trough, and saves a save/restore pair.
|
| |
|
|
|
|
|
| |
This api automatically takes care of dealing with disappearing
frame clocks, which we currently forget to and pay with crashes.
|
| |
|
|
|
|
|
|
| |
handle_x always corresponds to the visible position of the handle,
which is where we want to start the animation. Without this, repeated
keyboard activation will not always animate.
|
|
|
|
|
|
|
|
| |
Since we are storing positions here that depend on the allocation,
we need to update them in size-allocate. This fixes incorrect
positioning of the handle if the switch is active initially.
https://bugzilla.gnome.org/show_bug.cgi?id=734213
|
|
|
|
|
|
| |
Instead, calculate it on the spot in the tick callback, and
update handle_x in gtk_switch_set_active, based on the new
active property.
|
|
|
|
|
| |
Handle the unlikely case that a switch gets finalized while its
toggle animation is running.
|
|
|
|
|
| |
End any running toggle animation before setting the set,
otherwise things get confused.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
So switches can have shadows, too.
https://bugzilla.gnome.org/show_bug.cgi?id=733360
|
| |
|
|
|
|
|
| |
This makes switches more similar to other activatable widgets
like buttons or scales.
|
| |
|
|
|
|
|
|
| |
Mainly doing s/TARGET/BUBBLE/ on the fully ported widgets, but GtkTreeView
where the double click handler has moved to GTK_PHASE_TARGET so it runs
parallelly to the still existing event handlers.
|
|
|
|
|
|
|
|
| |
Event controllers now auto-attach, and the GtkCapturePhase only determines
when are events dispatched, but all controllers are managed by the widget wrt
grabs.
All callers have been updated.
|
| |
|
|
|
|
|
|
| |
A pan gesture is used to handle switch dragging, which is only triggered
by horizontal panning movements. A multipress gesture handles the cases
where clicking without dragging happens, just toggling the switch.
|
| |
|
| |
|
|
|
|
|
| |
Size vfuncs always get non-null out variables passed, so no need to
check for NULL.
|
|
|
|
|
|
|
|
| |
This commit makes it possible for GtkSwitch to indicate when
the underlying state changes with a delay, causing the switch
to temporarily go 'out of sync' with the underlying change.
https://bugzilla.gnome.org/show_bug.cgi?id=725648
|
|
|
|
| |
Instead of Return value:
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=707926
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We've recently a number of classes wholly. For these cases,
move the headers and sources to gtk/deprecated/ and adjust
Makefiles and includes accordingly.
Affected classes:
GtkAction
GtkActionGroup
GtkActivatable
GtkIconFactory
GtkImageMenuItem
GtkRadioAction
GtkRecentAction
GtkStock
GtkToggleAction
GtkUIManager
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=702996
|
|
|
|
| |
It is recommended to use GAction et al and GtkBuilder.
|
|
|
|
|
|
|
| |
Also use GDK_EVENT_{STOP,PROPAGATE} to make return
values clearer.
https://bugzilla.gnome.org/show_bug.cgi?id=696640
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
The same effect can now be achieved via
.switch { font-size: smaller; }
so there is no need to hardcode things.
|
| |
|
|
|
|
|
|
|
|
| |
Deprecate public API where appropriate and make it no-ops.
Remove all calls to it.
Get rid of the 'transition' css property.
For now, this means spinners don't animate anymore.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
This should have been called _create_observer
https://bugzilla.gnome.org/show_bug.cgi?id=667394
Fixup switch
|
| |
|
|
|
|
|
|
|
|
| |
This makes the behavior identical to other widgets which
handle button presses, and it avoids problems when placing
switches into a windows main toolbar.
https://bugzilla.gnome.org/show_bug.cgi?id=656986
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|