Desktop app conventions#

Rules every page, menu and window of the desktop app (crates/ohl-app) follows. A change that breaks one needs a reason written next to it.

Menus#

Menus of options stay open while boxes are ticked. Display options, layers, snaps, classes, lines shown — anything where a user may tick several boxes in a row — is made with crate::menu::options_menu: a tick never closes it; only a click outside it, or a command, does. Commands in such a menu close it themselves (ui.close()), as every menu command does. A plain ui.menu_button closes on any click inside and is only for menus of commands.
Commands of the menus are menu::Commands where they can be, so the quick bar can hold them.

What a user shows (layers, surfaces, LiDAR classes, colours, notes on the wires…) is that user's own: kept in ViewPrefs, per project file on their computer, never in the project nor sent to a server.
What changes results (the surface the checks use, rules, cases) belongs to the project and goes through the session (logged, undoable).

Text written in a view next to an object uses the object's colour, with no box around it; notes that would overlap one already written are left out (the nearest first in the 3D view).

Every error, list of errors or report shown in a window goes through crate::menu::error_label (red) or crate::menu::message: short text is shown as it is, long text (over 300 characters or 4 lines) scrolls in a box of fixed height. A window must never grow beyond the screen: its Close / OK / Cancel buttons always stay in reach.
Many files failing for the same reason are reported once, with the number of files and a few of their names, not one line per file.
What cannot work is refused before a job starts (e.g. ECW files without a converter), not reported once per file after.