#5
Post
by OT » 02 Jun 2018 06:05
For some further testing in of 7.1.0 in a VM I wanted to see how crazy things would become if the font scaling is set to 150%. That is when I discovered that by default, Win7 then performs some graphic up-scaling from 100% scaling of everything so that text and lines look fuzzy (it just enlarges the whole screen image) and not very comfortable to look at, but the dialogs are accessible as they are just enlarged from the 100% view. VTFT editor to code font re-scaling also responds as if the system has 100% font scaling. The application window size was messed up though, I could never resize the window so that I could see the bottom it, it was almost like the bottom was fixed outside the bottom screen. With font scaling is set as high as 150% one need to tick on "Disable display scaling on high DPI settings" under the Compatibility tab of the shortcut to see how bad things really scales. At 125% the display scaling never occurs, so the problems are visible without changing any setting but not quite as bad as at 150%.
1. With the Windows shortcut's display scaling turned off at 150% font scaling things got really crazy. There were actually very few dialogs that had any settings that were accessible in 7.1.0.
2. The second problem, the size of fonts in the VTFT editor and the generated code, did not have as crazy effect on the MMB display as expected. However what happens when the project experiences a change in Windows font scaling, is that all the VTFT font sizes are resized (for instance size 8 at 100% font scaling went down to size 6 at 150% font scaling, which cannot even be selected with the drop down menu), and then apparently re-scaled again when the code is generated. This caused inaccuracies in the scaling so that fonts may not fit the size of boxes chosen for them, but at 150% it was not much worse than at 125%, just different.
Scaling of the chosen font size, (for instance a size 8 ) should scale directly to a certain size in the code (for instance Tahoma 11x13_Regular) by a fixed factor, as if a 100% font scaling factor was used independently of actual Windows font scaling. Then the size displayed on the screen image can apply the 125% scaling factor to display font image on the edit screen correctly if appropriate. As it is now, it appears that fonts are scaled back and forth again causing inaccuracies. (I believe i posted about this about 4 years back). This kind of back and forth scaling would never survive in an electronic CAD package or mechanical CAD package, no one would want to buy such software that could potentially change the project when moved to another computer. Nor would it be accepted in a word processor.
If the editor/code font scaling method is changed in VTFT (which I hope it will), it could become issues with how projects that were created with other than 100% scaling in Windows would be translated. However the conversion routines could prompt for original font scaling of the project, or could figure it out by looking at font size in existing code compared to VTFT editor font size . Perhaps the scaling factors used are even stored in the project file? Also since VTFT has not been very functional with different than 100% font scaling there might not be many projects out there that would be affected.
On top of this as mentioned above the scaling of the space character need to be corrected, particularly at larger font sizes.
mikropascal dsPIC, Visual TFT, MMBdsPIC v.105, 1.10_9A, mikroProg, "Big"(P30F6012A)EasydsPIC2
