erik/acdream
1
0
Fork 0
Code Issues Pull requests Projects Releases 6 Packages Wiki Activity Actions

feat(quest): QT5/QT6 — the Journal panel, and the button that was already there

Browse source 
The quest log is on screen. Rows come from the live tracker joined to the
authored catalog, the Status column runs QT4's port of FillProgressString, and
the detail pane shows contact, locations, description and the other timer.

Two things measured rather than assumed, each now pinned by an installed-DAT
test rather than left to the commit message:

The tab pairing is read from the authored 0x2E table, not inferred from
x-order — the FA campaign had to correct exactly that mistake, and Contracts
turns out to be the authored DEFAULT tab (0x32 = True), so opening on the
wrong one would have looked like an empty panel.

The open path needed no keybind at all. Toolbar button 0x1000055A authors
0x10000029 = 0x19 and has been sitting in ToolbarController.PanelButtonIds
since the toolbar was ported — it just had no panel behind it, so clicking it
did nothing. Registering slot 25 finished a wiring that was already
three-quarters present.

The list rebuild is revision-gated while the repeat countdown is not: nothing
on the wire changes as a cooldown runs down, so a rebuild-gated timer would
freeze on screen, and a per-frame rebuild would reset the player's scroll under
them. Both directions have a test.

Deliberately inert: the Abandon button (retail's abandon path is a
contract-registry command this campaign did not port — authored and visible,
but wiring a no-op handler would look responsive and lie), and the Journal
notes and Page List tabs, which are their own feature.

Campaign QT slices 5 and 6 of 6 — code-complete, connected gate owed.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Erik 2026-08-21 15:12:05 +02:00
parent fac2dc7248
commit ec6eeb120d
12 changed files with 1109 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

10
tools/LayoutDump/Program.cs
View file

@ -333,10 +333,20 @@ void Print(ElementInfo e, int depth)
UiPropertyKind.Bool => v.BoolValue.ToString(),
UiPropertyKind.Integer => v.IntegerValue.ToString(),
UiPropertyKind.Enum => $"0x{v.UnsignedValue:X}",
UiPropertyKind.DataId => $"did:0x{v.UnsignedValue:X8}",
// An authored StringInfo is a table id + string id, which says
// nothing on its own -- resolve it, because "what does this
// label SAY?" is the whole reason to dump properties.
UiPropertyKind.StringInfo => DescribeString(v.StringInfoValue),
// A tab table (0x2E) is an array of structs pairing a button
// id with its page id. Printing "Array" hides the one thing it
// is for -- and inferring the pairing from x-order instead is
// exactly the mistake Campaign FA had to correct.
UiPropertyKind.Array => "[" + string.Join(
", ", v.ArrayValue.Select(Describe)) + "]",
UiPropertyKind.Struct => "{" + string.Join(
", ", v.StructValue.OrderBy(kv => kv.Key)
.Select(kv => $"0x{kv.Key:X2}={Describe(kv.Value)}")) + "}",
_ => v.Kind.ToString(),
};