fix Stephen's bug with frame sizing -------------------- ChangeLog entries follow: -------------------- src/ChangeLog addition: 2010-03-05 Ben Wing <ben@xemacs.org> * frame.c: * frame.c (Fframe_pixel_height): * frame.c (Fframe_displayable_pixel_height): * frame.c (Fframe_pixel_width): * frame.c (Fframe_displayable_pixel_width): * frame.c (Fset_frame_pixel_height): * frame.c (Fset_frame_displayable_pixel_height): * frame.c (Fset_frame_pixel_width): * frame.c (Fset_frame_displayable_pixel_width): * frame.c (get_frame_char_size): * frame.c (change_frame_size_1): Make it so that `frame-pixel-height', `set-frame-pixel-height', etc. use updated values for the displayable or total pixel size that will reflect what will happen as of the next redisplay. This basically means using the character-cell height and converting on-the-fly to pixel units. In the process, make sure FRAME_CHARWIDTH/ FRAME_CHARHEIGHT are always correct and change get_frame_char_size() to simply use them; the old logic in that function was inlined into change_frame_size_1(), which is the only place that needs the logic.

/* XPM */
static char * bug_xpm[] = {
"28 28 6 1",
"X	c Gray75 s backgroundToolBarColor",
"o	c Gray60",
"O	c Gray40",
"+	c Gray60",
"@	c white",
"#	c Gray90",
"XXXXXXXXXXXXXXXXXXXXXXXXXXXX",
"XXXXXXXXXXXXXXXXXXXXXXXXXXXX",
"XXXXXXooooooooooooooooXXXXXX",
"XXXXXoooooooooOoOoOoOooXXXXX",
"XXXXXoooooooooOoOoOoOooXXXXX",
"XXXXXoooooooooooooooooo+XXXX",
"XXXXXXo@@@@@@@@@@@##Xo++XXXX",
"XXXXXo@@@@@@@@@@@@##XXo+XXXX",
"XXXXXo@@@@@@@@@@@@##XXoXXXXX",
"XXXXXo@@@@@@@@@@@@##XXo+XXXX",
"XXXXXo@@@@@@@@@@@@##XXo+XXXX",
"XXXXXo@@@@@@o@@oo@##XXo+XXXX",
"XXXXXo@@@o@@o@oooo##XXo+XXXX",
"XXXXXo@@@@o@oo@ooo##XXo+XXXX",
"XXXXXo@@@@@oooooo@##XXo+XXXX",
"XXXXXo@ooo@ooooo@@##XXo+XXXX",
"XXXXXo@@@oo@oooooo##XXo+XXXX",
"XXXXXo@@o@ooooo@@@##XXo+XXXX",
"XXXXXo@oooooo@@o@@##XXo+XXXX",
"XXXXXo@oooooo@@@o@##XXo+XXXX",
"XXXXXo@ooooooo@@@@##XXo+XXXX",
"XXXXXo@ooooo@o@@@@##XXo+XXXX",
"XXXXXo@@ooo@@o@@@@##XXo+XXXX",
"XXXXXo@@@@@@@@@@@@##XXo+XXXX",
"XXXXXXoooooooooooooooo++XXXX",
"XXXXXX++++++++++++++++++XXXX",
"XXXXXXX++++++++++++++++XXXXX",
"XXXXXXXXXXXXXXXXXXXXXXXXXXXX"};