Documentation

UI Basics

OsprioView uses a single shell with multiple workspace tabs. Understanding the shell matters because close behavior, device ownership, and diagnostics all live there rather than inside individual pages.

Top shell layout ​

  • The top tab strip holds workspace tabs such as Capture, Emulator, Help, and App Switcher.
  • Tabs are long-lived sessions, not just page links.
  • The active tab can change without tearing down the others.
  • Help tabs can stay open while hardware tabs continue to exist beside them.

Tab lifecycle ​

Each tab has mode-specific close behavior.

  • Capture tabs can block close while capture is running or unsaved data exists.
  • Emulator tabs can block close while emulation is running.
  • A Capture tab reviewing a saved .ovb is read-only and usually closes without side effects.
  • Returning to the workspace picker is different from closing the tab: the shell resets the session back to the wizard state and performs the required cleanup first.

If hardware disappears during a session, the shell keeps the tab and marks the workspace orphaned instead of dropping the user back to a blank state.

Global controls ​

The header-level controls are shared by every workspace:

  • documentation access
  • diagnostics drawer
  • theme switch

These controls apply to the whole shell, not only the active tab.

Theme controls ​

Use the theme switcher in the header to move between light and dark themes. The selected theme applies across all open tabs.

Diagnostics ​

Diagnostics is the shared runtime console for the whole application.

You can use it to:

  • inspect runtime and device-operation logs
  • turn debug logging on or off
  • copy logs together with environment details
  • clear the console before reproducing an issue

The shell is the main subscriber for structured device-operation failures, so diagnostics is where cross-workspace USB and session problems show up.

Practical navigation pattern ​

For most debugging sessions, the useful pattern is:

  1. Keep one operational tab open for capture or emulator work.
  2. Open help tabs when you need reference material.
  3. Open saved .ovb files in a separate Capture tab without disturbing the live session.
  4. Use diagnostics as the shared place to verify what happened across those tabs.