| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Make it possible to set foreground or background alpha in the
builder ui support for Pango attributes.
|
|
|
|
|
| |
We don't need to store our own copy of the colors anymore,
now that PangoRenderer can do alpha.
|
|
|
|
|
|
| |
A few attribute types were missing from the support:
rise, letterspacing, fallback, font features. Add support
for these.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
The first Escape clears the search entry, the second Escape
closes the dialog.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Since we're dealing with networks, terms like "Eject" or
the eject button are misleading, since we're not actually
ejecting but disconnecting.
Fix that by showing the appropriate icon and tooltip.
|
|
|
|
|
| |
As pointed out by Cosimo, we should sort the
items according to their path.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We are not showing the URL of network locations
anymore, since they are distracting and not
necessary.
The code, however, forgot to cleanup the URL,
so we are still showing the URL for network
locations.
Fix that by properly cleanup the URL for network
locations.
|
|
|
|
|
|
|
|
|
|
|
| |
The .button:link .label selector matches any label "inside" a
link button. And a label inside the context menu counts as inside
for this purpose. This causes the text-decoration property to
leak into the context menu, even though the property is not
inherited. Avoid this by tightening the selector to
.button:link > .label.
https://bugzilla.gnome.org/show_bug.cgi?id=753451
|
|
|
|
|
|
|
|
|
|
|
|
| |
When we connect to a server, the default and expected
behavior is going to the default location, which usually
is the home directory or a writable directory.
GtkPlacesSidebar behaves properly, while GtkPlacesView
doesn't.
Fix that by jumping to the default locations instead of
the root location.
|
| |
|
| |
|
| |
|
|
|
|
| |
clang doesn't like those.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
This was just not implemented, and the sidebars solid white
background color was inherited by undershoot rectangle.
https://bugzilla.gnome.org/show_bug.cgi?id=753391
|
|
|
|
|
|
|
|
|
|
|
|
| |
Don't use gtk_widget_show_all() on row widgets because that would
unconditionally show all of its children. This might be unwanted in case
the row implementation wants to keep some of its children hidden.
This commit changes it to use show() instead of show_all() and relies on
the row widget to control the visibility of its children itself as
appropriate.
https://bugzilla.gnome.org/show_bug.cgi?id=753392
|
| |
|
| |
|
|
|
|
|
|
|
| |
Manual resizing for CSD windows only worked with the bottom
right corner. This extends it to work for all corners and edges.
https://bugzilla.gnome.org/show_bug.cgi?id=753329
|
|
|
|
|
|
| |
Make days gray that are not in the current month.
https://bugzilla.gnome.org/show_bug.cgi?id=753357
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
GtkFileSystem has a complicated way to handle cancellables.
You keep the cancellable pointer that is returned by
_gtk_file_system_get_info and similar methods so that you can
cancel the operation, but you do not own a reference to it.
The only place where it is ok to unref a cancellable is in
your callback, which gets handed a cancellable that you need
to unref at the end. You are expected to compare it to the
pointer you stashed away to find out if the operation has
already been superseded by a newer call, in which case you
disregard the results.
GtkFileChooserButton was following these rules for most of
the cancellables it keeps around, but it was sometimes unreffing
the cancellables that are stored in the model, which could lead
to refcount confusion and crashes. This commit makes it follow
the rules for that case too, which fixes the crash in the bug
below, and does not show up any leaks in valgrind under light
testing.
https://bugzilla.gnome.org/show_bug.cgi?id=737804
|
|
|
|
|
|
|
|
|
|
|
| |
The recent change to the enum declaration for GtkCssChange actually
relied on compiler-dependent behavior, which also breaks the build on
some non-GCC compilers, such as Visual Studio. As noted in the
G_STATIC_ASSERT line just beneath this declaration, we need to change
this enum declaration to #define's, in order to fix the build in such
situations.
https://bugzilla.gnome.org/show_bug.cgi?id=752814
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
The type of xalign property of GtkLabel is float, not int. Using wrong type
crashes GtkFileChooser on x86_64 when compiling with clang.
https://bugzilla.gnome.org/show_bug.cgi?id=753284
|
|
|
|
|
|
|
| |
Don't return that a key event was handled when the corresponding
scrollbar can not scroll.
https://bugzilla.gnome.org/show_bug.cgi?id=753256
|
|
|
|
|
|
| |
- provide insensitive button state for GtkCalendar buttons
https://bugzilla.gnome.org/show_bug.cgi?id=753230
|
|
|
|
|
|
|
| |
It works just as well here as it does in the file chooser, and
this lets us unify the right-click and long-press behavior a bit.
We used to switch directly to the editor on long-press, now we
can show the popover, just as we do on right-click.
|
|
|
|
|
|
|
|
|
|
|
| |
Only a drag context which was created with 'drag_begin' will be
guaranteed to have a source window at all times. Thus, in finalize we
cannot assume we can retrieve a GdkDisplay from the source_window
pointer since it may be NULL. Though, the display is only needed for
contexts created via 'drag_begin' thus we can retrieve it after
checking that is the case.
https://bugzilla.gnome.org/show_bug.cgi?id=749339
|
|
|
|
|
|
|
| |
These operations will require a grab on the WM side, so we can spare the
attempt from the WM to take a grab when we're certain it won't suceed.
https://bugzilla.gnome.org/show_bug.cgi?id=752327
|
|
|
|
|
|
|
|
|
| |
This is implicitly done for us in the case of grabs on windows from other
groups, but we must perform this check explicitly for grabs with
owner_events=True on windows from the same group, in that case the window
would handle the events as if there was no grab.
https://bugzilla.gnome.org/show_bug.cgi?id=752327
|
|
|
|
|
| |
Blocking a signal should be paired with unblocking.
Spotted by Krzesimir Nowak
|
|
|
|
|
|
|
|
| |
We were failing to construct the child if an image was set
before constructed (e.g. in the init() function of a button
subclass).
https://bugzilla.gnome.org/show_bug.cgi?id=753048
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=753060
|
| |
|
|
|
|
|
|
|
|
|
| |
We need to be mapped to have a gtk_surface and thus be able to do
requests on it so we need to save the modal hint and apply it when we
get mapped so that code that sets the hint before showing a window
doesn't get ignored.
https://bugzilla.gnome.org/show_bug.cgi?id=753138
|
|
|
|
|
|
|
| |
Otherwise if we get mapped again we'll try to use an invalid
gtk_surface and the compositor will disconnect us.
https://bugzilla.gnome.org/show_bug.cgi?id=753138
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=752920
|