Your libraries
Four collections belong to you rather than to any one drawing: your palettes, your media, your themes and your saved layouts. They follow you from project to project with no import step, and they live in folders of small readable files beside your settings.
| Library | Where | One file is |
|---|---|---|
| Palettes | ~/.config/flatty/palettes/ | a .json file |
| Media | ~/.config/flatty/media/ | a .png plus a small .meta.json beside it |
| Themes | ~/.config/flatty/themes/ | a .json file |
| Layouts | ~/.config/flatty/layouts/ | a .json file |
One rule decides what goes where. A preference is a setting you flipped, and it lives in your settings file. An asset is a thing you made or imported, named, and might want to copy, keep or send to somebody. Assets live in a folder, one file each — so you can back one up, mail it, or drop one in by hand.
Dropping a PNG into the media folder from your file manager makes it a brush the next time Flatty starts. That is not a side effect; it is the point of the folder being a folder.
There is a fifth place, and it is none of the above: a cache, in your system’s cache directory, holding what Flatty can rebuild by itself — the list of fonts on your machine, and the gallery’s thumbnails. Delete it whenever you like.
The Media pane
Everything you have imported — brush textures and reference pictures — in one gallery. Switch any pane to Media, or press Manage… in the texture brush’s settings.
Click a thumbnail and the column on the right fills in with that picture and everything you can do to it. The + tile at the end of the grid brings a new one in.
| In the right-hand column | What it does |
|---|---|
| Name | rename it in place. Renaming never moves the file, so anything pointing at it keeps working |
| Kind | Brush texture or Reference — a filter, not a folder |
| Paint with this | put a texture in the texture brush’s hand and pick the brush up |
| Place on the canvas | crop and size it, then drag it into place as a floating paste |
| Edit… | crop, straighten and resize. The result is filed as a new picture and this one is left alone |
| Pin / Unpin | say this project uses it, before you have painted with it |
| Tag… / Untag… | file it, so the filter can find it again |
| Delete | remove it from the library and from disk, on a second click |
The tick boxes on the thumbnails are for doing something to several at once. With some ticked, the right-hand column becomes Picked out and its buttons act on all of them. Clear unticks everything.
Ticks survive a change of filter. That is what makes the usual pass work: narrow to Untagged, tick the lot, tag them, then narrow to something else. A ticked row the filter has since hidden is left alone, though — the buttons never reach something you can no longer see.
Tags
A tag is any word you like. Add a few to something and the filter bar can find it again in a library of two hundred.
Case does not matter, and neither does how you typed it the first time.
Forest,forestandFORESTare one tag. The chip shows the spelling you used first, and everything else compares them as the same word — so a library cannot quietly collect three near-identical tags that split your work between them.
Right-click a tag chip to rename it everywhere or remove it from everything.
That is the only cure for a typo: forrest has to become forest on every
picture at once, because the misspelling is the only thing tying them together.
Renaming one onto a tag that already exists merges the two.
Typing in the tag box offers the words you have used before. Not being able to remember last week’s spelling is the main reason tag lists rot.
Finding things
The filter bar sits above both the media gallery and the palette library’s Manage tab, and it is the same set of controls in both.
| Control | Narrows by |
|---|---|
| the scope | which part of the library — see below |
| the kind | media only: brush texture or reference |
| the sort | by name, newest first, or recently used |
| the search box | part of a name |
| the tag chips | click one to require it |
Every tag you add shows you less. Requiring forest and stone gives you
the things carrying both, not the things carrying either. That is what makes a
filter useful on a big library; the search box is there for the times you want
the looser thing.
The five scopes
| Scope | Shows |
|---|---|
| Everything | the whole library |
| This project | what this project pins, and what it has been seen using |
| Untagged | the inbox — everything imported and not yet filed |
| Unused | in no project and never painted with — what is safe to delete |
| Missing | referenced by this project and no longer in the library |
Untagged is your inbox. Import forty pictures and they all land there; it is where you go to file them.
Unused is the answer to the drawer everything ends up in. It is the one view that tells you what is safe to delete after three years — and it needs both halves to be true, so something a project pins is never listed there even if you have never painted with it.
What this project uses
The This project scope is about the drawing you have open rather than about your library.
Flatty watches what you actually paint with: stroke with a texture and it notes that this project used it. That is the half you get for free, and it is what makes This project worth trusting rather than aspirational.
Pin is the other half — you saying “this project uses these” before you have touched them, which is how a set gets gathered at the start of a job rather than discovered at the end. Pinned pictures are badged as such.
Why it does not tidy itself. Once you have stroked with a texture, its pixels are in your artwork. Nothing can tell later whether you painted over every trace of it, so Flatty never quietly drops something from the list — it would eventually drop one you were relying on. Forgetting is a button you press.
If this project names something you have since deleted, it is listed under Missing rather than silently vanishing, so a reference that has gone is something you find out about here rather than when you go looking for it.
Packing a project up to send
Pack for sharing…, in the Export pane, asks for a new, empty folder and copies your project into it along with every asset it uses:
somewhere/
fluffy cloud/ the project, exports and all
library/
media/ the textures it uses
palettes/ the palettes it uses
Zip that folder and it is a complete handover — the artwork, and everything it was made with.
It has to be an empty folder. Packing into one that already holds something is refused, because you would have no way of telling afterwards which files came from this run and which were an older copy.
Why the libraries are not inside each project to begin with. They could be, and then every project would be self-contained without a button. But forty textures across twenty projects is eight hundred files, and improving one leaves nineteen stale copies of it behind. Keeping one copy and packing on demand costs you one button on the days you are actually sending something, and nothing at all the rest of the time.