Anki/proto
llama 80cff16250
fix: persist colour picker's custom palette in profile (#4326)
* add SaveCustomColours rpc method

* restore custom colour palette on editor init

* save custom colour palette on colour picker open and input

there doesn't seem to be an event fired when the picker is
cancelled/closed, so it's still possible for work to be lost

* save colours on `change` instead of `input`

`input` is supposed to be fired on every adjustment to the picker
whereas `change` is only fired when the picker is accepted, but qt
seems to treat both as the latter, so this is currently a no-op

* Store colors in the collection

One minor tweak to the logic while I was there: an invalid color no
longer invalidates all the rest.

---------

Co-authored-by: Damien Elmes <gpg@ankiweb.net>
2025-09-17 16:46:53 +10:00
..
anki fix: persist colour picker's custom palette in profile (#4326) 2025-09-17 16:46:53 +10:00
.clang-format move protobuf into separate folder in preparation for multiple files 2021-07-09 21:02:40 +10:00
.top_level refactor protobuf handling for split/import 2021-07-10 19:17:05 +10:00
README.md Move away from Bazel (#2202) 2022-11-27 15:24:20 +10:00

Protobuf files defining the interface the frontend and backend components use to talk to each other, and how Anki stores some of the data inside its SQLite database. These files are used to generate Rust, Python and TypeScript bindings.