Mercurial > emacs
annotate admin/notes/iftc @ 111566:b4dbe6c4111e
Cleanup of window coordinate positioning code.
Now, text area click input events measure Y from the top of the text
area, excluding the header line if any.
* src/dispnew.c (buffer_posn_from_coords): Assume that X counts from
the start of the text area.
* src/keyboard.c (make_lispy_position): For text area clicks, record Y
pixel position relative to the text area, excluding header line.
Also change X and Y to Lisp_Objects, not pointers; don't return
coordinate values via pointers. Pass ON_TEXT_AREA coordinate to
buffer_posn_from_coords counting from the start of the text area.
(Fposn_at_x_y, make_lispy_event): Callers changed.
* src/w32term.c (w32_read_socket):
* src/msdos.c (dos_rawgetc):
* src/xterm.c (handle_one_xevent): Likewise.
* src/window.c (coordinates_in_window): Change X and Y to ints rather
than pointers; don't return coordinates via pointers.
(struct check_window_data): Change X and Y from pointers to ints.
(window_from_coordinates): Remove args WX and WY; don't return
coordinates via pointers.
(Fcoordinates_in_window_p, window_from_coordinates):
(check_window_containing, Fwindow_at): Callers changed.
(window_relative_x_coord): New function.
* src/window.h (window_from_coordinates, window_relative_x_coord):
Update prototypes.
* src/xdisp.c (remember_mouse_glyph): Change window_from_coordinates
call. Use window_relative_x_coord.
(note_mouse_highlight): Change window_from_coordinates call.
author | Chong Yidong <cyd@stupidchicken.com> |
---|---|
date | Tue, 16 Nov 2010 21:37:45 -0500 |
parents | 695cf19ef79e |
children | 375f2633d815 ef719132ddfa |
rev | line source |
---|---|
45625 | 1 Iso-Functional Type Contour |
2 | |
3 | |
4 This is a term coined to describe "column int->float" change approach, and can | |
5 be used whenever low-level types need to change (hopefully not often!) but the | |
6 meanings of the values (whose type has changed) do not. | |
7 | |
8 The premise is that changing a low-level type potentially means lots of code | |
9 needs to be changed as well, and the question is how to do this incrementally, | |
10 which is the preferred way to change things. | |
11 | |
12 Say LOW and HIGH are C functions: | |
13 | |
14 int LOW (void) { return 1; } | |
15 void HIGH (void) { int value = LOW (); } | |
16 | |
17 We want to convert LOW to return float, so we cast HIGH usage: | |
18 | |
19 float LOW (void) { return 1.0; } | |
20 void HIGH (void) { int value = (int) LOW (); } /* iftc */ | |
21 | |
22 The comment /* iftc */ is used to mark this type of casting to differentiate | |
23 it from other casting. We commit the changes and can now go about modifying | |
24 LOW and HIGH separately. When HIGH is ready to handle the type change, the | |
25 cast can be removed. | |
52401 | 26 |
27 ;;; arch-tag: 3309cc41-5d59-421b-b7be-c94b04083bb5 |