| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Nautilus property extensions to add property pages to the property
dialog was providing a GtkWidget to be modified by extensions.
This makes the extension need to target a specific gtk version, which
with the new gtk versioning might be hard to provide, and it's quite a
bad practice since it requires everyone to be on top of any gtk update.
This is currently holding the work for porting Nautilus to gtk4, since
the Totem extension depends on us having the same gtk+ version, which is
unlikely.
This work makes the extension for providing property extensions not
depend on gtk by providing a plain struct to be filled with data that
later on Nautilus will layout on the UI.
See https://gitlab.gnome.org/GNOME/nautilus/issues/276
|
| |
|
|
| |
(cherry picked from commit 0fdf0d2f8c3d2a580df00697aa72c23c5eac09b1)
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
NautilusSelectionCanvasItem lost a few properties that control the way
the selection rectangle is drawn, namely the color and
stippling-enabling ones, which results in different rendering of the
file outlines when dragging multiple of them. At the moment, the
outlines are styled according to GTK_STYLE_CLASS_RUBBERBAND, which gives
them solid blue-ish borders and a light blue background.
This commit removes the code that sets those properties.
|
| |
|
|
|
| |
Since style properties are a thing of the past and we never enable label
prelighting, this one can be safely put away.
|
| |
|
|
|
| |
Since claiming the event sequence in the button press handler makes the
::motion-notify-event not fire, there is not much choice.
|
| |
|
|
|
|
|
|
|
| |
This takes care of a couple of things:
- not claiming the sequence at the end of the button press handler
breaks ctrl-clicking;
- chaining up to button_press_event() in some cases is superfluous;
- chaining up to button_press_event() instead of propagating the
event down breaks expanders.
|
| |
|
|
|
|
|
| |
Until 3.22.31 or 3.24.0 is released with
https://gitlab.gnome.org/GNOME/gtk/commit/4d2b39d98c3f392782e0ae205dfb50cbc1052b3d,
this will act as a workaround for ::released being emitted after ::cancel due
to a grab.
|
| |
|
|
|
|
|
| |
Even though more convoluted than the previous solution, this one
should last longer. Canvas item icons are now colorized by first drawing
the background to a Cairo surface and then multiplying the color values
of the original icon pixbuf and the ones from the newly created one.
|
| | |
|
| |
|
| |
To cross_environment, since now we have some Flatpak too.
|
| | |
|
| |
|
|
| |
So we test the ecosystem regularly.
|
| |
|
|
| |
See previous commit for more info.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
So far we have been building master of all of our dependencies, also
master of the Sdk. This is good for testing the next version of the
ecosystem, but has many downsides that we now can avoid with Flatpak.
For instance, we want to be buildable at any point in the history,
specially when doing bisects. Also, we need to be a bit stable so that
when designers, users or others build the latest Nautilus they are able
to work with it regardless of its dependencies on other projects.
Even more, now with CI we can test the master of the ecosystem regularly
while not affecting our regular development and operations by depending
on that.
So let's separate in two different manifests the development version
with stable dependencies, intended for our regular operations, and a
development version with all the ecosystem on master, to test the
ecosystem regularly on the CI or on-demand locally.
|
| |
|
|
| |
The expression will not be evaluated if the macros are disabled.
|
| |
|
|
| |
::event-after is obsolete and ::key-press-event is getting there, too.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
::window-state-event is gone.
|
| | |
|
| |
|
|
| |
After removing the desktop window, this type is no longer derived.
|
| |
|
|
|
| |
gdk/gdkprivate.h is no longer a thing in GTK+ 4 and doesn’t seem to be
at all required.
|
| |
|
|
|
| |
This commit also drops properties that no longer apply, including border
width - it’s controlled by the theme.
|
| |
|
|
| |
Easiest fix so far.
|
| |
|
|
| |
And replace it with a handler for ::event.
|
| | |
|
| |
|
|
|
| |
Docs say that a response signal is emitted automagically when such an
event is received.
|
| |
|
|
|
|
|
| |
According to GTK+ docs, this should be the same for all windows of an
application, and GTK+ defaults to doing that itself. However, there is a
slight issue in that the properties window sets a custom window icon
that isn’t reset instantaneously after closing the dialog.
|
| | |
|
| |
|
|
| |
It’s not derived anywhere, and thus it shouldn’t be derivable.
|
| |
|
|
|
| |
With the query editor being inside the header bar now, switching focus
to the content view no longer works.
|
| |
|
|
|
| |
NautilusQueryEditor is only mentioned in passing, this will do just as
fine.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Since we’re handling duplicate branches, this makes sense.
|
| | |
|
| |
|
| |
It makes a bit more sense
|
| |
|
|
| |
It defaults to lib64 and that might be an issue.
|
| |
|
|
| |
The install log might be useful.
|
| |
|
|
|
|
|
|
|
|
|
| |
So the site is down, and the archive cannot be downloaded...
I uploaded the archive to an issue in GitLab
https://gitlab.gnome.org/GNOME/nautilus/issues/458.
If it works...
It works.
|
| | |
|
| |
|
|
|
| |
I needed for a talk because it's more compacted, and we should switch to
it as soon as Builder gets support for yaml!
|
| | |
|
| |
|
|
|
| |
Additionally, this requires setting adjustments in the underlying flow
box after removing the (now deprecated) event box.
|
