RotorLab logo RotorLabDocs

Build history and organizing

Every build in your library carries its own timeline. Each save appends a full snapshot of the build's parameters as a new version, and you can add dated log notes in between: what changed, how a flight went, what to try next. Nothing on the timeline is ever overwritten, so you can always get an earlier iteration back.

On top of the timeline, the library offers three organizing tools: a project per build, free-form tags, and a search box that reads all of them.

Versions happen on save#

Saving a build (Build menu, then Build library, then Save current) writes the current parameters as the next version of that name. The optional field under the name box ("What changed?") attaches a short note to that version, so the timeline reads like a changelog.

In the library list, a build shows a version badge (for example v4) once it has more than one version, and its History button shows how many timeline entries it has.

The History & log dialog#

Press History on a library row to open the History & log dialog for that build. It contains, top to bottom:

  • Project and Tags fields for organizing the build (see below).
  • A note box ("Add a log note") with an Add note button.
  • The timeline, newest first.

The timeline mixes two kinds of entry:

  • Versions: numbered dots (v1, v2, ...) with the save time and the "what changed" note if one was given. The newest version is marked current.
  • Log notes: dated text entries with no parameter change.

A build saved before its history existed shows "No history yet. Save the build to start its timeline."

Loading an old version onto the bench#

Press Load this on any older version to put that snapshot on the bench and rerun the analysis. This only changes what you are looking at; it does not change the saved build. Save afterwards if you want to keep it.

Comparing a version with the current state#

Press Compare on an older version and a table expands under it, showing only the key specs that differ between that version and the build's current state: dry mass, payload, motor count, prop diameter and pitch, blade count, motor KV, max thrust, arm length, ESC rating, altitude, and a battery summary (cells and capacity). If none of the key specs differ, it says "No differences in the key specs." Press Compare again to collapse the table.

Restoring a version#

Press Restore on an older version and confirm. The snapshot becomes the build's current parameters, and the timeline gains a fresh version entry noted "Restored from vN". Restore is append-only: the versions in between are all still there, so restoring is always reversible. If the restored build is the one loaded on the bench, the bench updates immediately.

Adding log notes#

Type into the note box and press Add note. The note lands on the timeline with its date. Empty notes are refused. Use notes for anything worth remembering that is not a parameter change: a flight result, a component that ran hot, the reason behind the last version.

Tags and projects#

At the top of the History & log dialog:

  • Project is a single short label, for example "Mapping rig". One project per build, up to 60 characters.
  • Tags is a free-text list, for example 7inch longrange 6s. Separate tags with spaces or commas; they are normalized to lowercase and deduplicated, and a build keeps up to 12.

Both appear on the build's row in the library list: the project with a folder icon, tags as small chips.

Searching and filtering the library#

The My builds tab has a search box ("Search builds, tags, projects...") and a chip row. The chip row shows every project and every tag that exists in your library. Click a chip to filter the list to builds with that project or tag; click it again to clear the filter. The search box matches against build names, tags, projects, and notes, and combines with the active chip.