| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
Unless there is a writer, this may block forever.
And if there is one, we're somewhat likely to break something.
|
| |
|
|
|
| |
The sanitizer would scream, and LibRaw would rather confusingly
return I/O errors.
|
| |
|
|
|
| |
LibRaw started returning the largest possible thumbnail,
which in the case of NEFs may be a nearly full-scale image.
|
| |
|
|
| |
Don't claim an alpha channel when we don't use it.
|
| |
|
|
| |
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.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
In particular, this handles screenshots from Rigol oscilloscopes,
which reuse the same name series with the same file modification time.
|
| |
|
|
| |
Upon closer thought, I don't know how to implement the idea reasonably.
|
| |
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
| |
Fixes Meson warnings.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
The manual skipping of the initial "v" from tag names is unfortunate,
but still a bit better than further cluttering up the build system.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
wperl is necessary to get rid of the console window,
which is merely one of several issues with the PAR Packer-based
ExifTool bundle used in the last commit.
The Perl installation could be heavily trimmed down,
but it seems to require a very manual process.
|
| |
|
|
|
|
|
| |
- 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.
|
| |
|
|
|
|
|
| |
Scripts have been ported from sdtui, and adjusted for Meson.
The port is broken through and through on WINE,
but sort-of works natively.
|
| |
|
|
| |
Parasitic gesture code previously discarded from fiv gets to live on.
|
| |
|
|
| |
But let's keep it hidden from application lists for now.
|
| | |
|
| |
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
| |
It's mildly less awkward to use, and fixes one complexity issue.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
