Mercurial > hg > xemacs-beta
view etc/toolbar/undo-up.xpm @ 5105:d76a51b29d91
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.
| author | Ben Wing <ben@xemacs.org> |
|---|---|
| date | Sat, 06 Mar 2010 00:01:04 -0600 |
| parents | 376386a54a3c |
| children | 7910031dd78a |
line wrap: on
line source
/* XPM */ static char * undo[] = { "28 28 5 1", "X c Gray75 s backgroundToolBarColor", "o c black", "O c Gray60", "+ c Gray90", "@ c white", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXooXXXXXXX", "XXXXXXXXXXXXXXXXXooOOooooXXX", "XXXXXXXXXXXXXXXooOOOOOOOOooX", "XXXXXXXXXXXXXooOOOOOOOOOooXX", "XXXXXXXXXXXoo++ooooOOOooOoXX", "XXXXXXXXXoo++++++++oooOOoXXX", "XXXXXXXoo+++++++++oooOOOoXXX", "XXXXXoo+++++++++oo++oOOoXXXX", "XXXXoo++++++++oo+++oOooXXXXX", "XXXo++oooo++oo+++++ooXXXXXXX", "XXXo++++++oo+++++ooXXXXXXXXX", "XXo+++++++o++++ooXXXXXXXXXXX", "XXo+++++++o++ooXXXXXXXXXXXXX", "Xoo++++++o+ooXXXXXXXXXXXXXXX", "X@@oooo++ooXXXXXXXXXXXXXXXXX", "X@@@@@@ooXXXXXXXXXXXXXXXXXXX", "X@@@@@@XXXXXXXXXXXXXXXXXXXXX", "X@@@@XXXXXXXXXXXXXXXXXXXXXXX", "X@@@XXXXXXXXXXXXXXXXXXXXXXXX", "X@XXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX"};