While I can't offer any sort of support anymore, remember that in the previous post here the final source code was made available. This should allow people to locate and fix bugs they find or add new features.
Lately I've been buried in emails (most end up routed into a "MMM support issues" folder I rarely look at now) whinging on about problems with programs where the manifest had "High-DPI Aware" selected.
I cannot reproduce any "bugs" in this myself though I'm not saying there aren't issues. But please note that it makes no sense to mark a program High-DPI Aware if it isn't!
I direct you to the MSDN article on the subject: User Interface - High DPI Awareness.
Marking an application in this way is a declaration of capabilities. Telling Windows that it's true when it is not is just asking for trouble. The link given above is a brief guide to the changes you must make to a program before it should try to "wear the badge" of High-DPI Awareness.
Here is the fragment MMM adds to the application manifest when you seelct the DPI-Awareness option:<application xmlns="urn:schemas-microsoft-com:asm.v3">
Note that this is precisely the information MSDN documents as required. it also works fine for my own programs and those of many others.
Switching Windows to XP DPI-scaling only masks your DPI bugs.
Duplicated comClass Entries
Some people have installed faulty "updates" to several VB6 controls. These have broken many controls with "off by one" errors throughout various properties and methods.
They have also broken binary compatibility and thus add extra registry entries on a system that already has properly functional VB6 controls installed. One symptom of this is that many members of the classes involved will get two <comClass/> entries in the manifest that MMM produces.
MMM cannot "fix" this. It is the result of a machine that has been trashed by installing a faulty update from Microsoft. These "VB6 controls" security rollups" (and note Microsoft tried, tried, and retried getting these right - and never did) are not pushed via Windows Update, so you must have done it explicitly yourself.
As far as I know there is only one reliable fix: reformat and reinstall Windows, then avoid installing the bad updates again.
- Posted at Thursday, October 27, 2011 11:41 PM