comparison src/window.c @ 365:30d2cfa1092a r21-1-12

Import from CVS: tag r21-1-12
author cvs
date Mon, 13 Aug 2007 11:00:12 +0200
parents 182f72e8cd0d
children a4f53d9b3154
comparison
equal deleted inserted replaced
364:63c3368d1275 365:30d2cfa1092a
4955 First of all, the units are inconsistent. The frame sizes are measured 4955 First of all, the units are inconsistent. The frame sizes are measured
4956 in characters but the window sizes are stored in pixels. So if a 4956 in characters but the window sizes are stored in pixels. So if a
4957 font size change happened between saving and restoring, the 4957 font size change happened between saving and restoring, the
4958 frame "sizes" maybe equal but the windows still should be 4958 frame "sizes" maybe equal but the windows still should be
4959 resized. This is tickled alot by the new "character size 4959 resized. This is tickled alot by the new "character size
4960 stays constant" policy in 21.0. It leads to very wierd 4960 stays constant" policy in 21.0. It leads to very weird
4961 glitches (and possibly craches when asserts are tickled). 4961 glitches (and possibly craches when asserts are tickled).
4962 4962
4963 Just changing the units doens't help because changing the 4963 Just changing the units doesn't help because changing the
4964 toolbar configuration can also change the pixel positions. 4964 toolbar configuration can also change the pixel positions.
4965 Luckily there is a much simpler way of doing this, see below. 4965 Luckily there is a much simpler way of doing this, see below.
4966 */ 4966 */
4967 previous_frame_width = FRAME_WIDTH (f); 4967 previous_frame_width = FRAME_WIDTH (f);
4968 previous_frame_height = FRAME_HEIGHT (f); 4968 previous_frame_height = FRAME_HEIGHT (f);