| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
The design patterns using statusbar are no longer popular,
and it is pretty easy to make a statusbar yourself with boxes
and labels, if you need one. The only thing special about
GtkStatusbar was its window resize handle, but that has
been gone for a long time.
|
|
|
|
|
|
| |
The filechooser portal does not support this,
and we are defaulting to using the portal now.
Lets not offer a non-functional API.
|
|
|
|
| |
Accept both open_multiple and open-multiple.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
GtkDialog is too flexible in terms of UI (headerbars vs action bar,
etc), and has archaic APIs. It is time to retire it.
|
|
|
|
|
|
|
|
|
| |
These are being replaced by GtkFileDialog.
This commit only moves the headers for GtkFileChooserWidget and
GtkFileChooserDialog to deprecated/, and keeps the implementations
in gtk/, since they will eventually be salvaged into a private
GtkFileChooserWindow.
|
|
|
|
|
|
|
|
|
| |
It is getting replaced by GtkAlertDialog
This commit only moves the header to deprecated/,
and keeps the implementation in gtk/, since it will
eventually be salvaged into a private, dialog-free
widget.
|
|
|
|
|
|
|
|
|
|
| |
These are being replaced by GtkFontDialog
and GtkFontDialogButton
This commit only moves the headers for GtkFontChooserWidget and
GtkFontChooserDialog to deprecated/, and keeps the implementations
in gtk/, since they will eventually be salvaged into a private
GtkFontChooserWindow.
|
|
|
|
|
|
|
|
|
|
| |
These are being replaced by GtkColorDialog
and GtkColorDialogButton.
This commit only moves the headers for GtkColorChooserWidget
and GtkColorChooserDialog to deprecated/, and keeps the
implementations in gtk/, since they will eventually be
salvaged into a private GtkColorChooserWindow.
|
|
|
|
|
| |
Sadly, we can't just use an interger for a GPid on Windows, so just cast
it. Sounds silly for non-Windows, but that's life...
|
|
|
|
|
|
| |
Some of our tests use deprecated style context api.
Most of them should be ported to use global style
providers eventually. For now, ignore deprecations.
|
| |
|
|
|
|
| |
Eventually, most of these tests should be dropped.
|
| |
|
| |
|
|
|
|
|
|
| |
Without this, it is hard to trigger the
dialog. Event with this, we have to force
GtkMountOperation to use its own dialog.
|
|
|
|
|
|
| |
We want to drop cell renderers and tree models
in GTK 5. The functionality of GtkEntryCompletion
may be replaced by a new widget in GTK 5.
|
|
|
|
|
|
| |
These are a family of pretty specialized widgets, and
are very rarely used. Instead of porting them away
from GtkTreeView and GtkComboBox, deprecate them.
|
|
|
|
|
|
| |
The associated surface window handle is a HWND, not a HGDIOBJ.
Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
|
|
|
|
| |
Allow testing levels.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add a GtkColumnView scrolling performance test similar to the one used
previously in https://gitlab.gnome.org/GNOME/gtk/-/issues/3334.
The test creates a table with 20 columns and 10,000 rows and scrolls it
to a random position every frame, while measuring the frame times.
There is a commandline flag to pick the cell widget between none (for
benchmarking raw column view scrolling) and various label types. There
is also a commandline switch to disable automatic scrolling in case a
manual assessment is desired. Finally, there's an argument for
controlling the number of columns.
|
|
|
|
|
|
|
| |
This test is suddenly MASSIVELY faster.
I wonder why.
Could it be because inscription does exactly what it was made for?
|
|
|
|
|
| |
Not sure what changed here, but we want to
be able to build this without fontconfig too.
|
|
|
|
| |
This should help for figuring out #4325.
|
| |
|
| |
|
|
|
|
| |
This can only ever have worked by accident.
|
|
|
|
|
| |
This shows the minimal work required to hook up an
im context to a custom widget.
|
|
|
|
| |
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.
|