FlameRobin Files

FlameRobin 26.7.2 — Theme & Readability Fixes

Released: 2026-07-07

This patch release closes three open bug reports — all related to colour, theme, and readability — making FlameRobin look great in both light and dark mode out of the box.

---

🎨 Default Light Theme Redesign (fixes [#642] — "Hex-rated Crisis")

The default stylers.xml palette has been completely overhauled. The old scheme relied on harsh, neon-saturated hex codes inherited from an early Notepad++ port — pure 0000FF blue keywords, FF8000 neon-orange numbers, 800080 magenta type-names — producing eye-straining, low-contrast results. Every colour in the new palette meets WCAG AA contrast (≥ 4.5:1) on white.

SQL Lexer

Token	Before	After
Keywords (SELECT, FROM, WHERE …)	0000FF harsh pure-blue, bold	0550AE deep blue-indigo, bold
Numbers	FF8000 🔴 neon orange	0E7C5F calm teal-green
String literals	808080 flat grey (low contrast)	953800 earthy sienna-brown
Secondary keywords / types	800080 saturated magenta	6639BA muted purple-indigo
Operators	000080 navy, bold	393A34 dark charcoal, bold
Comments (--, /* */)	008000 bright green	57606A slate grey

Diff Lexer

Token	Before	After
Deleted lines	Dark-red text only	82071E on FFEBE9 pale-red tint
Added lines	Plain blue text	116329 on DAFBE1 pale-green tint
Position marker	FF8000 neon orange	0E7C5F teal

Global Editor Chrome

Element	Before	After
Default font	Courier New	Consolas (crisper rendering)
Current-line highlight	E8E8FF purple wash	F0F6FF subtle blue
Selection	C0C0C0 flat silver	BDD7F5 soft sky blue
Text cursor (caret)	8000FF neon violet	0550AE deep blue
Edge / indent guides	80FFFF neon cyan	D0D7DE light grey
Brace match	Red text	Green text on mint tint
Fold markers	Hard grey	Harmonious 8C959F / F6F8FA
Whitespace dots	FFB56A neon peach	AFBAC4 muted grey
All Mark Styles (1–5)	Pure neon (00FF00, 0080FF, 8000FF …)	Accessible pastels (sky-blue, amber, yellow, violet, mint)
Find Mark highlight	Pure FF0000 red	FFD966 soft amber

---

🌙 Light Theme Ignored in System Dark Mode (fixes [#633])

When a user explicitly chose the Light theme in Preferences but their OS was set to dark mode, FlameRobin ignored the preference — the SQL editor and other panels rendered in dark colours regardless.

Root cause: Several call sites queried wxSystemSettings::GetAppearance().IsDark() directly instead of honouring the stored preference.

Fix: All three remaining direct appearance checks have been replaced with FRStyleManager::isEffectivelyDark(), which correctly respects the user's stored ThemeLight=1 / ThemeDark=2 / ThemeSystem=0 setting:

• PrintableHtmlWindow.cpp — HTML report background colours
• ExecuteSqlFrame.cpp — statistics pane text colours (×2)
• SchemaVisualizationFrame.cpp — schema diagram JSON payload

---

🌙 SQL Editor / BLOB Editor Unreadable in Dark Mode (fixes [#615])

This release extends the dark-mode fix from v26.7.1 with one additional coverage gap:

BLOB Text Editor (EditBlobDialog) — newly fixed

The BLOB text editor (blob_text wxSTC control inside Edit BLOB dialog) was never connected to stylerManager(), so it always rendered with Scintilla's hard-coded white background regardless of theme.

Changes in EditBlobDialog.cpp:

• Added #include "gui/FRStyleManager.h"
• Called stylerManager().assignGlobal(blob_text) during do_layout() so the initial open honours the active theme
• In blob_textSetReadonly(false): replaced the hard-coded "WHITE" background + StyleResetDefault() (which wiped theme colours back to Scintilla defaults) with a theme-aware restore via stylerManager().getGlobalStyle()->getbgColor() + re-applying assignGlobal()

---

Commits in this release

Commit	Description
97358ac6	Bump version to 26.7.2
b67f8290	fix(#642): redesign default light theme palette in stylers.xml
1012eeaa	fix(#615): apply dark theme to BLOB text editor in EditBlobDialog
e395e32c	fix(#633): use isEffectivelyDark() in SchemaVisualizationFrame

Full diff: https://github.com/mariuz/flamerobin/compare/v26.7.1...v26.7.2

---

Upgrading

Drop-in replacement for v26.7.1. No database or configuration migration required.

If you had previously customised stylers.xml, your file will not be overwritten on upgrade — your custom colours are preserved.