We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Wiki dev pages: more prose semicolons -> periods Virtual-Controllers.md and Services-Layer.md had several 'X; Y' constructions where Y was glossing X. Periods read cleaner and match the project style rule. Semicolons retained inside code blocks and inside short table-cell phrases where they act as series separators.
Settings-and-Serialization: prose semicolons -> periods Three 'X; Y' constructions in body prose where Y was glossing X. Periods read cleaner and match the project style rule. Semicolons inside C# property-declaration code blocks left untouched (they're syntactically required there).
HIDMaestro-Deep-Dive: prose semicolons -> periods Five 'X; Y' constructions in the dropped-vJoy-features bullets, plus the back-compat XmlEnum paragraph, were using semicolons as pseudo-periods to gloss the prior clause. Periods read cleaner and match the project style rule.
Wiki: semicolons in prose -> periods/sentences Troubleshooting.md and Dashboard.md had three semicolons being used as pseudo-periods to gloss the prior clause. Memory rule favors periods for the 'X; gloss-Y' AI-tell pattern.
Macros: em-dash pseudo-colon -> colon in variable-letter explanation 'Each one becomes a letter — a for the first' uses the em-dash as a pseudo-colon attaching the example list. Plain colon reads cleaner and matches the style rule (em-dashes only for true parentheticals).
Wiki: em-dash pseudo-colon -> period/colon Home.md (Battery lightbar description) used em-dash to attach the explanation of charge-level colors; replaced with a colon since the em-dash here was a pseudo-colon, not a true parenthetical. Settings.md (Inactivity Timeout description) used em-dash to attach the consequence sentence; replaced with a period since the second clause is a standalone elaboration.
Input-Pipeline: document v3.2 MappingSet evaluator file + Step 3 hook Wiki said 'split across eight files' but the actual codebase has 9 InputManager partial files now. New file InputManager.Step3.MappingSetEval.cs runs ahead of the per-device mapping pass for slots that carry a MappingSet, resolves multi-source rows + combine modes + custom formulas + shift layers, and feeds the synthesized PadSetting into the existing MapInputToGamepad path. Add the file row to the partial-class table and a companion-file callout under the Step 3 header.
Build-and-Publish: PadForge.App tree lists all model/asset dirs Solution-structure tree was missing 3DModels under PadForge.App and the 2DModels listing only mentioned DS4/ and XBOX360/. Now lists all 4 OBJ directories (DS4, DualSense, XBOX360, XBOXONE) and all 5 PNG directories (DS4, DualSense, XBOX360, XBOXONE, XBOXSERIES).
Wiki: replace 'per (slot, device)' tuple notation with plain English memory rule feedback_no_tuple_notation_in_prose.md flags 'per (slot, device)' as AI-jargon math notation. Five wiki pages had it. Replaced with 'per pad per slot' so prose reads like prose, not like a Python dict-key lookup.
Wiki: eradicate remaining 'chip' jargon from formula-editor prose Button-and-Axis-Mappings.md: 'Chip palette' section heading and the 'drag a chip' body sentence were still using the WPF Material Design control name. Renamed to 'Operator palette' / 'Drag an operator'. Macros.md: 'chip-style picker' cross-reference replaced with the plain 'cross-device input picker' + 'operator palette' wording that matches the editor's actual user-facing terminology. Memory rule feedback_no_chip_jargon.md flags 'chip' as opaque to readers; this completes the sweep across the wiki.
Engine-Library: document new CustomInputState battery fields Add BatteryPercent and BatteryCharging field rows and value-convention entries; update Clone() and the zero-state constructor row to reflect that both fields are part of the snapshot. These were added for v3.2's lightbar Battery mode and have been missing from the docs.
Wiki dev pages: fix 3 more stale 2-variant references 2D-Overlay-System.md: 'How All Views Relate' step 5 said EnsureModel maps PlayStation->DS4 and everything else->XBOX360. Now reflects the actual 5-way HMaestroProfileCatalog.ResolveAssetFolders dispatch. XAML-Views.md: Controller Tab Type Icon DataTrigger value was listed as 'Microsoft', actual value is 'Xbox'. Also clarified that the icon resource keys cover the whole family, not just DS4/360. Input-Precision.md: PlayStation slot header was 'DS4 protocol' only; broadened to 'DS4 / DualSense protocol' since DualSense profiles also emit 8-bit sticks and triggers.
Architecture overview: list all 4 3D model files + 5 2D / 3D asset dirs Models3D directory listing was missing ControllerModelXboxOne.cs and ControllerModelDualSense.cs. 2DModels and 3DModels directory listings were missing XBOXONE, XBOXSERIES, and DualSense subdirectories.
Dev wiki: document all 4 3D model classes and all 5 2D layouts 3D-Model-System.md: add detailed sections for ControllerModelXboxOne and ControllerModelDualSense (mesh groups, color palettes, rotation points, material assignment order). Expand OBJ Mesh Files listing to include XBOXONE (46 meshes) and DualSense (48 meshes) directories. Rewrite EnsureModel() docs to reflect the actual 4-way HMaestroProfileCatalog.ResolveAssetFolders branching plus the xbox-series-* ProfileId Share-button gate. 2D-Overlay-System.md: add Layout sections for DualSenseLayout, XboxOneSLayout, and XboxSeriesXLayout. Expand PNG Asset Structure listing to include XBOXONE, XBOXSERIES, and DualSense directories. Rewrite Model Selection docs to reflect the actual 5-way layout dispatch in BuildCanvas().
Input-Precision: math fix — 16-bit (65536) vs 15-bit (32768) is 2x the resolution, not 16x
Drop 'chip-based' / 'chip palette' jargon — 'drag-and-drop formula editor' or 'operator palette' reads cleaner
Home nav: 'Touchpad Overlay' display text instead of raw 'Dashboard#Touchpad-Overlay' URL fragment
wiki pad-mappings.png: refresh with Pit Stop shift-layer tab visible
Wiki: real Impulse Triggers screenshot (was reusing pad-forcefeedback.png as a stand-in)
Drop math-tuple 'Per-(device, slot)' jargon — 'per pad per slot' reads cleaner
Pass 91: HIDMaestro-Deep-Dive — drop first-person voice (we/our → PadForge / imperative)
Pass 73: fix broken gollum-pipe-in-table-cell links (Devices/Dashboard/Virtual-Controllers) — table column pipe collided with link-target pipe, rendering as literal '[[Slot' text on the published wiki. Replaced with regular markdown links.
Pass 65: Settings-and-Serialization Table of Contents lists the new MappingSet section
Pass 64: Engine-Library See Also pointer to Settings-and-Serialization now names the v3.2 MappingSet family of DTOs explicitly
Pass 63: Settings-and-Serialization documents v3.2 MappingSet, MappingRow, MappingSource, ShiftActivator, MappingSetMigrator XML schema (was undocumented; these are the v3.2 mapping engine DTOs)
Pass 59: Driver-Management first-run text matches reality (HMContext.InstallDriver() runs on engine start, no Dashboard 'install card')
Pass 58: Settings.md Driver Management corrected — HIDMaestro card has status only (no Install/Uninstall buttons); auto-installs on engine start
Pass 57: Installation drops 'click Install next to HIDMaestro' instruction (driver auto-installs via HMContext.InstallDriver() when the engine starts; Settings shows status only)
Pass 38: Troubleshooting Quick Reference row for each new v3.2 entry (Shift Layer / Impulse Triggers tab / Custom Expression / Touchpad Overlay)
Pass 35-37: Troubleshooting adds Shift Layer + Impulse Triggers + Custom Expression + Touchpad Overlay entries (v3.2 features were undocumented)