I knew that I was right but as usual in these days clients have to prove that they are right as vendors (in this case RME) more and more just state that ?multiple ten thousands of users worldwide do not have your problem? and as a conclusion ?the problem is your system? (or you) and not with the vendor's product!
Even though I stated that I made tests with different systems and that I am software developer the only (and very superficial) answer of MC is repeating all the time the same message.
As a consequence I analysed and in the end tweaked RME?s Settings Dialog program and here is the result:
First, the Settings Dialog program delivered by RME:
[img align=Settings Dialog by RME]http://i43.tinypic.com/2a8i4xl.png[/img]
Second, the same Settings Dialog program tweaked by me:
[img align=Settings Dialog by RME (tweaked)]http://i39.tinypic.com/2unvskg.png[/img]
So what was the reason? As many users already reported, changing any sort of settings didn't influence the behaviour of the Settings Dialog. Why? Because the Settings Dialog doesn't take the OS context into consideration. Up to Windows XP the "standard" dialog font was "MS Sans Serif". From Vista and Windows 7 on the standard dialog font changed to "Segoe UI" which has a significantly smaller footprint to accomodate higher resolutions of these days.
Every Windows programmer knows (except the one who programmed Settings Dialog) that it has to take OS context into consideration. In this case it would mean: If the program is running with Windows XP or earlier use ?MS Sans Serif?. If the program is running with Vista or later OS use ?Segoe UI?.
I edited the resources directly within the Settings Dialog Exe File in order to use ?Segoe UI? instead of ?MS Sans Serif?.
So, in the end, the client did the job of the vendor for free?
MC, you should be glad that I anticipated a problem RME will have when "multiple ten thousands of worldwide XP users" will upgrade to Windows 7.