Mercurial > hg > xemacs-beta
view man/lispref/range-tables.texi @ 5090:0ca81354c4c7
Further frame-geometry cleanups
-------------------- ChangeLog entries follow: --------------------
man/ChangeLog addition:
2010-03-03 Ben Wing <ben@xemacs.org>
* internals/internals.texi (Intro to Window and Frame Geometry):
* internals/internals.texi (The Paned Area):
* internals/internals.texi (The Displayable Area):
Update to make note of e.g. the fact that the bottom gutter is
actually above the minibuffer.
src/ChangeLog addition:
2010-03-03 Ben Wing <ben@xemacs.org>
* emacs.c:
* emacs.c (assert_equal_failed):
* lisp.h:
* lisp.h (assert_equal):
New fun assert_equal, asserting that two values == each other, and
printing out both values upon failure.
* frame-gtk.c (gtk_initialize_frame_size):
* frame-impl.h:
* frame-impl.h (FRAME_TOP_INTERNAL_BORDER_START):
* frame-impl.h (FRAME_BOTTOM_INTERNAL_BORDER_START):
* frame-impl.h (FRAME_LEFT_INTERNAL_BORDER_START):
* frame-impl.h (FRAME_PANED_TOP_EDGE):
* frame-impl.h (FRAME_NONPANED_SIZE):
* frame-x.c (x_initialize_frame_size):
* frame.c:
* gutter.c (get_gutter_coords):
* gutter.c (calculate_gutter_size):
* gutter.h:
* gutter.h (WINDOW_REAL_TOP_GUTTER_BOUNDS):
* gutter.h (FRAME_TOP_GUTTER_BOUNDS):
* input-method-xlib.c:
* input-method-xlib.c (XIM_SetGeometry):
* redisplay-output.c (clear_left_border):
* redisplay-output.c (clear_right_border):
* redisplay-output.c (redisplay_output_pixmap):
* redisplay-output.c (redisplay_clear_region):
* redisplay-output.c (redisplay_clear_top_of_window):
* redisplay-output.c (redisplay_clear_to_window_end):
* redisplay-xlike-inc.c (XLIKE_clear_frame):
* redisplay.c:
* redisplay.c (UPDATE_CACHE_RETURN):
* redisplay.c (pixel_to_glyph_translation):
* toolbar.c (update_frame_toolbars_geometry):
* window.c (Fwindow_pixel_edges):
Get rid of some redundant macros. Consistently use the
FRAME_TOP_*_START, FRAME_RIGHT_*_END, etc. format. Rename
FRAME_*_BORDER_* to FRAME_*_INTERNAL_BORDER_*. Comment out
FRAME_BOTTOM_* for gutters and the paned area due to the
uncertainty over where the paned area actually begins. (Eventually
we should probably move the gutters outside the minibuffer so that
the paned area is contiguous.) Use FRAME_PANED_* more often in the
code to make things clearer.
Update the diagram to show that the bottom gutter is inside the
minibuffer (!) and that there are "junk boxes" when you have left
and/or right gutters (dead boxes that are mistakenly left uncleared,
unlike the corresponding scrollbar dead boxes). Update the text
appropriately to cover the bottom gutter position, etc.
Rewrite gutter-geometry code to use the FRAME_*_GUTTER_* in place of
equivalent expressions referencing other frame elements, to make the
code more portable in case we move around the gutter location.
Cleanup FRAME_*_GUTTER_BOUNDS() in gutter.h.
Add some #### GEOM! comments where I think code is incorrect --
typically, it wasn't fixed up properly when the gutter was added.
Some cosmetic changes.
author | Ben Wing <ben@xemacs.org> |
---|---|
date | Wed, 03 Mar 2010 05:07:47 -0600 |
parents | 6772ce4d982b |
children | 9fae6227ede5 |
line wrap: on
line source
@c -*-texinfo-*- @c This is part of the XEmacs Lisp Reference Manual. @c Copyright (C) 1996 Ben Wing. @c See the file lispref.texi for copying conditions. @setfilename ../../info/range-tables.info @node Range Tables, Databases, Hash Tables, top @chapter Range Tables @cindex Range Tables A range table is a table that efficiently associates values with ranges of fixnums. Note that range tables have a read syntax, like this: @example #s(range-table type start-closed-end-open data ((-3 2) foo (5 20) bar)) @end example This maps integers in the range [-3, 2) to @code{foo} and integers in the range [5, 20) to @code{bar}. By default, range tables have a @var{type} of @code{start-closed-end-open}. (@strong{NOTE}: This is a change from 21.4 and earlier, where there was no @var{type} and range tables were always closed on both ends.) This makes them work like text properties. @defun range-table-p object Return non-@code{nil} if @var{object} is a range table. @end defun @menu * Introduction to Range Tables:: Range tables efficiently map ranges of integers to values. * Working With Range Tables:: Range table functions. @end menu @node Introduction to Range Tables @section Introduction to Range Tables @defun make-range-table &optional type Make a new, empty range table. @var{type} is a symbol indicating how ranges are assumed to function at their ends. It can be one of @example SYMBOL RANGE-START RANGE-END ------ ----------- --------- `start-closed-end-open' (the default) closed open `start-closed-end-closed' closed closed `start-open-end-open' open open `start-open-end-closed' open closed @end example A @dfn{closed} endpoint of a range means that the number at that end is included in the range. For an @dfn{open} endpoint, the number would not be included. For example, a closed-open range from 5 to 20 would be indicated as @samp{[5, 20)} where a bracket indicates a closed end and a parenthesis an open end, and would mean `all the numbers between 5 and 20', including 5 but not 20. This seems a little strange at first but is in fact extremely common in the outside world as well as in computers and makes things work sensibly. For example, if I say "there are seven days between today and next week today", I'm including today but not next week today; if I included both, there would be eight days. Similarly, there are 15 (= 20 - 5) elements in the range @samp{[5, 20)}, but 16 in the range @samp{[5, 20]}. @end defun @defun copy-range-table range-table This function returns a new range table which contains the same values for the same ranges as @var{range-table}. The values will not themselves be copied. @end defun @node Working With Range Tables @section Working With Range Tables @defun get-range-table pos range-table &optional default This function finds value for position @var{pos} in @var{range-table}. If there is no corresponding value, return @var{default} (defaults to @code{nil}). @strong{NOTE}: If you are working with ranges that are closed at the start and open at the end (the default), and you put a value for a range with @var{start} equal to @var{end}, @code{get-range-table} will @strong{not} return that value! You would need to set @var{end} one greater than @var{start}. @end defun @defun put-range-table start end value range-table This function sets the value for range (@var{start}, @var{end}) to be @var{value} in @var{range-table}. @strong{NOTE}: Unless you are working with ranges that are closed at both ends, nothing will happen if @var{start} equals @var{end}. @end defun @defun remove-range-table start end range-table This function removes the value for range (@var{start}, @var{end}) in @var{range-table}. @end defun @defun clear-range-table range-table This function flushes @var{range-table}. @end defun @defun map-range-table function range-table This function maps @var{function} over entries in @var{range-table}, calling it with three args, the beginning and end of the range and the corresponding value. @end defun