| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Its very easy to get extra references to the NativeDialog so that
when you release your last reference any visible dialog is not
hidden. We handle this by adding a destroy method similar to how
you destroy regular toplevels.
|
| |
|
|
|
|
|
|
| |
It's not a hugely complicated file, but it's easier to deal with some of
the details of tooltip windows styling if we have a UI file to edit,
instead of source code.
|
| |
|
|
|
|
| |
They are not needed.
|
| |
|
|
|
|
| |
Adapt to the changes in the previous release.
|
|
|
|
| |
Adapt to the changes in the previous commit.
|
|
|
|
|
|
| |
Use element names levelbar, trough, block, and some style
classes on the block nodes: .discrete, .continuous, .empty,
.level-low, etc.
|
|
|
|
|
| |
We don't need to add .view - its already added, and shouldn't
really be needed in the first place.
|
|
|
|
| |
Use the selection element name.
|
|
|
|
| |
Use the selection name.
|
|
|
|
|
|
|
| |
Use the text CSS node for rendering text, and the selection node
for rendering selected text, avoid gtk_style_context_save, update
states of all CSS nodes, and use the proper states when querying
style properties.
|
|
|
|
|
|
|
| |
Use a CSS node with name selection, like we do for entries
and labels. Unlike those widgets, we currently don't user
gtk_render_background, but just use the background color.
That will require more effort.
|
|
|
|
| |
The element name is...cellview.
|
|
|
|
| |
Adapt to changes in the previous commit.
|
|
|
|
| |
Adapt to the changes in the previous commit.
|
|
|
|
|
| |
This adds new possibilities for themes to render the selection
in fancy ways.
|
|
|
|
|
|
|
|
| |
Calling gtk_render_background for each rectangle in the region
leads to suboptimal and sometimes weird results. Getting this
right requires more work in Pango first. Go back to just rendering
a single background, and clip it to the selection region. This
matches what GtkLabel does.
|
|
|
|
|
| |
Labels in the object tree are application data. Ellipsize them
to avoid growing extremely wide if the data is bogus.
|
| |
|
|
|
|
| |
Adapt to changes in the previous commit.
|
|
|
|
| |
Adapt to the changes in the previous commit.
|
|
|
|
|
| |
This adds new possibilities for themes to render the selection
in fancy ways.
|
|
|
|
|
| |
Now that tooltips are csd again, the CSS wasn't quite working
anymore.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
At the time gtk_window_move() or gtk_window_resize() get called, there
is no way to predict if a popup window will actually draw its shadow, so
applying an offset in this case may end up with a wrong size or
positioning for such windows.
Changing the logic in gtk_window_should_use_csd() as previously done to
address that issue will cause some other breakage as popup windows may
not draw a shadow but still need CSD.
So best is to actually apply client side decorations offset for regular,
top level windows only. This is actually a lot simpler and safer and
less likely to cause additional breakage.
Bugzilla: https://bugzilla.gnome.org/show_bug.cgi?id=756618
|
|
|
|
|
|
| |
Adapt to the changes in the previous commit. Note that tooltip
appearance is currently affected by tooltips having lost their
csd nature, due to a regression.
|
| |
|
|
|
|
| |
Start from GtkAccelLabel and walk the tree downwards.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Cover letter
Having a single header file for all autocleanups definitions was a
reasonable stop-gap measure, but now GTK+ is starting to use G_DECLARE_*
macros. This means that every class using a G_DECLARE_* macro will need
to include "gtk.h" to avoid compiler warnings, which is not acceptable.
By moving the G_DEFINE_AUTO* use to the header that defines the type we
allow using the G_DECLARE_* macros without sacrificing the ability to
include only the needed files when deriving from a class.
* Commit
This commit changes all includes relative to GtkWindow to define their
own autocleanup macros.
|
|
|
|
|
| |
When compiling inside GTK we also use the GTK_COMPILATION guard, as the
GtkPlacesView and GtkPlacesViewRow widgets are shared with Nautilus.
|
|
|
|
|
| |
This allows GtkPlacesViewRow to use G_DECLARE_FINAL_TYPE without having
to include gtk.h.
|
|
|
|
| |
And the compiler warning that comes with it.
|
|
|
|
|
| |
Otherwise we won't be able to use G_DECLARE_* macros internally to GTK
without generating warnings, or without including gtk.h itself.
|
|
|
|
|
| |
We must set the construct-only "type" to GTK_WINDOW_POPUP, otherwise
this ends upo being a regular toplevel.
|
|
|
|
| |
Instead of a style class.
|
|
|
|
|
| |
GtkTooltip does a lot of set up on the GtkWindow it uses internally. We
should move that code to a separate class to keep it contained.
|
|
|
|
|
|
| |
There was one more call to gtk_style_context_save here that I
overlooked. We can get rid of it by just setting the element name
on the drawing area.
|
| |
|
| |
|
| |
|
|
|
|
| |
Adapt to the changes in the previous commit.
|
|
|
|
| |
Adapt to the changes in the previous commit.
|
|
|
|
|
| |
Use a CSS node with name rubberband to draw the rubberband
selection.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When I added the draw_layer vfunc it accidentally got passed a cairo_t
that was configured with to draw in the viewport coordinate space (rather
than the buffer coordinate space). This makes things unnecessary complex,
because you have to convert between the two.
The pixel cache is shared between the text and the layers, so there is
no way to use draw_layer to get a stationary overlay effect. Thus it makes
much more sense for the draw_layer vfunc to draw in the buffer space.
Just changing this would break ABI for existing code, so this is fixed
by adding new layer types and deprecating the old ones.
Also, we use the new layer types to fix gtk3-widget-factory.
https://bugzilla.gnome.org/show_bug.cgi?id=757856
|
|
|
|
| |
This change belongs to the iconview rubberband changes.
|
|
|
|
| |
Adapt to the changes in the previous commit.
|
|
|
|
| |
Adapt to the changes in the previous commit.
|