| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
| |
If icon lookup fails or if loading it fails later, just always
fall back to the built in image-missing icon. Nobody is handling
missing icons in a sane way anyway.
If you *truly* need to handle missing icons, you need to manually
use gtk_icon_theme_has_icon().
While changing the loading code I also fixed an issue where it
was always passing "png" to pixbuf, now it also handles "xpm" if
that is the filename suffix.
|
|\
| |
| |
| |
| | |
Fix building recent GTK master on Visual Studio
See merge request GNOME/gtk!1369
|
| |
| |
| |
| | |
Instead, on Windows when it is not available, include io.h for close()
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Instead, rely on people passing fallbacks explicitly.
Alternatively, GThemedIcon provides the functionality to create
fallbacks, which is what GtkImage and the testsuite now use.
That method is slightly better, too, so the expected test results
have been updated accordingly.
|
| |
| |
| |
| | |
This way, we can remove gtk_icon_theme_choose_icon() completely.
|
| |
| |
| |
| |
| |
| |
| |
| | |
There is no way to query contexts or do anything useful with them.
So don't keep track of them and don't make them an argument in public
APIs with the docs saying "I don't know what to use here, maybe read
some spec somewhere".
|
| |
| |
| |
| |
| |
| |
| |
| | |
Those functions are unused and the documentation says "Returns some
random number that the icon theme creator chose" which does not seem at
all useful and an implementation detail.
So get rid of it.
|
| |
| |
| |
| | |
It's unused.
|
| |
| |
| |
| |
| |
| | |
Most users were just forgetting to set the proper flags.
And flags aren't the right way to set this anyway, it was just
acceptable as a workaround during GTK3 to not break API.
|
| |
| |
| |
| |
| |
| |
| | |
Widgets would not use them properly. In fact, the only user was using
them wrong.
As icons are loaded async by default, this call isn't necessary.
|
|/
|
|
|
|
|
| |
The API encouraged wrong usage - most of the users were indeed wrong.
Use the correct version instead:
gtk_icon_theme_get_for_display (gtk_widget_get_display ())
|
|
|
|
|
|
|
|
| |
We only have implementations of this on X11 and Win32,
so make it available as backend api there.
Update all callers to use either the backend api, or
just monitor 0.
|
|
|
|
|
| |
This is set on the GTask and lower priority will be loaded before,
this can be used to prioritize some icons for preloading.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
If you want to test font stuff, it's 2020 and we have an inspector.
|
|
|
|
| |
They shouldn't be (and aren't) used anymore.
|
|
|
|
| |
Only build and run the performance tests if we have sysprof.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is an attempt to see how we can use sysprof data
in our tests to extract useful performance numbers.
Use it as a wrapper around any GTK+ process:
./testperf ./gtk4-widget-factory
Currently, it repeatedly runs the given commandline,
extracts the first css validation time from the resulting
syscap file, and prints out the min/max/avg of the runs
at the end.
This relies on the environment variable GTK_DEBUG_AUTO_QUIT
to cause the process to exit soon after launch.
|
|
|
|
| |
That way, it's correct in subclass's init functions.
|
| |
|
| |
|
| |
|
|
|
|
| |
We must take mime types into account when checking.
|
|
|
|
|
| |
This one tests nested drop sites and interaction between
DND and other gestures.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Remove arguments from the constructor.
For actions, we now default to COPY, which is the most common one
that we should enable by default (MOVE requires handling deletion
on the the source side, and ASK only makes sense if we have
multiple actions).
For the content provider, we add a new ::prepare signal where
it should be provided just-in-time.
|
|
|
|
|
| |
Add GdkDrag back to signals, drop ::drag-data-delete,
and replace it with a boolean in ::drag-end.
|
|
|
|
|
|
| |
Now that drop targets are event controllers,
we can just use gtk_event_controller_get_widget.
Update all callers.
|
|
|
|
|
|
| |
Since drop targets are now just event controller,
gtk_widget_add/remove_controller works just fine
for them.
|
|
|
|
|
|
| |
These no longer have any effect.
Update all callers.
|
|
|
|
|
|
| |
It is a bit unfortunate that we need to extend the
lifespan of the drop object by keeping our own
ref, but I don't see a better way of doing it.
|
| |
|
| |
|
| |
|
|
|
|
| |
Make this mostly work again.
|
| |
|
| |
|
| |
|