| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Nothing fits in there normally, it's about time to acknowledge that.
|
|
|
|
|
|
|
|
|
|
|
| |
The new menu has a few more entries, and shows accelerators.
Most shortcuts have now moved from on_key_press() to actions,
and Alt-Shift-D has started working on macOS.
This also adds support for the global menu in macOS,
and moves some accelerators/key equivalents to the Command key.
There is no other easy way of accessing that global menu in GTK+.
|
| |
|
| |
|
| |
|
|
|
|
| |
And fix a resource leak.
|
|
|
|
| |
As on Windows.
|
| |
|
|
|
|
|
|
| |
On a sample of JPEGs, it improved loading speed from ~0.26s to ~0.15s.
Unfortunately, it isn't normally installed.
|
| |
|
|
|
|
| |
It's not pretty, but it works.
|
|
|
|
| |
Most important Cairo bugs seem to have been fixed recently.
|
|
|
|
| |
So far, it's rather crude.
|
| |
|
|
|
|
| |
Split out clearly internal options.
|
| |
|
|
|
|
|
|
| |
When starting in A/B, then manually going up to A,
and back down to A/B, going back in history to A was impossible,
because it would actually end up being a /forward/ entry.
|
| |
|
|
|
|
| |
And turn the initial load hack into somewhat clean-looking.
|
| |
|
|
|
|
|
|
| |
This makes the user interface more cohesive, and easier to use.
Both toolbars should ideally be made configurable.
|
| |
|
|
|
|
| |
Thus far merely bound to the [ and ] keys in the browser.
|
|
|
|
|
|
|
|
|
|
|
| |
This makes use of our image processing capabilities in order to
turn arbitrary image files into normalized thumbnails,
upload them to a temporary host, and pass the resulting URI
to a search provider.
In future, fiv should ideally run the upload itself,
so that its status and any errors are obvious to the user,
as well as to get rid of the script's dependency on jq.
|
|
|
|
|
| |
The manual skipping of the initial "v" from tag names is unfortunate,
but still a bit better than further cluttering up the build system.
|
|
|
|
|
|
|
| |
- Fix launching of subprocesses (missing gspawn helpers).
- Discard unused GSettings schemas.
- Make the program find its user guide.
- Bundle a somewhat suboptimal version of ExifTool.
|
| |
|
|
|
|
|
|
|
| |
It doesn't make a lot of sense to be able to toggle invisible widgets,
so just make F9 toggle "the toolbar that can currently be seen".
The more permanent setting can be adjusted in GSettings.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Implement a process-local VFS to enable grouping together arbitrary
URIs passed via program arguments, DnD, or the file open dialog.
This VFS contains FivCollectionFile objects, which act as "simple"
proxies over arbitrary GFiles. Their true URIs may be retrieved
through the "standard::target-uri" attribute, in a similar way to
GVfs's "recent" and "trash" backends.
(The main reason we proxy rather than just hackishly return foreign
GFiles from the VFS is that loading them would switch the current
directory, and break iteration as a result.
We could also keep the collection outside of GVfs, but that would
result in considerable special-casing, and the author wouldn't gain
intimate knowledge of GIO.)
There is no perceived need to keep old collections when opening
new ones, so we simply change and reload the contents when needed.
Similarly, there is no intention to make the VFS writeable.
The process-locality of this and other URI schemes has proven to be
rather annoying when passing files to other applications,
however most of the resulting complexity appears to be essential
rather than accidental.
Note that the GTK+ file chooser widget is retarded, and doesn't
recognize URIs that lack the authority part in the location bar.
|
| |
|
| |
|
|
|
|
| |
This is a more than adequate solution for now.
|
|
|
|
|
| |
While all GVfs files implement the mountable interface,
mounting may not actually achieve anything.
|
| |
|
|
|
|
|
|
| |
So far, the macOS special casing is only partial.
Also, GtkShortcutsWindow confusingly labels Command as Meta.
|
|
|
|
| |
Before, it was only possible to achieve the same result using keyboard.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Windows and Linux applications are more likely to not bother,
and their desktop environments don't place windows right in the corner,
which is what happens with GTK+/macOS.
|
|
|
|
| |
LF was converted to CR LF, systematically corrupting bitmap data.
|
|
|
|
|
| |
This could also be resolved through `#define NO_OLDNAMES`,
however the function rather deserved a more precise name.
|
|
|
|
|
| |
There is no conflict with X11/Wayland, because 4/5 are the scroll wheel,
which never gets forwarded to button-press-event.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Making the GtkScrolledWindow's scrollbars draggable again.
|
| |
|
|
|
|
|
|
|
|
|
| |
It would also be possible to handle this through press/motion/release
event handlers, though GtkGestureDrag is more convenient for hacking in
support for dragging to widgets not supporting GtkScrollable (yet).
There may be some undesired interactions lurking, besides the jarring
movements when dragging native GdkWindows (these are a pain).
|