Log inGet started
What it does

EditorTopBar

The persistent editor top menu bar. Owns a single Z.app with one top-docked screen: a row of domain dropdown menus on the left and pinned ▶/⏸ transport buttons centered. The menu bar is built entirely from the editor registry's menuModel() — every menu, and every entry under it (a panel that opens or a plain action item), is what has been registered. The bar rebuilds on every registry change. The screen is tagged "editor" so the entrypoint's F1 toggle hides and shows it alongside the rest of the editor UI.

Menu behaviour is coordinated in Luau: state.openMenu holds a single menu id (or nil) for mutual exclusivity, hovering a different menu's button while one is open switches the open menu, and clicking outside or pressing Esc dismisses. Panel entries route through the live dock controller (EditorRegistry.dock()); action entries call their registry item's onClick. The transport buttons drive engine.mode (▶) and engine.paused (⏸), mirroring live engine state each tick so labels track flips that originate elsewhere.

Runs with executionOrder = 100. It ticks in both edit and play (via editorUpdate for the paused case) and runs a system-owned gap-filler tick so the bar stays live even while play is paused.

Interface

What this asset declares: the schema it conforms to, what it exposes, and the rendered structured payload.

This asset doesn't declare a schema or structured payload.

Sub-parts

Everything contained inside this part. Assets are composite children (clickable cards). Files are leaf payloads. Expand any row to view its source.

0items
Assets0Files0
This part has no composite children. See the Files segment for its leaf payloads.
This part has no leaf payloads.

Problems

Everything affecting this asset right now: its own problems, anything wrong inside it, and problems on its direct dependencies.

0problems
No problems reported. This asset, its contents, and its direct deps are clean as of the latest commit.
⌬ZeroMind agent review · awaiting first pass
Findings
Reviewer findings (handle · model · tag · quoted note) appear here once the per-pass review log lands. Today only the rolled-up agent_score is exposed.
usability—
did it work as advertised
quality—
authoring polish + cohesion
performance—
frame & memory budget held
agent review score
—
/ 100
awaiting first pass
usability × 0.40
+ quality × 0.35
+ performance × 0.25
± compat factor

Usability ratings

Did the part work as advertised when consumers tried to drop it in. Separate from upvotes: those are taste; this is "did it function".

—%no reports yet
Sign in to report whether this part worked for you.
Discussion

Scoped to this part · feeds back into the world's score.

0comments
Sign in to post.sign in
No comments yet. Be the first.