| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
... in gtk_popover_bind_model
and gtk_popover_menu_init
|
|
|
|
|
| |
And use it to determine whether we should actually interpolate between
stack sizes or not.
|
|
|
|
|
|
|
| |
We are trying to scroll the header in view together with the
focus row. The way this is implemented works fine when scrolling
up, but falls short when scrolling down. Fix this by making sure
that both the row and the header bar visible.
|
|
|
|
|
|
|
|
| |
We automatically pick up an adjustment from our parent
scrollable, but we failed to update it when it changes.
This is happening in the places sidebar, and it was causing
the focus-tracking to fail there, letting the focus move
out of view. With this change, the focus remains visible.
|
|
|
|
|
|
| |
Remove the code in the sidebar keypress handler that imperfectly
reproduces what GtkListBox already does: moving selection and
focus in response to arrow keys.
|
| |
|
|
|
|
| |
No need to set or unset adjustments explicitly.
|
|
|
|
|
|
| |
Make these go to the lower/upper boundary of the adjustment, like
Ctrl-PageUp/PageDown already do.
https://bugzilla.gnome.org/show_bug.cgi?id=309300
|
|
|
|
|
|
|
| |
This allows to use a custom font map for parts of the widget
hierarchy - this can be used for application-specific fonts.
https://bugzilla.gnome.org/show_bug.cgi?id=751812
|
|
|
|
|
|
| |
This will make things more understandable if an application
sets an empty preview text.
https://bugzilla.gnome.org/show_bug.cgi?id=725551
|
|
|
|
|
| |
Strictly speaking, this would only have to be special-cased inside
GtkDialog, but lets just skip it altogether.
|
|
|
|
|
|
| |
By accident, commit b9b17c3c2a434983452561c3 removed one line
that wasn't unused, but important for hiding close buttons on
dialogs. Bring it back.
|
|
|
|
|
| |
There is no reason to wait until map() to reset a type hint on the GDK
window. Just set it when it changes.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
1. This confuses the code as it's using the old type hint with the new
type hint on GDK window creation
2. It only existed as a workaround for old code that directly accessed
window->type_hint which hasn't been possible since 3.0.
|
|
|
|
|
| |
We don't add new children to the child's parent, we add them to ourself.
Because guess who a child's parent is?
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This reverts commit e215db6da21fc7c54f49b247afabc06a18d60513.
We are actually requiring non-NULL out arguments here now.
|
|
|
|
|
| |
Coverity pointed out that getting a class name requires
dereferencing the pointer, so only don't do it if it is NULL.
|
|
|
|
|
|
| |
We were printing a string in a warning after freeing it.
Also, fix an x/y typo that might cause popovers to be
mispositioned.
|
|
|
|
| |
Pointed out by coverity
|
|
|
|
| |
Not sure what I was thinking here. Coverity pointed this out.
|
| |
|
|
|
|
|
|
| |
I believe that first_column can only ever be NULL here if
last_column is NULL too, in which case we'd exited already.
But coverity doesn't see that, so add an explicit exit.
|
|
|
|
| |
Coverity uses these as clues to complain.
|
|
|
|
| |
Again, coverity takes these as clues to complain.
|
|
|
|
|
| |
Coverity has the annoying habit of guessing backwards that
if we check the value here, it might be NULL earlier.
|
|
|
|
| |
Coverity complained about these.
|
| |
|
|
|
|
|
|
|
| |
We don't care about the error here, but we were relying on
g_resources_get_info to zero the size even in case of error.
No need to do that, we can just check the return value. Plus,
it makes coverity happy.
|
|
|
|
|
|
|
| |
The way this code is written, we know that there is an item in
the hash table and the iter_next call will give it to us, so
no need to check the return value. Annotate the call to tell
coverity.
|
|
|
|
|
| |
We were already looking at the error anyway, but rewriting things
this way lets coverity see the light.
|
|
|
|
|
| |
Add some assertions that things are non-NULL when we know they
are, so that coverity gets it.
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, the (1<<31) value evaluated to the 64bit value
0xFFFFFFFF80000000
instead of
0x0000000080000000
Avoid this by explicitly casting the value to unsigned long long.
Also cast all values to unsigned long long to achieve consistency
and hopefully in the future get new values added the same way.
|
| |
|
|
|
|
|
| |
We keep the popover vertically tied to the selected row, but pick
up the horizontal position from the click / touch.
|
|
|
|
|
|
|
|
| |
We "fix" this signal the same way we did for GtkEntry and
GtkTextView: slightly change the signature so that the passed
widget may be a container other than a GtkMenu, and add a
property to explicitly opt in to receiving the signal in
this case.
|
|
|
|
|
| |
Use a popover for the context menu, and add a long press gesture
to allow opening it with touch.
|
|
|
|
|
| |
Use a popover for the context menu, and add a long press gesture
to allow opening it with touch.
|
|
|
|
| |
No need to count the strings first before iterating over them.
|
|
|
|
|
|
|
| |
With the name entry being in the header bar now, we no longer
get bindings working by just letting the key event bubble up,
we have to explicitly apply them on key events that the save
entry is not handling.
|
|
|
|
|
|
|
|
|
|
|
| |
They were updated in style-changed, causing the label to get set to
(None), then to the actual file name again a frame later, both of the
updates cause the GtkFileChooserButton to resize, possibly to the
minimal width, causing the layout to jump. Fix this by only updating
icon/label in style-updated when the icon theme actually changed, which
is the only case we care about here.
https://bugzilla.gnome.org/show_bug.cgi?id=752509
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
"Yo, we heard you like traversing NULL-terminated arrays to operate on
them, so we called g_strv_length() as the for condition, so you can
iterate the array while iterating the array."
Instead of making famed rapper and television producer Xzibit proud, we
should avoid calling g_strv_length() on an array while looping on the
array, to avoid quadratic complexity.
We do this in various places that deal with arrays of strings that we
cannot really guess are short enough not to matter — e.g. the list of
CSS selectors in the inspector, or the required authentication
information for printing.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previous commits changes the behavior of GtkPlacesSidebar, as it stops
handling persistent devices and only manages mounted networks, XDG
directories and bookmarks.
By radically breaking the previous behavior, we may have trouble
since we provide no alternatives to that besides the private widget
GtkPlacesView.
Fix that by showing the persistent devices when not showing Other
Locations item.
|