| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
|
|
|
|
|
| |
Clarify that only parts of the font name are used.
https://bugzilla.gnome.org/show_bug.cgi?id=758367
|
|
|
|
|
|
|
|
| |
These are not supposed to be supported by gtk-doc¹
¹https://bugzilla.gnome.org/show_bug.cgi?id=758137
https://bugzilla.gnome.org/show_bug.cgi?id=758175
|
|
|
|
| |
GTK+ is licensed under the terms of the GNU LGPL v2.1+.
|
|
|
|
| |
GTK+ is released under the terms of the GNU LGPL v2.1+.
|
|
|
|
|
|
| |
There is no GNU Lesser General Public License version 2; it's either GNU
Library General Public License version 2, or GNU Lesser General Public
License version 2.1.
|
|
|
|
|
| |
Since it's using Lesser GPL, use version 2.1; there is no Lesser GPL v2,
as it was called 'Library GPL' prior to v2.1.
|
|
|
|
|
|
|
|
| |
Copy-pasta from GPL instead of LGPL.
Also, there is no GNU Lesser General Public License version 2; either
it's the GNU Library General Public License version 2, or it's the GNU
Lesser General Public License version 2.1.
|
|
|
|
|
| |
The code is released under the terms of the LGPL v2.1+, as is the rest
of the GTK+ code.
|
|
|
|
|
| |
I didn't meant to make this different from any other file
in GTK+ when I added it.
|
|
|
|
|
| |
This was showing up in glade, which creates freestanding
popovers.
|
|
|
|
|
|
|
|
| |
Just like it happens for window dragging, we're likely to not see the
matching button release for this event, so we must reset the controller
manually here.
https://bugzilla.gnome.org/show_bug.cgi?id=758661
|
|
|
|
| |
Sad face for me.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
tracker:uri-is-descendant/parent has the unfortunate side effect of
rendering the collation mechanisms in the database useless, so those
require full table scans to be validated.
Performing these as pure string comparisons will perform much better,
as those allow the underlying sqlite to rely on its own collation
to perform the search, which can be significantly faster with many
elements in the database.
https://bugzilla.gnome.org/show_bug.cgi?id=758407
|
|
|
|
|
|
|
| |
This could produce strange warnings as it is currently passed to
tracker:uri-is-* sparql functions, as these expect no NULLs.
https://bugzilla.gnome.org/show_bug.cgi?id=758407
|
|
|
|
|
|
|
|
| |
Just return the default value for those properties.
Testcase included.
https://bugzilla.redhat.com/show_bug.cgi?id=1281234
|
|
|
|
|
|
| |
If the window has not yet been created, then we can't set the invisible
cursor yet. This can happen in situations where the widget is in a
revealer with type-to-search functionality.
|
|
|
|
|
| |
For @import, we want to emit the error as part of the @import statement,
not as part of the new file.
|
|
|
|
|
|
|
|
| |
Since we are now interpreting button press events and
make our own double-click determination, we should not
handle double-click events that are generated by GDK.
https://bugzilla.gnome.org/show_bug.cgi?id=757950
|
|
|
|
|
|
|
|
|
|
|
|
| |
When loading a nonexisting CSS file using
gtk_css_provider_load_from_file() or gtk_css_provider_load_from_path()
we would emit the error using a NULL scanner. Don't do that, because
we'll have a NULL section in that case and error handlers don't like
that.
Testcase attached.
https://bugzilla.redhat.com/show_bug.cgi?id=1277959
|
|
|
|
|
|
|
|
|
| |
Signal handlers expect a section to be present, so provide them with
one.
New testcase included.
https://bugzilla.gnome.org/show_bug.cgi?id=757240
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since the change to use GtkPlacesView we don't want to show
internal storage on the sidebar.
In our case we were checking for drive_can_eject and
drive_is_media_removable.
However for some external hard drives it's reported that they
are not ejectable nor the have removable media. So the only
attribute that they have different from internal drives is that
they can be stopped.
So check for if the drive can be stopped to decide if it is
external or internal.
On the way realized we don't need to check for the mounts associated
with the volume to know if the volume can be ejected or not. So remove
that code.
https://bugzilla.gnome.org/show_bug.cgi?id=756589
|
|
|
|
|
|
|
|
| |
Since 4ebb5781eaf332da3f8ce5ffb5ecc8668a56f118 ID has a specific value,
while it used to be the same as NAME. Thus, explicitly list ID as a
radical change just like NAME.
https://bugzilla.gnome.org/show_bug.cgi?id=757397
|
|
|
|
|
|
|
| |
This reverts commit 1536710dbac58f0d46a6c308370e1e3864bf42e0.
Because of the revert at
commit 0dc66f5125196ee10c7e851b75f16e9f5669eb49.
|
|
|
|
|
|
| |
This reverts commit cf51c4f6dbd91dae1878a0cb0d08b24c67e15232.
This change broke binding api.
|
|
|
|
|
|
| |
This is a private object, don't export its symbols.
https://bugzilla.gnome.org/show_bug.cgi?id=756978
|
|
|
|
|
| |
make check checks this for writable properties, and fails now that
we've made this property writable.
|
|
|
|
|
| |
We were copying an iterator that sometimes was not initialized,
which caused debugger warnings in VS2015.
|
|
|
|
|
|
| |
Using lookup_icon() and lookup_by_gicon() with a size multiplied by a
scaling factor is almost certainly going to get worse results than using
their for_scale() variants.
|
|
|
|
|
|
|
| |
A GdkPixbuf has no scaling factor, so drawing directly from it can only
using a scale of 1, to avoid blurry, fuzzy icons.
You should be using gtk_render_icon_surface() anyway.
|
|
|
|
|
|
|
|
| |
It looks like the param spec for interpolate-size was
copied from the line above it, which is a read only property.
There is a setter for interpolate-size, and it is implemented in
set_property().
|
|
|
|
|
|
|
| |
This fixes the ability to sublcass GtkHeaderBar from a UI template which
contains a custom <child type="title"> element.
https://bugzilla.gnome.org/show_bug.cgi?id=757544
|
|
|
|
|
|
|
| |
An error in the loading function was making us load the file from
the first data dir repeatedly, instead.
https://bugzilla.gnome.org/show_bug.cgi?id=757377
|
|
|
|
|
| |
This causes a hickup in the new css node machinery, causing
the default-value test to fail.
|
|
|
|
|
|
|
|
| |
If the svg pixbuf loader is not available, we end up with criticals
from gtk_css_image_icon_theme_draw because gtk_icon_info_load_symbolic
returns NULL without setting an error.
Avoid this by propagating the load error.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The search window of a tree view was implemented by showing without
making it visible by by positioning it outside the screen edge. This is
not possible on Wayland, so implement another method for being able to
enter text into a non-visible entry.
The new method is implemented by, before showing the window, pass the
key event directly to the IM context backing the entry. If the key
event triggered the context to commit new text or change the preedit
content, the search window is shown, and from that point the key events
are forwarded directly to the entry widget.
https://bugzilla.gnome.org/show_bug.cgi?id=756780
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=756780
|
|
|
|
|
|
|
| |
Instead of alternating between search dialog and search window, use
search window everywhere.
https://bugzilla.gnome.org/show_bug.cgi?id=756780
|
|
|
|
|
|
| |
Only get the class once per object, not once per property.
And don't canonicalize the property name, g_object_class_find_property
does that already.
|
| |
|
|
|
|
|
|
| |
Use CHILD1/CHILD2 instead of 0 and 1, always use the same order and
don't check for child NULL-ness, because it will be done in
gtk_paned_set_child_visible anyways.
|
|
|
|
|
|
| |
The function is now safe to use.
https://bugzilla.gnome.org/show_bug.cgi?id=735341
|
|
|
|
|
|
|
|
|
|
|
|
| |
Avoid crashes when passing an invalid location to a
gtk_text_buffer_get_iter_at_*() function.
A boolean is returned to know if @iter has been set to the exact
location.
Unit tests are added.
https://bugzilla.gnome.org/show_bug.cgi?id=735341
|
|
|
|
|
|
|
|
|
| |
When the search entry is shown, the 'special' nature of
., ~ and / should not trigger the location entry, because
that interrupts the search and is likely not what the
user intended.
https://bugzilla.gnome.org/show_bug.cgi?id=756505
|
|
|
|
|
|
|
|
|
|
| |
We have to remove the page itself from the intermediate box
first, before removing the box from the notebook. Otherwise,
reffing the page to keep it alive is ineffective: the box
gets destroyed, and that destruction recurses over the page.
This fixes the problem in
https://bugzilla.gnome.org/show_bug.cgi?id=756385
|
|
|
|
|
|
|
| |
GtkMenu and GtkMenuBar, the two implementations of GtkMenuShell in GTK,
already draw it.
Furthermore, rendering a background here will overdraw any rendering
that the subclass will do, such as arrows for scrolling menus.
|
|
|
|
|
|
| |
When the entry completion is popped up from a timeout, we may
not have a device. In that case, don't call gdk_device_grab,
do avoid criticals.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The current situation is somewhat sad, with the path
label totally misaligned throughout the rows.
This is fixed by using a size group for the path labels,
so they all have the same allocated size (with the max
of 15 chars). Also, instead of hiding the eject button,
set it child-invisible, so it is hidden and yet it's size
is allocated by GtkBox.
https://bugzilla.gnome.org/show_bug.cgi?id=757303
|
|
|
|
|
|
|
| |
On Drag'n'Drop actions across system boundaries (VM host to guest), the
happen to be null.
https://bugzilla.gnome.org/show_bug.cgi?id=757298
|
|
|
|
|
|
|
|
|
|
| |
If a window is decorated, we need to draw the frame and shadow, even if
it is app-paintable - it's just nonsense to have a frame that we handle
events on, but expect the app to paint it. (We paint the titlebar in
any case.) If a client wants to handle all painting, it should use an
undecorated window.
https://bugzilla.gnome.org/show_bug.cgi?id=756886
|