| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The floating bar was a bad choice since it's inception. Not
only it hovers content, it's behavior is inconsistent and the
usability of it is very poor.
After the introduction of the actionbar, most of the data that
we displayed through the floating bar was moved to the actionbar,
making the floating bar obsolete.
This commit follows up and completely removes the floating bar.
|
|
|
|
|
| |
When we change the view, add the view's actionbar
to the bottom of the window slot.
|
|
|
|
|
| |
This will be used in the next patch so we can
access the actionbar of the view.
|
|
|
|
|
|
| |
The new NautilusActionBar class handles everything
needed to be an usable actionbar as envisioned by
the available mockups.
|
|
|
|
|
| |
This action will be consumed by the actionbar, to simplify
the development of the stop button.
|
|
|
|
|
|
|
|
|
|
| |
Currently we don't have any way to track selection
changes, although NautilusView exposes selection. This
is an inconsistency in code, and should be avoided.
Fix that by adding a NautilusView::selection property
and deprecating the NautilusFilesView::selection-changed
signal.
|
|
|
|
|
|
| |
As it's quite common way to be needed to run display
tests, it's now included in the base gnome-nightly
docker image.
|
| |
|
|\
| |
| |
| |
| |
| | |
list-view: Allow right clicking expanders
list-view: Make list view selection consistent
See merge request GNOME/nautilus!131
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Selecting rows using CTRL/SHIFT with left click is different
to right click as GtkTreeView's default code does not support
SHIFT+CTRL selection.
We want consistency between the two behaviours.
We fixed this by replicating the left click behaviour in the
right click case. The GTK dependency is also bumped in order
to use GtkTreePath autocleanup.
|
|/
|
|
|
|
|
|
|
|
|
|
|
| |
Right now, right clicking an expander opens the context menu
without changing the selection.
This resulted in the context menu affecting other items than the
clicked one, which is counterintuitive and should not happen.
We fix this by isolating the case where an expander was clicked
and we change the selection to the clicked row.
Closes https://gitlab.gnone.org/GNOME/nautilus/issues/286
|
|\
| |
| |
| |
| |
| |
| | |
general: Error out if unhandled protocol is entered from CLI or pathbar
Closes #237
See merge request GNOME/nautilus!151
|
| |
| |
| |
| |
| |
| |
| |
| | |
The problem is that upon entering "x-nautilus-search" in cli a crash is observed.
The solution is to explicitly check for "x-nautilus-search" in cli and error out before even opening the uri.
Closes https://gitlab.gnome.org/GNOME/nautilus/issues/237
|
|\ \
| |/
|/|
| |
| | |
file-utilities: Create parents along with config dir
See merge request GNOME/nautilus!159
|
|/
|
|
|
| |
While under normal circumstances one could expect XDG_CONFIG_HOME to
exist, in rare cases (e.g. test environments), it might not.
|
|
|
|
| |
(cherry picked from commit 5a6a923d03054246f642ad44cd6a9b1b74410abc)
|
|
|
|
|
|
|
|
|
|
| |
f42979f0b073d96a9157c05c0bff963820a630b4 changed the ellipsis to a
unicode one, which is one character in length, in turn changing the
expected output.
For cases where the truncation length is zero, the expected output is
changed to NULL, as 536505728e3963cfc6d2fa93ca2b188bfb5a144b added an
assertion.
|
|
|
|
| |
Thanks to Christian for pointing out `flatpak build` use in Builder.
|
|
|
|
| |
(cherry picked from commit e0cfcef44f79c68ad11d768921cea9d65ba70618)
|
|
|
|
| |
(cherry picked from commit 7e17250ef94e04d4610ef5c0bbc316fe677f6c22)
|
|
|
|
| |
(cherry picked from commit abbb6776a9b5886a7d3cdc20aea437e12b4d84c4)
|
|
|
|
| |
(cherry picked from commit 4f88733ed20f2e6d5fa8c1c46ea750fd6dd211cf)
|
|
|
|
| |
(cherry picked from commit 2713ad8261c1f76fa85ca85020c7aa51b69830ed)
|
|\
| |
| |
| |
| | |
list-view: Fix "row expanded" typo
See merge request GNOME/nautilus!158
|
| |
| |
| |
| |
| | |
The text was supposed to be "row expanded", but was missing
an 'n' and 'uri' should be capitalized.
|
| |
| |
| |
| | |
(cherry picked from commit fce335f21680a6eb98c41c21ab51835946ce1cf6)
|
| | |
|
|/
|
| |
We want that as part of the Flatpak build.
|
| |
|
|\
| |
| |
| |
| | |
Add issue templates
See merge request GNOME/nautilus!135
|
| |
| |
| |
| | |
Until we have a repo with the stable one.
|
| |
| |
| |
| |
| | |
This commit adds issue templates for use in GitLab to hopefully improve
the quality of bug reports and feature requests that come in.
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Replace include guards with pragma once functionality
Closes #294
See merge request GNOME/nautilus!141
|
| | |
| | |
| | |
| | |
| | | |
A couple of arguments were misaligned, so we placed
them properly.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The traditional include guards are not as easy to handle
and require extra thought into the names.
Pragma once is an easier, more contributor friendly approach.
Closes https://gitlab.gnome.org/GNOME/nautilus/issues/294
general: Remove include guards in favor of pragma once
The traditional include guards are not as easy to handle
and require extra thought into the names.
Pragma once is an easier, more contributor friendly approach.
Closes https://gitlab.gnome.org/GNOME/nautilus/issues/294
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
(cherry picked from commit c5bc9f92d0bedc5b8c485fe69c43e88e7e6604ea)
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
Don’t search without a set-up view
See merge request GNOME/nautilus!153
|
| | | |
| | | |
| | | |
| | | |
| | | | |
While not strictly necessary, it might prevent the cornerest of corner
cases regarding actions in window slots.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Since the view can be null at the time the user is pressing keys, doing
anything with it may lead to a crash.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Since the location of the query editor is nullable, we cannot rely on it
having a value. An example of such situation is triggering a search
while the window slot has no view set and, therefore, no location, which
can happen when opening remote locations.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
So it’s a bit clearer how the return values or parameters should be
managed.
|