Calendar / Activity Log

The Calendar workspace tab is a project-level audit log and lightweight task tracker. It records both system events (auto-generated when something changes in the project) and user notes (manually authored, with a status tag).

Opening the Calendar

The Calendar tab appears in the project’s workspace alongside Sections, Alignment, Templates, Volumes, Analytics, etc. Each open project has its own scoped Calendar. Switching projects switches the visible activity log.

What is recorded

System events

Auto-recorded entries are produced for actions that change the project’s structure or state. The categories include:

  • Project lifecycle – new project, open, save, save-as, close

  • Structural edits – adding, editing, or deleting sections, line definitions, template line definitions, templates, station definitions, alignments, section line styles, and volume definitions

  • Imports – LandXML import, measurement import, point cloud attachments, DXF template imports

  • Exports – LandXML export, measurement export, PDF export, mass-table export, analytics report export

  • Conversions – legacy .tcm → .tun conversions

  • Analytics runs – compliance, geometry, statistics, longitudinal, clearance reports

Note

Granularity is per-action, not per-edit. A long template edit session that changes multiple points in one dialog produces a single “template edited” event rather than one per edit.

User notes

Notes are authored manually via Add Note in the detail pane. Each note has:

  • A title (one line) and free-form body

  • A category (chosen from the same set as system events, or “Note” for general entries)

  • A status: Open, Done, or Cancelled

  • A scope: project-wide, alignment, section, template, etc.

User notes are editable; system events are read-only. The status of a user note can be toggled directly from the detail pane without reopening the Edit dialog.

The interface

The tab is split into three regions:

Filter strip (top)

Date range picker, category dropdown, status filter, and scope filter. Filters are AND-combined; clearing a filter widens the result set.

Timeline list (left)

Chronological list of entries that match the filters. Each row is colour-coded by status (system events use a neutral colour; user notes are tinted by their status).

Detail pane (right)

Shows the selected entry’s full body, metadata, and – for user notes – Edit, Delete, and status-toggle buttons.

Persistence

The activity log is stored in the project’s .tun file as XML. Each entry has a stable GUID so cross-references survive saves and reloads. Closing and reopening the project preserves the entire log.

Privacy

The activity log lives only in the .tun file; nothing is sent to a remote server. Sharing a .tun file shares the activity log with it. If you need to scrub history before sharing, delete user notes individually (system events cannot be deleted, but you can save a fresh copy of the project to start a new log).

Tips

  • Use Open notes as a tunnel-scoped TODO list. Toggle them to Done as work is completed – the timeline view shows the original creation date and the close date.

  • Filter by category Import or Export before sharing a .tun to see exactly what data has flowed in or out.

  • The same activity log records analytics runs, so you can answer “when was the last clearance report generated for this project?” directly from the Calendar.