From 5ff34782cb9bbd233c5b299a4857afb5f1956b80 Mon Sep 17 00:00:00 2001 From: "Ayberk A." <105879357+AyberkA0@users.noreply.github.com> Date: Thu, 15 Oct 2026 02:21:25 +0300 Subject: [PATCH] color.loadProfile: say that a loaded profile lasts for the run (#1955) The profile is registered in the process's colour registry only, so the next `vectorcraft-cli run` (or the next launch of the app) doesn't know it and edit.colorSettings falls back to the built-in profile. The command's description now says so, and that the profile has to be loaded again in each run that names it. Keeping profiles across runs would need a place in the preferences to remember them, which is left for the maintainers. --- crates/engine/src/cmd/colormgmt.rs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/crates/engine/src/cmd/colormgmt.rs b/crates/engine/src/cmd/colormgmt.rs index bb962dd3a..f034d6164 100644 --- a/crates/engine/src/cmd/colormgmt.rs +++ b/crates/engine/src/cmd/colormgmt.rs @@ -39,7 +39,7 @@ pub fn specs() -> Vec { "Load Color Profile…", [], None, - "{path: .icc/.icm file} register an ICC profile (native only) → {name, kind}", + "{path: .icc/.icm file} register an ICC profile until the app quits or the `run` ends (native only; it isn't remembered, so load it again in each run that names it) → {name, kind}", always, load_profile ),