keeper 0.4.3

keeper was walking into your photos library and putting its insides on the
wall. that is the one to read. the other three are keeper knowing something
and not saying it.

updating to this is one click from any 0.3.x or 0.4.x: press the version in
the header.

mac	open the .dmg, drag keeper to applications, open it
windows	run the .exe setup, then open keeper from the start menu

0.4.2 against 0.4.3

	0.4.2	0.4.3
a photos library inside the folder you opened	walked into, and its derivatives put on the wall	left closed, and said so
a lightroom preview cache	every frame appeared twice	left closed, and said so
a frame the decoder cannot open	a blank rectangle, no reason given	says unreadable, with the decoder's words
the size of a portrait frame in the quick look	800x1200 drawn as 800x120	drawn whole, or not at all
pressing k	nothing said back	the card says kept
selecting a clip with no poster	the selection ring vanished	it stays
answering never, then wanting an update	"updates are turned off", no way back	pressing the version installs it

the library one

point keeper at your pictures folder and there is usually a photos library
sitting in it. keeper walked in. on a mac that is a permission prompt you did
not ask for, and then several thousand of that library's internal derivatives
on the wall, presented as photographs you took. a lightroom preview cache did
something quieter and worse: it holds a small copy of every frame already on
the wall, so your archive turned up twice, once as itself and once as
thumbnails of itself.

the rule for this already existed. the half of keeper that finds a folder you
dropped knew a .photoslibrary is a document wearing a folder's clothes and
walked past it. the half that scans had never been told. two lists meaning one
thing, and only one of them was right.

one list now, asked by both, and hidden folders go by rule rather than by
name, because a list of names can only ever hold the caches somebody has
already been bitten by. a library that gets left closed is said out loud
rather than dropped in silence, since it is the one skip that hides
photographs rather than clutter:

2 libraries left closed: Lightroom/Previews.lrdata, Photos Library.photoslibrary
  these are apps' own folders. export from the app to cull what is inside them.

measured on an archive with sixteen frames planted inside a photos library, a
.lrdata cache, a synology @eaDir and a hidden folder. before: all sixteen
were indexed. after: none.

the number that was not true

the quick look put four facts on one row with one ellipsis on it, and an
ellipsis eats the tail of its box without caring what the tail means. on a
portrait frame, the narrowest card keeper draws, it ate back through the
folder name and into the resolution, and 800x1200 was drawn as 800x120.

that is not a shortened number. it is a different number, it is a plausible
one, and it sat exactly where you decide whether a frame can be a 2400px
banner. whole facts are given up now instead, in a set order: the folder
first, since the path underneath spells it out anyway, then the running time,
then the tag. the resolution is the last thing standing, because that card is
the only place it appears.

the door that locked from the inside

answering never to the update question turned off the check, which is right.
it also made the install button unreachable forever, which is not: pressing
the version still found a newer keeper and then refused to fetch it, and the
only control that could have said yes was a card that never appears again.

may keeper look on its own, and may it install the one you are pointing at,
were never the same question. the second is answered by pressing the button.
nothing is written either way, so a keeper you told never stays as quiet next
launch as you asked.

this is not hypothetical. a machine here sat on 0.3.1 through five releases
for exactly this reason, and never received a single one of the windows fixes
shipped in between.

if you already answered never, this release cannot reach you, and there is
no way it could. the fix is in the copy you do not have. measured on a real
0.4.2 install carrying that answer: pressing the version finds 0.4.3 and the
install is still refused. download the setup or the dmg from this page once,
by hand, and it never happens again. everyone else, including anyone who has
not been asked yet, updates by pressing the version.

an update also no longer stages in the system temp folder. every step of the
swap is a rename and a rename cannot cross a volume, so anyone whose TEMP
sits on another drive had an updater that could not install anything and
blamed the swap for it.

smaller

the windows doctor ended in pause, so the one command whose entire purpose
is producing text to send to somebody else could only be run by a hand on a
mouse. it now writes its report to %LOCALAPPDATA%\keeper\doctor.txt as well
as the window, and only waits for a key when it was opened by double click.