[Bug]: Screenshot path handling ignores in-memory config #6

New Issue

2026-04-17T11:31:09Z

tgohle commented

2026-04-17 11:31:09 +00:00

Problem

Screenshot saving re-reads the config file from disk instead of using the current in-memory config state.

Current code

outdir = load_config(CONFIG_FILE)["SCREENSHOT_DIR"]

Why this is a bug

If the screenshot directory is changed in the Config tab but not yet reloaded from disk, screenshot saving can still use the old path.

That means the live application state and the actual save destination can drift apart.

Fix approach

Use the active in-memory config object instead:

outdir = self.cfg["SCREENSHOT_DIR"]

This keeps screenshot saving aligned with the current runtime configuration.

Status

Local fix already implemented in the current v0.2 working copy.
Still needs commit, push, and hardware verification before closing.

### Problem Screenshot saving re-reads the config file from disk instead of using the current in-memory config state. ### Current code ```python outdir = load_config(CONFIG_FILE)["SCREENSHOT_DIR"] ``` ### Why this is a bug If the screenshot directory is changed in the Config tab but not yet reloaded from disk, screenshot saving can still use the old path. That means the live application state and the actual save destination can drift apart. ### Fix approach Use the active in-memory config object instead: ```python outdir = self.cfg["SCREENSHOT_DIR"] ``` This keeps screenshot saving aligned with the current runtime configuration. ### Status Local fix already implemented in the current v0.2 working copy. Still needs commit, push, and hardware verification before closing.

tgohle added the area/screenshot

labels 2026-04-17 11:39:52 +00:00

tgohle added this to the v0.2.0 - first bugfix round finished milestone 2026-04-17 12:08:10 +00:00