Acting on your choices
The actions queue
Why nothing happens until you commit, what the review shows you, and how to undo a commit.
Cullant separates deciding from doing. You decide all afternoon; the doing happens once, at the end, after you have read the list.
What goes in the queue
Three kinds of action:
- deletes: from a reject flag, or from Del
- moves: from V
- copies: from V
Everything else you do (stars, labels, tags, rotation) is state, not an action. It lives in the database and only reaches your files through a sidecar, if you asked for sidecars.
Review
Press Ctrl + Enter.
The dialog groups the queue by phase, which is deletes, then moves, then copies, then the sidecar writes, and shows every file in each. Read it before you run it. Anything you are unsure about can be unqueued from here, and unqueueing a delete also clears the reject flag that put it there.
Run it, and Cullant works through the phases with progress for each. Conflicts, such as a destination file that already exists or a file that vanished since the scan, are reported rather than guessed at.
Undo
Cullant keeps a history of commits. You can undo a whole commit, or one entry inside it, after the fact.
Deletes go to the Recycle Bin by default, which is what makes that possible. If you chose a permanent delete, no history can bring the file back. That is the point of the option, and it is why it is not the default.
Auto mode
If the review is friction you do not want, auto mode runs each action the moment you queue it. Rejecting a frame deletes it there and then.
Use it when you are sure. Everything else about the app stays the same.
What is planned
A rules engine: “a rating of five or higher moves the file to /selects”, applied
automatically as you cull, with the results landing in the same reviewable queue. The database
already reserves a place for rule-generated actions so that they can be told apart from the ones
you queued by hand. The interface for writing the rules is not built yet.