| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Vim and emacs modelines are used to specify some of the code style in the code.
However, this is misleading and poorly supported since nautilus had a mix of
code style for some time.
Also, the mode lines doesn't specify the whole code style, so we will need to
use a different tool as well to specify the whole code style.
For that, we can just use a different tool for everything.
So remove the mode lines, and in a short future we will reestyle the nautilus
code to have a single code style, and use a tool like editorconfig to specify
the whole code style.
|
|
|
|
| |
It was incorrectly using guint16.
|
|
|
|
|
|
|
|
| |
If we don't request the slider preferred size in allocation, gtk+
triggers a warning.
The code of the path bar shouldn't do what is doing, and now gtk+ warns
about it. In order to fix it, request the preferred size in size_allocate.
|
|
|
|
| |
So they behave like the file chooser ones.
|
| |
|
| |
|
|
|
|
| |
Just symbolic icons, not GtkArrows.
|
|
|
|
|
|
|
|
|
| |
The style cannot be done in a way that makes the path bar with a
permanent visual glitch.
Follow what the file chooser does and always show the sliders to prevent
that, although we are reclutant to any solution, none of them are good.
Let's make the new path bar for 3.22.
|
|
|
|
| |
Request from Lapo.
|
|
|
|
|
|
|
| |
The function is deprecated. Replace it with the parent function
gtk_widget_set_focus_on_click.
https://bugzilla.gnome.org/show_bug.cgi?id=762245
|
|
|
|
|
|
|
|
|
|
|
|
| |
In Nautilus, a size allocation of the pathbar could cause style context
invalidation for its children. Previously the invalidation had to be done
manually. Since it is now done automatically, checking if it is needed and
explicitly doing it are no longer necessary.
Remove function responsible for invalidating style contexts. Remove the logic
for checking if invalidation is needed.
https://bugzilla.gnome.org/show_bug.cgi?id=762246
|
|
|
|
|
|
|
| |
We unref in unschedule, so not need to do it here, which
causes that we unref twice a file and therefore crashes
randomly after some time if the user uses the rigth click
menu of the pathbar
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=757978
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
GtkFileChooser received a Other Locations view that lists
persistent devices, as well as networks and the root location
for the computer's hard drive.
Since Nautilus is a file management tool too, it should keep
consistency between Gtk+ file chooser, something that doesn't
happen since it doesn't display Other Locations.
To fix that, add NautilusPlacesView, a NautilusView implementation
that displays the GtkPlacesView widget. In order to implement that,
update window-slot to correctly display the places-view whenever
Other Locations is clicked.
https://bugzilla.gnome.org/show_bug.cgi?id=753871
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
NautilusView is an abstract class that manages
various context menus, depending on the view's
location, the clicked point and the implementation
details.
While this in theory provides a good isolation
from other classes, in practice NautilusView
manages the pathbar context menu, which is not
necessary, as it doesn't depend on the current
view anymore after the GAction rework.
Fix that by making NautilusPathBar manage the
context menu by itself instead of the view. To
cleanly implement that, add a new signal that
matches GtkPlacesSidebar::open-location signature,
and adapt NautilusWindow to reuse the existing
methods to handle pathbar's new signal.
https://bugzilla.gnome.org/show_bug.cgi?id=753158
|
|
|
|
|
| |
Not very pretty, but this is the best we can do right now with public
API...
|
|
|
|
|
| |
Use the same style class that GTK+ adds to its pathbar now, so
the two can share the theming.
|
|
|
|
|
|
|
| |
Instead, we can use the natural size request which is equivalent to the non-ellipsized size.
See: https://developer.gnome.org/gtk3/stable/GtkLabel.html#label-text-layout
https://bugzilla.gnome.org/show_bug.cgi?id=697198
|
|
|
|
|
|
|
|
| |
GtkWindow relies on button press, release and motion notify
events being propagated. Therefore, we need to select for
motion notify events to make window dragging work.
https://bugzilla.gnome.org/show_bug.cgi?id=722542
|
|
|
|
|
|
|
| |
Otherwise, we are at the mercy of the container giving us
more space than we request, which does not always work.
https://bugzilla.gnome.org/show_bug.cgi?id=722542
|
| |
|
|
|
|
|
|
|
|
| |
And make it so the return value is actually given in the callback,
instead of depending on the window and the pathbar agree on what
happened.
https://bugzilla.gnome.org/show_bug.cgi?id=706605
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=706605
|
|
|
|
| |
Signed-off-by: Federico Mena Quintero <federico@gnome.org>
|
|
|
|
|
| |
This will give it more horizontal spacing, like we do for text buttons
in main toolbars.
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=692234
|
|
|
|
|
|
| |
We might be refreshing while the mount disappears; in that case, the
pathbar will try to get a symbolic icon from a NULL mount, hitting an
assertion.
|
|
|
|
| |
We were still using non-symbolic icons for mount roots.
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=683769
|
|
|
|
|
|
| |
Instead of having the code in nautilus-window-manage-views clear the
pathbar, since it receives the same signal, handle it internally. This
should make code more robust.
|
|
|
|
|
|
| |
Go to home instead.
https://bugzilla.gnome.org/show_bug.cgi?id=666985
|
|
|
|
|
|
|
| |
This will allow us to retain canvas view for the desktop directory
but implement a new icon view for other folders.
https://bugzilla.gnome.org/show_bug.cgi?id=681370
|
|
|
|
| |
We were missing to add the up slider width in the LTR case.
|
|
|
|
|
|
|
| |
We want the down slider button to be linked visually to the rest of the
pathbar.
https://bugzilla.gnome.org/show_bug.cgi?id=680916
|
|
|
|
|
| |
We use a linked style right now, so keeping this around just makes the
code harder to read.
|
|
|
|
|
|
| |
We never want these buttons to have more than a single line of text.
https://bugzilla.gnome.org/show_bug.cgi?id=680289
|
|
|
|
|
| |
Since we don't show any icon for the trash in the pathbar, there's no
need to listen to the changed signal on the trash monitor here.
|
|
|
|
| |
This allow it to work with symbolic icons
|
| |
|
|
|
|
|
| |
It's convenient to just call this in a loop on the button data, so just
return if there's no label to set the size request for.
|
|
|
|
| |
Implementation taken from GtkPathBar
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=676531
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Themes can nowadays set padding on GtkLabel widgets (e.g. Ambiance and
Radiance do this for labels in primary toolbar buttons). This breaks our
hack to force a size request for the pathbar labels, since we measure
the PangoLayout directly instead of measuring the GtkLabel it's part of
(which includes the border/padding values from the theme).
Fix this by measuring the size requisition of GtkLabel directly; for
this to work effectively, we need to pack an (invisible) additional
label in the button GtkBox, always set the text to both labels and
update the requisition of the non-bold one to
MIN(MAX_POSSIBLE_WIDTH, MAX (width, bold_width)) every time a
size-request cycle is called.
https://bugzilla.gnome.org/show_bug.cgi?id=678341
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Set a maximum allowed width of 250px for pathbar button requisitions,
and ellipsize after that. This fixes buttons disappearing completely
from the pathbar in case there was not enough space to show the complete
folder name,
I am not sure I completely like this approach in all the situations,
since there might be some value in showing more of a very long folder
name if there's space available on screen, but unfortunately, it's not
really possible without restructuring completely the way NautilusPathBar
allocates children.
Adapted for master, and slightly modified from an initial patch by
Ted M Lin <tedmlin@gmail.com>
https://bugzilla.gnome.org/show_bug.cgi?id=313854
|
| |
|
|
|
|
| |
New cycle, new set of warnings triggered by glibc/GCC.
|
|
|
|
|
| |
The path-set signal has no listeners connected anymore, so it can be
safely removed.
|
|
|
|
| |
This will be useful to remove some hairy code from NautilusWindowPane
|
|
|
|
|
|
|
|
|
|
|
| |
We currently allow going up from Home towards the filesystem root with a
little back arrow; in the code this is implemented by keeping track of an
additional fake root.
Since we want to change the pathbar not to show the back arrow anymore
in such cases, remove this code (and refactor other pieces of code
around it).
https://bugzilla.gnome.org/show_bug.cgi?id=619616
|
| |
|