Another work around would be to use Preferences to select "enlarge window contents to improve readability" or to set the window zoom to a larger figure.
Here in our mixed xp/windows 7 LAN, I set up a preferences file that looks up a zoom percentage for each user based on their user name--which I've set up to identify the specific computer rather than the user and it then sets a global field to this value as well as the zoom level of the current window. Any scripts that open a new window check the global and set the zoom to match.
I've seen that preference setting too. But it only affects the display of the Filemaker database and not the system fonts - although it does a better job of zooming in than the windows system. My point is that the Windows System has a global zoom funtion which corrupts the look of things in Filemaker. When the Windows Display setting is set to zoom it pixelates EVERYTHING in Filemaker. If you adjust the view of the database zoom percent it has no affect on the operating system i.e. menus are still small.
I can see that setting a 'zoom' variable per device would be handy in some cirumstances, but makes it hard to predict what dimensions to create the layout at to make the most of the screen real estate. It is also possible to determine what kind of device/platform is being used and set it that way i.e. it looks different on mac OS, iOS, Windows etc.