| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
This function has been replaced with gtk_render_insertion_cursor, but we
forgot to mark it as deprecated.
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
This setting was available since 2.90.x, so give it a 3.0 tag.
https://bugzilla.gnome.org/show_bug.cgi?id=670832
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
In this way the the code executed when the message_type property is set
to its default value (which is 0) gets actually run.
|
|
|
|
|
|
| |
The widget window is usually covered by the bin_window.
Its background color will become relevant when we introduce
kinetic scrolling with overshooting.
|
|
|
|
|
|
| |
The widget window is usually covered by the bin_window.
Its background color will become relevant when we introduce
kinetic scrolling with overshooting.
|
|
|
|
|
|
| |
The widget window is usually covered by the bin_window.
Its background color will become relevant when we introduce
kinetic scrolling with overshooting.
|
|
|
|
|
|
|
| |
_gtk_widget_set_device_window() is suppose to make accounting of
the topmost widget under the device at each time, so avoid setting
it on virtual crossing events as the device is already in another
window.
|
|
|
|
|
| |
This is all private api, no need to confuse gtk-doc with
doc comments for this.
|
|
|
|
| |
To get the time in milliseconds since the last frame
|
|
|
|
|
|
| |
The implicit grab on priv->event_window already warrants that this
widget is the only one getting events while the button is pressed,
so avoid the extra GTK+ grab here.
|
|
|
|
|
|
| |
If a drag operation is about to start when the drag
device is grabbed somewhere else, unset drag start x/y,
otherwise the drag will start anyway.
|
|
|
|
|
|
|
| |
Store the device, and unset private fields whenever the device
is shadowed by another GTK+ grab, so popping up menus while
selecting (i.e. press-and-hold) doesn't leave the entry in a
confused state.
|
| |
|
|
|
|
|
|
|
| |
* Restores the old padding
* Prelight on spin buttons
* Don't have a generic prelight background selector, as that got
picked up by things like images that should have a transparent bg.
|
| |
|
| |
|
|
|
|
| |
This is due to the use of round and nearbyint() function, which are C99 functions...
|
|
|
|
| |
Allows themes to set a different style on prelight.
|
|
|
|
|
|
| |
No need to subtract focus line width again, since the progressbar is
rendered starting at (0, 0).
This also fixes the entry-progressbar-coloring reftest.
|
|
|
|
| |
Reset style on visible headers, not on invisible ones
|
| |
|
|
|
|
|
|
|
|
| |
Instead of firing a 'quit' signal and expecting the application to do
something that will cause it to quit, just call the new
g_application_quit() API for ourselves.
https://bugzilla.gnome.org/show_bug.cgi?id=670485
|
|
|
|
|
|
|
|
| |
This seems a bit "too powerful" and unlikely to be used by most
applications. Remove it from now, until someone comes up with a strong
desire for it.
https://bugzilla.gnome.org/show_bug.cgi?id=670485
|
|
|
|
|
| |
The attached popup doesn't take ownership of its "parent" widget, so
ref_sink() was wrong, and caused widgets to be leaked.
|
|
|
|
| |
So we can easily catch it from the theme.
|
|
|
|
|
|
| |
Instead of having an input/output GdkWindow, make the widget no-window,
and use a separate input-only window for events, and paint on the parent
window directly.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
When a subclass of GtkEntry (e.g. GtkSpinButton) resizes the available
text area (by overriding the get_text_area_size vfunc), we need to
ensure we don't draw a possible progressbar over the part that got
removed from the text area.
This fixes drawing a progressbar in GtkSpinButton and in its subclasses,
such as GimpSpinScale, and makes Mitch happy too!
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=612283
|
|
|
|
|
|
|
| |
Mention that it is possible for it to be negative, or larger than the
current number of action groups.
https://bugzilla.gnome.org/show_bug.cgi?id=669947
|
|
|
|
|
|
|
| |
gtk_tree_view_set_hover_expand()
gtk_tree_view_column_set_clickable()
Signed-off-by: Jiří Klimeš <jklimes@redhat.com>
|
|
|
|
|
|
| |
Subclasses of GtkEntry could set a larger height request, so we need to
apply the same calculations to the insertion cursors than we do on the
PangoLayout to render it centered under all circumstances.
|
|
|
|
|
| |
If the color active swatch has been set a background image from the
theme, use it as an asset, and do not draw our custom thing.
|
|
|
|
|
| |
We still want to call into the background rendering code, to draw the
default background.
|
|
|
|
|
|
| |
Instead of GtkDrawingArea, since that calls in realize
gtk_style_context_set_background(). We don't want that to happen, given
that we do all the painting ourselves in _draw().
|
| |
|
|
|
|
|
| |
We don't want e.g. the swatch in GtkColorEditor to get the select badge
when it's clicked, so make this a property (on by default).
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=669116
|
|
|
|
|
|
| |
Forgot to increase the counter in the for loop, doing it now.
https://bugzilla.gnome.org/show_bug.cgi?id=669116
|
| |
|
|
|
|
|
|
|
|
| |
These should use :, not ::, though signals would use ::.
See
http://developer.gnome.org/gtk-doc-manual/unstable/documenting_syntax.html.en
and
http://developer.gnome.org/gtk-doc-manual/unstable/documenting_symbols.html.en
|
| |
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=669116
|
|
|
|
|
|
|
| |
For each page added/removed, notify all the other children changing
position.
https://bugzilla.gnome.org/show_bug.cgi?id=669116
|
|
|
|
|
|
|
| |
Instead of special-casing Adwaita, apply the half-width logic for themes
that have a scale slider with vertical proportions.
Also, simplify the rendering code a bit by factoring out the trough
sizing logic.
|