Module settings 

The settings screen: what the person can change about QCode, and what the shell has already decided for them.

Everything the framework keeps for every Quvyta application — language, theme, icons and reduced motion — is read straight from the environment the screen draws in, which is the one place that knows what is actually in force. QCode’s own settings, the container engine and the store folder, come from Config, which repairs the file it reads; the repairs are shown here rather than swallowed.

The screen changes nothing outside itself. A choice is applied at once, so it can be seen, and handed to the application as a Request to be stored or carried out. That keeps the settings file, the setup wizard and the container engine in the hands that own them.

Modules

bar

The repair strip: the band that stands over the whole application while the engine is gone.

engine

The engine as the settings screen and the repair strip see it, and the pattern that greys out everything which would reach into a container while there is no engine.

identity

Logins, profile by profile: whether one is stored, refreshing it into the workspaces that use it, and signing out.

Structs

Settings

The settings screen’s state.

Enums

Msg

What can happen on the settings screen.

Request

What the settings screen asks the application to do, because it reaches past the screen.

ServiceRow

What the settings screen shows about the background service.

Functions

entry

The control that takes the keyboard when the screen opens: the list of settings, so the arrow keys walk it from the first key the person presses.

hints

The keys of the settings screen that are not in the keymap, for the key list.

motion_note

The line under the reduce-motion row while the shell decides it.

update

Applies a settings message, answering with the command to run and what the application has to do about it.

view

Draws the settings screen.