-
I have been using ScaleMode 7 (centimeters) in an application which does gravitational computations and displays results as dots moving in a Picture Box.
The application resizes the Picture box when User changes the Form size (by dragging or maximizing). The application also resizes the Picture Box when user changes Screen Resolution (EG: From 640X480 to 1024X768).
An experimental application I use indicates that Pixels, inches, centimeters are some kind of "logical" units instead of being absolute. It looks as if Pixel size changes with Screen resolution, but certain ratios are keep constant. EG: Twips per Pixel seems to be a constant, making Twips a "logical" rather than an absolute unit.
My gravitational application works okay because absolute units are not required (Viewer position changes scale of the graphics). For future applications, I would like to understand what is going on when Form size changes, and/or Screen resolution changes, and/or an application runs with a different monitor. What units, if any, are uneffected? Which are scaled or "logical" units? I am particularly concerned with how to cope with a different monitor than the one I have on my system.
Is there something I could read to enlighten me on this? I have the MSDN Library on CD, but the pertinent data seems scattered in bit & pieces, making it hard to see the forest due to all the trees.
Thanx for any help you can give me.
-
I'm not sure what you mean with absolute, i have never used centimeters, but they might be absolute to a ruler.
Pixels are always absolute, to the screen size.
But i use twips by default as form position is measured in twips.
You can use these methods to convert between scales:
ScaleX (width, fromscale, toscale)
ScaleY (height, fromscale, toscale)
