Three things Ben saw on the running application that all read as "this is still
the tool it was forked from".
1. The upstream 50-page manual was sitting in the repository root as MmdPdf.pdf,
so it was the document on screen whenever it was opened or restored from the
last session - a full-page green upstream logo on black. It was never shipped
in the payload, but it was there to be opened, which is the same thing to
whoever is looking at the screen. Removed, and added to .gitignore so it does
not come back with a source drop. With no document, the application opens on
its own empty view.
2. Scan was in the title bar beside minimise, maximise and close. That is window
chrome, not a tool. It is a toolbar button now, next to Print in the file
group, with a caption in every label mode like every other tool. The band
button style it used has no other user and is gone with it.
3. The footer read v1.7.5, which is the upstream project's version. MMD PDF is
2026.8.1. Not 1.0: the pilot machines already carry a build numbered 1.7.5,
and an upgrade has to sort above what it replaces or Intune would read it as
a downgrade. The Intune detection rule moves with it.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Ben, 2026-08-28: four changes, then build it, sign it, and make it deployable
through Intune without alerts.
1. The row of icons is a fifth shorter. Every toolbar label mode comes down
together so the proportions between them are unchanged: 34 -> 27 for a
caption beside the icon, 52/56 -> 42/45 for a caption under it, with the
padding reduced to match. The row measures 48px on screen where it was 60.
2. Scan sits in the main bar. It is a solid white button on the band, to the
left of the window buttons, so a person can pull pages off a copier whatever
the toolbar is showing. Behind it, Services/ScanService.cs talks to the
copier through WIA - the imaging service that ships with Windows, reached
late-bound so a machine without it fails at a check instead of at load - and
Features/Scan/ScanDialog picks the copier, the feed, the colour, the detail
and the paper. Pages come back as images and take the same route into a
document as an imported photograph. "Make the words searchable" runs the
text recognition the application already carries.
3. The official MMD lockup, in white, because the band is red now.
4. The MMD design system locked on 2026-08-28: ONE merged top bar carrying the
mark, the name, the tabs and the tools; 4px corners; 24px window buttons;
the bevel on title bars only. Colours are NOT adjusted - the Red Plate
silver and ink set already in Themes/MMD.xaml is untouched.
Also fixed, both found by looking at the running application at 800x600:
- The default 1000x700 window does not fit an 800x600 plant screen, and a
window taller than the screen puts its own title bar - and therefore Scan,
the window buttons and the tabs - above the top edge where nobody can reach
them. MainWindow now starts maximised when the screen cannot hold the
default.
- The close button was invisible: CaptionCloseBrush defaults to the danger
red, which on a red band is red on red. The window buttons are white now,
and close inverts to a white plate with a red cross on hover.
Built and run on mmd-win-test-01 at 800x600 through keyboard and mouse only.
Signed with the internal MMD code-signing certificate and timestamped.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
- Services/PdfRedactText.cs: strip text whose origin falls inside a CoverAnnotation
from the page content stream at save time, hooked into PdfBurn.DrawAnnotationsIntoDoc.
Fixes edited values staying recoverable by text extraction.
- Themes/MMD.xaml replaces all thirteen themes; picker and accent strip removed; no dark mode.
- Rename KillerPDF -> MMD PDF across code, resources, packaging and locale strings; new icon.
- Remove the upstream author credit and the in-app install button.
kua-agent
