| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
so that dragging into the 'trashcan' is detected
|
|
|
|
|
| |
Add some toggle and check buttons to test that they
work as expected as GtkActionables.
|
|
|
|
| |
We weren't setting the state of the stateful actions.
|
|
|
|
| |
Check buttons aren't toggle buttons anymore.
|
|
|
|
|
|
|
|
| |
This is less flexible than a glob pattern, but it is
explicitly case-insensitive, to match the behavior
on Windows.
Fixes: #3705
|
|
|
|
|
|
| |
We can test internal apis in our testsuite now,
so move the text history tests there, to have them
run in ci.
|
| |
|
|
|
|
| |
This reveals some issues with scale handling.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This is useful for testing the interaction of arrows, shadows
or offsets with popover positioning.
|
| |
|
|
|
|
| |
The inspector no longer sets a window icon.
|
|
|
|
|
|
|
|
|
|
| |
According to OpenGL spec, a shader object will only be flagged
for deletion unless it has been detached; when a program object
is deleted, those shader objects attached to it will be detached
but not deleted unless they have already been flagged for deletion.
So we shall detach a shader object before it is deleted, and delete
it before the program object is deleted best.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It was used by all surfaces to track 'is-mapped', but still part of the
GdkToplevelState, and is now replaced with a separate boolean in the
GdkSurface structure.
It also caused issues when a widget was unmapped, and due to that
unmapped a popover which hid its corresponding surface. When this
surface was hidden, it emitted a state change event, which would then go
back into GTK and queue a resize on popover widget, which would travel
back down to the widget that was originally unmapped, causing confusino
when doing future allocations.
To summarize, one should not hide widgets during allocation, and to
avoid this, make this new is-mapped boolean asynchronous when hiding a
surface, meaning the notification event for the changed mapped state
will be emitted in an idle callback. This avoids the above described
reentry issue.
|
|
|
|
|
| |
This will actually make it resize on-demand, as the default size is the
size used when computing the window size when the size is not fixed.
|
|
|
|
|
|
| |
This will not work on X11 because it's too late to resize, due to
resizing being asynchronous i.e. it won't be complete before we need to
draw.
|
|
|
|
|
| |
It's not emitted, and everyone should use the GdkSurface::layout signal
from now on.
|
|
|
|
| |
The gtk_window_resize() API is going away, so remove this test.
|
|
|
|
|
| |
This means the window needs to be marked as non-resizable, otherwise it
won't shrink.
|
|
|
|
|
| |
Replace the usage of gtk_window_resize() with
gtk_window_set_default_size() where possible.
|
|
|
|
| |
... as discussed in the meeting.
|
|
|
|
| |
That demo lives in gtk-demo now.
|
|\
| |
| |
| |
| | |
Wip/otte/for master
See merge request GNOME/gtk!2855
|
| |
| |
| |
| |
| | |
We were still unreffing a listmodel where the reference wasn't ours
anymore.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
GtkTreeView.get_tooltip_context() takes an inout X and Y coordinates,
but the "out" side is a side effect: the conversion from widget-relative
to bin window-relative coordinates is not documented, and can be done
using public API, if needed.
GtkIconView.get_tooltip_context() follows the same pattern, and takes
two inout arguments for the coordinates, but it does not change them any
more, after GtkIconView's bin window was dropped in commit 8dc5e13e.
There's really no point in having these `inout` arguments, and while
GtkTreeView and GtkIconView are certainly de-emphasised in GTK4, and we
nudge developers to move to the new list views, we should take advantage
of the API break to remove warts.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Using GtkCssSection in public headers here may be
ok from the C perspective, since it all ends up in
the same library anyway. But it causes circular
dependency problems for our gir files that are still
split by namespace.
To avoid this problem, copy the GtkCssLocation struct
struct as GskParseLocation, and pass take two of them
instead of a GtkCssSection in the error callback.
Update all users.
Fixes: #2454
|
|/ |
|
| |
|
| |
|
|
|
|
| |
Doesn't exist anymore.
|
|
|
|
|
|
|
|
|
|
| |
Copy the format conversion code from GdkMemoryTexture
so we can produce all formats, and test them all.
The upload fast paths assume that the stride is a
multiple of four, so some of the padding values cause
it to fail. Apart from that, things seem to work for
all combinations.
|
|
|
|
|
|
|
|
|
|
|
| |
Create textures with various characteristics (alpha, premultiplication,
stride) that trigger different code paths in the gl texture upload
function, and show the resulting images. If all goes well, they all
should look the same.
On my system, this tests texture upload for memory formats
GDK_MEMORY_B8G8R8A8_PREMULTIPLIED, GDK_MEMORY_R8G8B8A8, and
GDK_MEMORY_R8G8B8, and it works with both gl and gles.
|
|\
| |
| |
| |
| | |
columnview: Simplify column constructors
See merge request GNOME/gtk!2622
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Drop gtk_column_view_column_new_with_factory and
just make gtk_column_view_column_new accept a
nullable factory. This follows what we've been
doing elsewhere.
Update all callers.
|
|/
|
|
|
|
| |
This API is kinda stuck in the GdkEvent days, we now negotiate ownership
of the input sequence via GtkGestures. Remove it as it reflects a way to
work that was not exactly accurate and it will turn plainly wrong soon.
|
|
|
|
|
|
| |
Replace most remaining uses of GTK+ in the docs and
user-visible strings by GTK. Also remove some leftover
"Was added in 3.x" sentences from the docs.
|
|
|
|
|
| |
This is meant to help with figuring out entry
selection drag issues.
|
|
|
|
|
|
| |
That is what it is.
Fixes: #2790
|
|\
| |
| |
| |
| | |
Filter constructors
See merge request GNOME/gtk!2360
|
| |
| |
| |
| |
| |
| |
| | |
Make functions like gtk_custom_sorter_new() return
the actual type they construct.
Update all callers.
|
| |
| |
| |
| |
| |
| |
| | |
Make functions like gtk_custom_filter_new() return
the actual type they construct.
Update all callers.
|
|/
|
|
| |
Make this show 'paintings in paintings'.
|
|
|
|
|
| |
This can help in tracking various things down,
from picking to clipping.
|
|
|
|
|
|
|
| |
Now that both arguments to the _new_with_factory() constructors
are nullable, there's no good reason to keep a separate _new()
around. Just make gtk_list_view_new() and gtk_grid_view_new()
take both a model and a factory.
|
|
|
|
|
|
|
|
| |
Change the apis in GtkListView, GtkColumnView and
GtkGridView to be explicitly about GtkSelectionModel,
to make it obvious that the widgets handle selection.
Update all users.
|
| |
|
|
|
|
|
| |
Replace all uses on check buttons by the corresponding
check button api.
|