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 * news_xpm[] = {
"28 28 5 1",
"X	c Gray75 s backgroundToolBarColor",
"o	c black",
"O	c white",
"+	c gray60",
"@	c gray",
"XXXXXXXXXXXXXXXXXXXXXXXXXXXX",
"XXXXXXXXXXXXXXXXXXXXXXXXXXXX",
"XXXXXXXXXXXXXXXXXXXXXXXXXXXX",
"XXXXXXXXXXXXXXXXXXXXXXXXXXXX",
"XXXXXXXXXXXXXXXXXXXXXXXXXXXX",
"XXXXXXXXXXXXXXXXXXXXXXXXXXXX",
"XXXXXXXXXXXXXXXXXXXXXXXXXXXX",
"XXXXXXXXXXXXXooooooooooXXXXX",
"XXXooooooooooOOOoOOOoOOoXXXX",
"XXoooOOOoOoooOoOoOoOOoOo++XX",
"XXo@oOOooOOooOooOooOooOOo++X",
"oo@o@oOOOOOOOOOOOOOOOOOOOo+X",
"o@@o@oOooooooooooooooOooOo++",
"oo@o@oOOOOOOOOOOOOOOOOOOOOo+",
"oo@@o@oOoOoOoOoooOoOoooooOo+",
"o@o@o@oOOoOooOOOOOOoOooOooOo",
"ooo@@o@oOoooooOoOOooOoooooOo",
"Xo@o@o@oOOooooOOOOOOOOoOooOo",
"XXoo@@o@oOoooooOOooooOoooooo",
"XXo@o@o@oOOooOooOooOoOoooOOo",
"XXXoo@@o@oOoOoooOooooOooOooo",
"XXXoXo@o@oOoooOoOooooOoooo++",
"XXXXoXoo@oOoOooooooooo++++++",
"XXXXXooooooooo++++++++++++++",
"XXXXXXX++++++++++++++++++XXX",
"XXXXXXXX+++++++++XXXXXXXXXXX",
"XXXXXXXXXXXXXXXXXXXXXXXXXXXX",
"XXXXXXXXXXXXXXXXXXXXXXXXXXXX"};