Mercurial > hg > xemacs-beta

comparison src/frame.c @ 209:41ff10fd062f r20-4b3

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Import from CVS: tag r20-4b3
author cvs
date Mon, 13 Aug 2007 10:04:58 +0200
parents acd284d43ca1
children 78f53ef88e17
comparison
equal deleted inserted replaced
208:f427b8ec4379 209:41ff10fd062f
2197 Finally, if a frame property symbol has the property `frame-property-alias' 2197 Finally, if a frame property symbol has the property `frame-property-alias'
2198 on it, then the value will be used in place of that symbol when looking 2198 on it, then the value will be used in place of that symbol when looking
2199 up and setting frame property values. This allows you to alias one 2199 up and setting frame property values. This allows you to alias one
2200 frame property name to another. 2200 frame property name to another.
2201 2201
2202 See the variables `default-x-frame-plist' and `default-tty-frame-plist' 2202 See the variables `default-x-frame-plist', `default-tty-frame-plist'
2203 for a description of the properties recognized for particular types of 2203 and `default-w32-frame-plist' for a description of the properties
2204 frames. 2204 recognized for particular types of frames.
2205 */ 2205 */
2206 (frame, plist)) 2206 (frame, plist))
2207 { 2207 {
2208 struct frame *f = decode_frame (frame); 2208 struct frame *f = decode_frame (frame);
2209 Lisp_Object tail; 2209 Lisp_Object tail;
2311 FROB (Qwidth, make_int (FRAME_WIDTH (f))); 2311 FROB (Qwidth, make_int (FRAME_WIDTH (f)));
2312 /* NOTE: FSF returns Qnil instead of Qt for FRAME_HAS_MINIBUF_P. 2312 /* NOTE: FSF returns Qnil instead of Qt for FRAME_HAS_MINIBUF_P.
2313 This is over-the-top bogosity, because it's inconsistent with 2313 This is over-the-top bogosity, because it's inconsistent with
2314 the semantics of `minibuffer' when passed to `make-frame'. 2314 the semantics of `minibuffer' when passed to `make-frame'.
2315 Returning Qt makes things consistent. */ 2315 Returning Qt makes things consistent. */
2316 FROB (Qminibuffer, (FRAME_HAS_MINIBUF_P (f) ? Qt : 2316 FROB (Qminibuffer, (FRAME_MINIBUF_ONLY_P (f) ? Qonly :
2317 FRAME_MINIBUF_ONLY_P (f) ? Qonly : 2317 FRAME_HAS_MINIBUF_P (f) ? Qt :
2318 FRAME_MINIBUF_WINDOW (f))); 2318 FRAME_MINIBUF_WINDOW (f)));
2319 FROB (Qunsplittable, FRAME_NO_SPLIT_P (f) ? Qt : Qnil); 2319 FROB (Qunsplittable, FRAME_NO_SPLIT_P (f) ? Qt : Qnil);
2320 FROB (Qbuffer_predicate, f->buffer_predicate); 2320 FROB (Qbuffer_predicate, f->buffer_predicate);
2321 2321
2322 #undef FROB 2322 #undef FROB
2379 FROB (Qwidth, make_int (FRAME_WIDTH (f))); 2379 FROB (Qwidth, make_int (FRAME_WIDTH (f)));
2380 /* NOTE: FSF returns Qnil instead of Qt for FRAME_HAS_MINIBUF_P. 2380 /* NOTE: FSF returns Qnil instead of Qt for FRAME_HAS_MINIBUF_P.
2381 This is over-the-top bogosity, because it's inconsistent with 2381 This is over-the-top bogosity, because it's inconsistent with
2382 the semantics of `minibuffer' when passed to `make-frame'. 2382 the semantics of `minibuffer' when passed to `make-frame'.
2383 Returning Qt makes things consistent. */ 2383 Returning Qt makes things consistent. */
2384 FROB (Qminibuffer, (FRAME_HAS_MINIBUF_P (f) ? Qt : 2384 FROB (Qminibuffer, (FRAME_MINIBUF_ONLY_P (f) ? Qonly :
2385 FRAME_MINIBUF_ONLY_P (f) ? Qonly : 2385 FRAME_HAS_MINIBUF_P (f) ? Qt :
2386 FRAME_MINIBUF_WINDOW (f))); 2386 FRAME_MINIBUF_WINDOW (f)));
2387 FROB (Qunsplittable, FRAME_NO_SPLIT_P (f) ? Qt : Qnil); 2387 FROB (Qunsplittable, FRAME_NO_SPLIT_P (f) ? Qt : Qnil);
2388 FROB (Qbuffer_predicate, f->buffer_predicate); 2388 FROB (Qbuffer_predicate, f->buffer_predicate);
2389 2389
2390 #undef FROB 2390 #undef FROB
2621 int new_pixheight, new_pixwidth; 2621 int new_pixheight, new_pixwidth;
2622 int font_height, font_width; 2622 int font_height, font_width;
2623 2623
2624 /* #### Chuck -- shouldn't we be checking to see if the frame 2624 /* #### Chuck -- shouldn't we be checking to see if the frame
2625 is being "changed" to its existing size, and do nothing if so? */ 2625 is being "changed" to its existing size, and do nothing if so? */
2626 /* No, because it would hose toolbar updates. The toolbar
2627 update code relies on this function to cause window `top' and
2628 `left' coordinates to be recomputed even though no frame size
2629 change occurs. --kyle */
2626 if (in_display) 2630 if (in_display)
2627 abort (); 2631 abort ();
2628 2632
2629 XSETFRAME (frame, f); 2633 XSETFRAME (frame, f);
2630 2634