Mercurial > hg > xemacs-beta
view lwlib/xlwgcs.h @ 844:047d37eb70d7
[xemacs-hg @ 2002-05-16 13:30:23 by ben]
ui fixes for things that were bothering me
bytecode.c, editfns.c, lisp.h, lread.c: Fix save-restriction to use markers rather than pseudo-markers
(integers representing the amount of text on either side of the
region). That way, all inserts are handled correctly, not just
those inside old restriction.
Add buffer argument to save_restriction_save().
process.c: Clean up very dirty and kludgy code that outputs into a buffer --
use proper unwind protects, etc.
font-lock.c: Do save-restriction/widen around the function -- otherwise, incorrect
results will ensue when a buffer has been narrowed before a call to
e.g. `buffer-syntactic-context' -- something that happens quite often.
fileio.c: Look for a handler for make-temp-name.
window.c, winslots.h: Try to solve this annoying problem: have two frames displaying the
buffer, in different places; in one, temporarily switch away to
another buffer and then back -- and you've lost your position;
it's reset to the other one in the other frame. My current
solution involves window-level caches of buffers and points (also
a cache for window-start); when set-window-buffer is called, it
looks to see if the buffer was previously visited in the window,
and if so, uses the most recent point at that time. (It's a
marker, so it handles changes.)
#### Note: It could be argued that doing it on the frame level
would be better -- e.g. if you visit a buffer temporarily through
a grep, and then go back to that buffer, you presumably want the
grep's position rather than some previous position provided
everything was in the same frame, even though the grep was in
another window in the frame. However, doing it on the frame level
fails when you have two windows on the same frame. Perhaps we
keep both a window and a frame cache, and use the frame cache if
there are no other windows on the frame showing the buffer, else
the window's cache? This is probably something to be configurable
using a specifier. Suggestions please please please?
window.c: Clean up a bit code that deals with the annoyance of window-point
vs. point.
dialog.el: Function to ask a
multiple-choice question, automatically choosing a dialog box or
minibuffer representation as necessary. Generalized version of
yes-or-no-p, y-or-n-p.
files.el: Use get-user-response to ask "yes/no/diff" question when recovering.
"diff" means that a diff is displayed between the current file and the
autosave. (Converts/deconverts escape-quoted as necessary. No more
complaints from you, Mr. Turnbull!) One known problem: when a dialog
is used, it's modal, so you can't scroll the diff. Will fix soon.
lisp-mode.el: If we're filling a string, don't treat semicolon as a comment,
which would give very unfriendly results.
Uses `buffer-syntactic-context'.
simple.el: all changes back to the beginning. (Useful if you've saved the file
in the middle of the changes.)
simple.el: Add option kill-word-into-kill-ring, which controls whether words
deleted with kill-word, backward-kill-word, etc. are "cut" into the
kill ring, or "cleared" into nothingness. (My preference is the
latter, by far. I'd almost go so far as suggesting we make it the
default, as you can always select a word and then cut it if you want
it cut.)
menubar-items.el: Add option corresponding to kill-word-into-kill-ring.
| author | ben |
|---|---|
| date | Thu, 16 May 2002 13:30:58 +0000 |
| parents | c33ae14dd6d0 |
| children | 5460287a3327 |
line wrap: on
line source
/* Tabs Widget for XEmacs. Copyright (C) 1999 Edward A. Falk This file is part of XEmacs. XEmacs is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2, or (at your option) any later version. XEmacs is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with XEmacs; see the file COPYING. If not, write to the Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. */ /* Synched up with: Gcs 1.7 */ #ifndef GCS_H #define GCS_H /* Overview of functions provided here: * * AllocFgGC() * Given a foreground pixel & a font, return an appropriate GC * * AllocBackgroundGC() * Given a widget, return a GC for painting the background color * * AllocShadeGC() * Given foreground, background, a contrast value & be_nice_to_colormap * flag, return a GC suitable for rendering in an intermediate color, * as determined by contrast. May return a dither pattern or a * solid color, as appropriate. * * Contrast 0 = background color, 100 = foreground color. It is legal * for contrast to be more than 100 or less than 0. * * AllocGreyGC() * Given widget, foreground, font, contrast & be_nice_to_colormap, * return a shade GC (see above) based on foreground and widget * background. * * AllocTopShadowGC() * Given widget, contrast & be_nice_to_colormap, return a GC suitable * for rendering the top shadow. * * Contrast 0 = use background pixel. Contrast > 0 = use brighter * colors. * * AllocBotShadowGC() * Given widget, contrast & be_nice_to_colormap, return a GC suitable * for rendering the bottom shadow. * * Contrast 0 = use background pixel. Contrast > 0 = use darker * colors. * * AllocArmShadowGC() * Given widget, contrast & be_nice_to_colormap, return a GC suitable * for rendering the "armed" shadow. * * Contrast 0 = use background pixel. Contrast > 0 = use darker * colors. * * AllocShadowPixel() * Given a widget & scale factor, allocate & return a color darker * or lighter than the background pixel, as determined by scale. * * Scale 100 = use background pixel. Scale > 100 = brighter color, * Scale < 100 = darker color. * * AllocGreyPixel() * Given two pixel values and scale factor, allocate & return a * pixel value between them, according to scale. * * Scale == 0: background color * Scale == 100: foreground color * 0<Scale<100: intermediate color * Scale > 100: more foreground * Scale < 0: more background * * * AllocGreyPixelC() * Given two color values and scale factor, allocate & return a * pixel value between them, according to scale. * * Scale == 0: background color * Scale == 100: foreground color * 0<Scale<100: intermediate color * Scale > 100: more foreground * Scale < 0: more background * * Draw3dBox() * Given box dimensions, shadow width, top shadow GC & bottom shadow GC, * draw a 3-d box. */ #if NeedFunctionPrototypes extern GC AllocFgGC( Widget w, Pixel fg, Font font) ; extern GC AllocBackgroundGC( Widget w, Font font) ; extern GC AllocShadeGC( Widget w, Pixel fg, Pixel bg, Font, int contrast, Bool ) ; extern GC AllocGreyGC( Widget w, Pixel fg, Font, int, Bool ) ; extern GC AllocTopShadowGC( Widget w, int contrast, int ) ; extern GC AllocBotShadowGC( Widget w, int contrast, int ) ; extern GC AllocArmGC( Widget w, int contrast, int) ; extern Pixel AllocShadowPixel(Widget, int scale) ; extern Pixel AllocGreyPixel(Widget, Pixel fg, Pixel bg, int scale) ; extern Pixel AllocGreyPixelC(Widget, XColor *fg, XColor *bg, int scale) ; extern void Draw3dBox(Widget w, int x, int y, int wid, int hgt, int s, GC topgc, GC botgc) ; #if XtSpecificationRelease < 5 extern GC XtAllocateGC(Widget, int depth, unsigned long mask, XGCValues *, unsigned long dynamic, unsigned long dontcare) ; #endif #else extern GC AllocFgGC() ; extern GC AllocBackgroundGC() ; extern GC AllocShadeGC() ; extern GC AllocGreyGC() ; extern GC AllocTopShadowGC() ; extern GC AllocBotShadowGC() ; extern GC AllocArmGC() ; extern Pixel AllocShadowPixel() ; extern Pixel AllocGreyPixel() ; extern Pixel AllocGreyPixelC() ; extern void Draw3dBox() ; #if XtSpecificationRelease < 5 extern GC XtAllocateGC() ; #endif #endif #endif /* GCS_H */