| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
AdwFlap has the same issues as all of our other adaptive widgetry.
In order to get rid of the issues caused by it, we need new widgetry
that can be manually used with AdwAdaptiveState.
This commit ports the main window to the new AdwUtilityPaneView
widget. This widget is a simplified alternative to AdwFlap, and
for our use case it's a drop-in replacement.
|
|
|
|
|
|
|
|
|
|
|
|
| |
AdwAdaptiveState is a new utility that is part of
AdwWindow and AdwApplicationWindow. It allows for arbitrary
changes at specific breakpoints, meaning that we can move,
show, and hide widgets normally without any undefined behavior
or flickering.
AdwAdaptiveState allows us to remove the GtkRevealers that we
used previously, as there's only a simple crossfade transition
between states now.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
(cherry picked from commit c1ebea52a5f653dcd55a20c10b8f74423c0d19dd)
|
|
|
|
|
|
|
| |
Declare what sort of hardware we support and the minimum
display size Nautilus is usable on. This allows applications
like Software to display hardware information or hide the app
on incompatible hardware.
|
|
|
|
|
|
| |
List the form factors the app was designed for in the desktop
file. This is so desktop environments like Phosh and Plasma Mobile
can show or hide the app in the correct contexts.
|
|
|
|
|
|
|
|
|
|
| |
The flatpak jobs are broken currently, because the tracker-miners project
fails to build due to missing upower-glib depenedency. It is used to tweak
the behavior when running on battery. It used to be automatically disabled
until the following MR:
https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/1121. I suppose
it is safe to disable this functionality as our flatpak isn't meant for
production. Let's explicitely disable that to fix our pipeline.
|
|
|
|
|
|
|
|
|
|
|
| |
The commit e2969a9c29d0d171038fcb35d8baa5a7df372191 introduced an assertion
statement to ensure that the `g_file_get_basename` returned non-NULL string.
Unfortunately, the assertion has an inverted condition. This leads to crashes
in the `get_unique_target_file` function for files that don't have the
`edit-name` attribute set (i.e just a few GVfs backends). Let's fix the
inverted condition.
Fixes: https://gitlab.gnome.org/GNOME/nautilus/-/issues/2825
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
The flatpak@aarch64 is not allowed on other branches than master but
is allowed on forks. It would be nice to allow manual run in those cases
to save resources, but to allow testing aarch64-specific fixes.
|
|
|
|
|
|
| |
The pages job is allowed on forks currently. It is not desired to run it
there and it is going to fail there anyway. Let's explicitly disable this
job on forks.
|
|
|
|
|
| |
The only/except keywords were deprecated in favor of rules. Let's
replace them with rules.
|
|
|
|
|
|
|
| |
The pages job is not running currently on master. This is because
`only: refs: $CI_DEFAULT_BRANCH` is not supported (e.g. see
https://gitlab.com/gitlab-org/gitlab/-/issues/29591). Let's fix that
using one of the suggestions from that issue.
|
|
|
|
|
|
|
| |
With non-local drops, when the value is initially NULL, we get
warnings because of some of the checks done on a NULL value. This was
a regression from 3d17ed252960cbc9848aea0b398a4a74ef05623c. Return
action copy before any check dependent on a dropped value.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Add a check to assert nautilus_files_view_drop_proxy_received_uris is
not called with an empty source uri list.
Make nautilus_dnd_perform_drop return whether the drop event was
actually handled. Adjust callers accordingly.
Fixes: https://gitlab.gnome.org/GNOME/nautilus/-/issues/2787
|
|
|
|
|
|
| |
This change makes the rubberband to have rounded corners,
making it consistent with other elements such as buttons and text entries,
which also have rounded corners.
|
| |
|
| |
|
|
|
|
| |
(cherry picked from commit 2c2a8394650da755a04c9cb3be357c9f57d35579)
|
|
|
|
|
|
|
|
|
| |
We are still leaking NautilusViewItem in several places. Essentially
every NautilusViewItem (and thus every NautilusFile) ever created is
leaked. In list-base, the queue in real_add_files is freed, but not
the items themselves. Make sure to also free the results of
g_list_model_get_item() and our macro listitem_get_view_item which now
calls gtk_tree_list_row_get_item.
|
|
|
|
|
|
|
| |
view-item holds a reference for the cell and the cell holds a ref
to the item. In order to break this cycle, let's make item_ui
a weak pointer in view-item. The cell will get freed by the
list factory.
|
| |
|
|
|
|
|
|
|
|
| |
* Update gpl to match project
* Update authors to match about page (otherwise it says "unknown author")
* Update website so it doesn't show a blank site
* Add logo
* Add dependencies
|
|
|
|
|
|
| |
We are generating the docs, so lets make them accessible online.
See: https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/941
|
| |
|
|
|
|
|
|
| |
As part of 42c195897c9e7cf9c80b01446466b4f535a354b2 uncrustify was being
built from source to address a bug that is now fixed in the current release
0.75.
|
| |
|
|
|
|
|
|
|
| |
We have a docs options, but we are generating the docs regardless
of if it is set. This was a regression in d47403bcede0f331c04c7fb28cec2583fed16724.
`gi_docgen.found()` is redundant because when 'docs' is set to true
gi_docgen is a requirement.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
GtkTreeExpander includes a built-in "expand on drag hover" feature.
But our own "open on drag hover" feature competes (and often wins)
over it, making it hard to reliably expand rows on hover without
opening the folder.
So, separate the content and the expander. Trigger "expand on drag
hover" only if over the expander, and "open on drag hover" only if
over the rest.
|
|
|
|
|
|
| |
No functional change in this commit, but this is going to make it
possible for each view to pick the areas which trigger the hover
timeout, to be done in the next commit.
|