Dialogs still carried the upstream wordmark. Controls/DialogChrome.cs built the caption as two runs, the literal "Killer" plus "PDF", which is why a search for "KillerPDF" never found it. Dialogs such as "Open a PDF first." therefore still said KillerPDF. The first run is now "MMD ", so every dialog caption reads MMD PDF.
The window title bar showed only the MMD mark. MainWindow.xaml now sets the words next to it on both the crisp and the shadow layer, so the title bar reads MMD PDF.
Not runtime-verified at the time of opening; the build and the signed-in check on the Windows test VM follow.
Two things Ben caught in the running app.
1. Dialogs still carried the upstream wordmark. Controls/DialogChrome.cs built the caption as two runs, the literal "Killer" plus "PDF", which is why a search for "KillerPDF" never found it. Dialogs such as "Open a PDF first." therefore still said KillerPDF. The first run is now "MMD ", so every dialog caption reads MMD PDF.
2. The window title bar showed only the MMD mark. MainWindow.xaml now sets the words next to it on both the crisp and the shadow layer, so the title bar reads MMD PDF.
Not runtime-verified at the time of opening; the build and the signed-in check on the Windows test VM follow.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Two things Ben caught in the running app.
Dialogs still carried the upstream wordmark. Controls/DialogChrome.cs built the caption as two runs, the literal "Killer" plus "PDF", which is why a search for "KillerPDF" never found it. Dialogs such as "Open a PDF first." therefore still said KillerPDF. The first run is now "MMD ", so every dialog caption reads MMD PDF.
The window title bar showed only the MMD mark. MainWindow.xaml now sets the words next to it on both the crisp and the shadow layer, so the title bar reads MMD PDF.
Not runtime-verified at the time of opening; the build and the signed-in check on the Windows test VM follow.