Wayland allows multiple pointers to be active at the same time, e.g. when
a Wacom tablet and mouse are both connected to a system. This means that
it is possible to recieve a "rubberband start" event from a second tool
while a rubberband is already active. At the moment, this results in stray
selection rectangles since the canvas does not properly perform cleanup.
To prevent these graphical glitches from occuring, we can simply cancel
any existing rubberband operation if a second one attempts to start. The
only additional minor complication is ensuring that the new rubberband
is not stopped when the first tool sends a button-up event.
https://bugzilla.gnome.org/show_bug.cgi?id=783797
Nautilus assumes that the pointer returned by gdk_seat_get_pointer will
return the same GdkDevice which started a rubberband action. This is
not necessarily the case, however. Under Wayland, for example, tablet
tools have pointers (and GdkDevice's) which are entirely separate from
the seat's primary mouse-driven pointer. Attempting to use a pen to
perform rubberband selection will result in the rectangle being drawn
with the incorrect coordinates.
This patch has the code store the GdkDevice which generated the event
and provides it in place of the call to gdk_seat_get_pointer.
https://bugzilla.gnome.org/show_bug.cgi?id=783797
The issue is that when navigating into the Desktop directory, the slot
is replaced with a desktop window slot.
This happens because when checking if the current location is handled by
the current slot, the check was made for the actual Desktop directory
instead for the virtual Desktop.
To fix this, instead of checking if the location matches the actual dir,
check if it matches the right uri. A similar issue was in files-view
when creating a new folder, so also change that accordingly.
https://bugzilla.gnome.org/show_bug.cgi?id=771710
Adds option to reopen closed tabs with Ctrl+Shift+T.
In order to do so, keep a list with data needed to restore closed
tabs. So, this list keeps the location bookmark, the view id before
search, which is needed in case the closed tab was a search and
the back/forward history.
https://bugzilla.gnome.org/show_bug.cgi?id=561136
If the search entry is empty and filtering for date or mime type is
added, then the sparql query always returns nothing because of
fts:match '""*'
To get the expected search results don't use fts:match when the
search text is empty.
https://bugzilla.gnome.org/show_bug.cgi?id=782596
Each view handles keyboard activation on its own by listening to
key-press-event, yet there are actions in files-view that could handle
it. This commit makes it so, additionally swapping the accelerators for
opening in new tab and window to make things more consistent throughout
the application (and others, too, e.g. Firefox).
https://bugzilla.gnome.org/show_bug.cgi?id=782600
When the destination name is empty, the "Rename" button goes
insensitive without explaining the user why it happened.
To explain what happened show a descriptive message to inform
the user.
https://bugzilla.gnome.org/show_bug.cgi?id=772435
Currently, Nautilus tries to find the default applications for files
itself, which does not work well in a sandbox. This commit makes
Nautilus blindly launch the default applications, which makes use of the
documents portal indirectly.
https://bugzilla.gnome.org/show_bug.cgi?id=781132
When undo_active/redo_active is FALSE, undo_label/redo_label
was getting overwritten irrespective of whether they were
NULL or not.
Let the label values be freed incase they are updated.
https://bugzilla.gnome.org/show_bug.cgi?id=782083
Nautilus allowed line wrapping for filenames after a . or _
The code made an exception for version numbers, but it
was too rigid and broke things like Ubuntu's 12.04 version
numbering. This relaxes the exception so that the line isn't
wrapped for a . or _ immediately followed by any numbers.
https://launchpad.net/bugs/942539https://bugzilla.gnome.org/show_bug.cgi?id=781875
The issue is that when pressing enter in search while the search entry
has the focus, right after the callback to activate the selection is
called, Nautilus also tries to activate the location corresponding to
the base of the search, as the view is still searching.
This occurs because in the activated signal the search is set as not
visible manually, which will make Nautilus check immediatly if it should
go back to the base of the search location, without waiting for the view
to update.
To fix this, don't set the search as not visible in the activated callback,
as when the search-mode-enabled property changes, if necessarry, the
cancel signal will be emitted which will set the search as not visible,
which will happen only after the view is updated. This is the behavior for
activating the selection in other ways, so activation with focus on the
entry should behave the same.
https://bugzilla.gnome.org/show_bug.cgi?id=764981
The problem is that when we have a file conflict dialog, we can write
a new name for the file in GtkEntry in the expander "Select a new
name for the destination", but after typing in a new file name,
pressing <ENTER> does nothing, but should close this dialog and
confirm the renaming.
To fix this we enable "activates-default" flag for the GtkEntry.
https://bugzilla.gnome.org/show_bug.cgi?id=780449
