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 * paste[] = {
"28 28 5 1",
"X	c Gray75 s backgroundToolBarColor",
"o	c Gray60",
"O	c Gray90",
"+	c Gray60",
"@	c white",
"XXXXXXXXXXXXXXXXXXXXXXXXXXXX",
"XXXXXXXXXXXXXXXXXXXXXXXXXXXX",
"XXXXXXXXXXXXXXXXXXXXXXXXXXXX",
"XXXXXXXXXXXXXooXXXXXXXXXXXXX",
"XXXXXXXXXXXXoOOoXXXXXXXXXXXX",
"XXXXXXooooooOooOooooooXXXXXX",
"XXXXXo++++oOOOOOOo++++oXXXXX",
"XXXXXo+++oooooooooo+++oXXXXX",
"XXXXXo++++++++++++++++oXXXXX",
"XXXXXo++++++++++++++++oXXXXX",
"XXXXXo++++++++++++++++oXXXXX",
"XXXXXo++++++++++++++++oXXXXX",
"XXXXXo++++++++++++++++oXXXXX",
"XXXXXo++++++oooooooooooXXXXX",
"XXXXXo++++++o@@@@@@@@ooXXXXX",
"XXXXXo++++++o@@@@@@@@o+oXXXX",
"XXXXXo++++++o@oooooo@ooooXXX",
"XXXXXo++++++o@@@@@@@@@@@oXXX",
"XXXXXo++++++o@oooo@@@@@@oXXX",
"XXXXXo++++++o@@@@@@@@@@@oXXX",
"XXXXXo++++++o@@@@@@@@@@@oXXX",
"XXXXXo++++++o@oooooooo@@oXXX",
"XXXXXoooooooo@@@@@@@@@@@oXXX",
"XXXXXXXXXXXXo@@@@@@@@@@@oXXX",
"XXXXXXXXXXXXo@@@@@@@@@@@oXXX",
"XXXXXXXXXXXXoooooooooooooXXX",
"XXXXXXXXXXXXXXXXXXXXXXXXXXXX",
"XXXXXXXXXXXXXXXXXXXXXXXXXXXX"};