Dockable inspection
Dockable Workbench
Keep checkbox-aware multi-log details and copy, source preview, Trace occurrences, and the Filter Builder in one optional dockable Unity workspace.
- Choose a presentation mode
- Use four fixed roles
- Understand selection and focus
- Follow, pin, and revisit subjects
- Know when retained content is cleared
Choose a Tool-Window Presentation
The Workbench is a normal Unity editor window that can be docked, floated, or placed in a Unity tab group. Open Window > Azkar Industries > Azkar Console > Settings > Workflow > Tool Windows and set Tool Window Presentation to Dockable Workbench (Recommended). Separate Utility Windows (Current Behavior) remains the first-release default.
Open or restore the Workbench directly from Window > Azkar Industries > Azkar Workbench. Changing presentation mode affects future Filter Builder, source-preview, and occurrence commands. It does not close, move, or redock windows that are already open.
Four Fixed Roles
The tabs describe what the shared workspace is doing; they are not one tab per log or source file.
| Role | Purpose |
|---|---|
Details | Shows one or many selected logs as chronological, virtualized cards. The primary log is marked. Details, Message, and Stack Trace checkboxes control visible sections. Copy All copies every selected card in chronological order using those same choices, including offscreen cards. At least one section remains on. Stack Trace defaults off, and hidden stacks are not parsed or copied. |
Source | Shows one selected log's source or call chain. Follow Selection updates automatically; turn it off to pin the current subject. Turning Follow back on releases a pinned log, archived bookmark preview, or Filter Builder source peek before loading the current selection. Successfully resolved subjects enter bounded back/forward history, and Open in New Window creates a separate utility. |
Occurrences | Shows repeated occurrences for one Trace API log across every retained log in its group, regardless of current presentation filters. Multiple selections ask for one subject, while ordinary logs explain that only Trace API logs display occurrence information. Follow, pin, history, and separate-window behavior match Source. |
Filters | Hosts the complete Filter Builder with the same filters, highlights, presets, context rules, recovery actions, and source Peek behavior as the utility presentation. The persistent Workbench role has no Done action, and Esc does not close the Workbench. |
Selection and Focus
Dock the Workbench beside or below Azkar Console for a companion split-view workflow. Selecting logs hydrates Workbench content in the background, but it does not open the Workbench, switch its active role, select its Unity dock tab, or take keyboard focus from the console. The role you were already using remains visible.
Explicit commands are navigation. Preview Source, View Occurrences, Open Filter Builder, and Filter Builder source Peek select the matching role. Commands issued from Azkar Console also show and focus the Workbench when Workbench presentation is enabled.
Follow, Pin, and History
Source and Occurrences accept one subject. Keep Follow Selection enabled when the role should track the current single-log selection. Turn it off to pin the current subject while you inspect or select other rows. Re-enabling Source Follow releases detached bookmark or Filter Builder preview content before hydrating the current selection. Back and forward navigate only successfully loaded subjects, and history is bounded so a long editor session does not create unbounded Workbench state.
Open in New Window is available for a valid current subject. It opens the compatible utility presentation without changing the configured default.
Log Lifetime
The Workbench is an inspection surface, not another log archive. Clear, retention eviction, database replacement or unmount, and closing the owning console push full-event-identity invalidation to affected Workbench and bound utility content. Removed Details cards, Source subjects, Occurrence analyses, pins, and matching history entries are cleared instead of presented as stale data.
The Workbench stays open on the same role, Filters remain intact, and personal display preferences remain. A log hidden only by a filter is still retained and is not treated as deleted. A bookmark can open a detached source preview from archived source data after the original row is removed; that preview remains explicitly pinned until Source Follow is enabled. Export the session or bookmark important rows when the information must outlive the retained log set.
Personal Workspace Preferences
Tool-window presentation and the Workbench Details, Message, and Stack Trace choices are stored for the current editor user. Workflow reset and global Settings reset return them to their defaults. They are intentionally excluded from portable profile import/export so a shared profile does not rearrange another user's Unity workspace.
Expectations and Limits
- Details supports one or many selected logs. Source and Occurrences require exactly one selected log.
- Details
Copy Allincludes every retained selected log, not only cards currently on screen, and honors the section checkboxes at the moment you copy. Large selections or enabled stack traces can produce a large clipboard payload. - Occurrence totals include every retained Trace API log in the selected group, including rows hidden by search, severity controls, or filters. Navigating to an occurrence does not automatically change those filters.
- The first Occurrences request in a large retained session can take longer while Azkar Console indexes retained Trace groups. Later appended logs update that index incrementally; clear, retention trimming, database replacement, or unmount requires a later rebuild.
- Large occurrence timelines load visible rows as needed, but retained logs, the occurrence index, and display formatting still use memory and editor time. Bounded in-memory retention is recommended for consistently responsive sessions.
- A rapidly repeating Trace group can appear after a short scheduled refresh rather than redrawing for every individual event.
- Archived bookmark previews resolve the source file currently available in the project. They are not historical copies of the source contents, so moved, missing, or changed files may differ from the code that originally logged the event.
- Enabling Source Follow intentionally releases any pinned log, detached bookmark preview, or Filter Builder Peek.
- Changing Tool Window Presentation affects future commands and does not migrate, close, move, or redock windows already open.