Where Does CubicSDR Store Config?
CubicSDR names config and bookmark files in source with OS expansions varying. Flags select named configs per launch.
Last updated
CubicSDR verifies filenames while leaving roots to toolkits. Config and bookmark XML names come from source with flags selecting variants. OS expansions follow standard-paths rules per wx build.
Bookmark managers add backup and last-loaded twins beside live files. Named configs fork through CLI options. Quote names confidently with roots qualified per install.
Where CubicSDR stores this, by platform
~/.config/CubicSDR/config.xml
Config and bookmark XML names from source with flag-selected variants. OS expansions follow toolkit rules varying by build. Confirm live roots locally before archiving.
Frequently asked questions
How do I back up CubicSDR?
Copy the config and bookmark XML files from the user-data expansion matching your OS and wx build. Named configs fork through launch flags. Expansions vary by toolkit version, so confirm locally.
Where are CubicSDR bookmarks?
They ship beside config with backup and last-loaded twins tracking state. Managers save through file menus while loading tolerates failures with renamed copies. Quote filenames confidently and roots carefully.
How do CubicSDR named configs work?
It selects named configs per launch with standard-paths expansion behind. Toolkit docs govern the mapping rather than app pages. Confirm the live root before scripting.
Notice an outdated path? Let us know.