Skip to content
Snippets Groups Projects
Commit 535d91cf authored by layer's avatar layer
Browse files

2.2.2.19

parent ffdf0d79
No related branches found
No related tags found
No related merge requests found
...@@ -10,6 +10,16 @@ If there are user-visible changes in this commit, then list the ...@@ -10,6 +10,16 @@ If there are user-visible changes in this commit, then list the
<standard changelog date stamp> <standard changelog date stamp>
* <changes go here...> * <changes go here...>
*******************************************************************************
2.2.2.19
2000-07-06 Kevin Layer <layer@ultra>
new file:
* RELNOTES.60
changed file:
* RELNOTES: move to RELNOTES.60 (and filed rfe)
******************************************************************************* *******************************************************************************
2.2.2.18 -- join from cley3 branch 2.2.2.18 -- join from cley3 branch
next merge tag: cley3_merge1 next merge tag: cley3_merge1
......
...@@ -13,106 +13,4 @@ developers or documentation. ...@@ -13,106 +13,4 @@ developers or documentation.
************* add new entries below this line ********************************* ************* add new entries below this line *********************************
1. rfe3925. CLIM now works in a case-sensitive Lisp. CLIM now will 1. rfe/bug# description....
work in two flavours of Lisp: `traditional' ANSI Lisp -- standard
CL symbols are uppercase, the reader converts non-escaped symbols
to uppercase; `modern' Lisp -- standard CL symbols are lowercase,
and the reader does no case conversion. In the former case, all
exported CLIM symbols are uppercase as before; in the latter they
are lowercase.
2. spr21587. On Windows platforms, NOTIFY-USER now always raises the
dialog box it creates to the top of the window stack. Formerly it
could be buried behind other windows if the CLIM application frame
was itself buried.
3. bug8764. Lisp will not prompt you to be sure you want to exit Lisp
if CLIM timers have been used. Previously if exited Lisp it would
ask you to confirm that you wanted to do so if you'd ever used a
timer.
4. <norfe>. For Unix/Linux the CLIM debug fasls (clim-debug.fasl,
clim-debugwnn.fasl and clim-debuxm.fasl) are empty. The debugging
code is now included in the normal fasls and the empty files
included for backwards compatibility. In a future release they
will disappear.
5. <norfe>. CLIM has been changed so that, the standard frame
top-level loop defaultly rebinds *error-output* to itself, and not
to one of the frame panes. This is an incompatible change, which
was made to stop problems when Lisp messages (unrelated to the CLIM
application) were getting printed to CLIM panes. This is at best
annoying, and at worst can cause errors in incremental redisplay.
Rather than hard-wire this change, it is controlled by an argument
to make-application-frame / make-instance of
standard-application-frame:
(make-application-frame ... :non-frame-stream-names <name list>)
Will cause the default top-level loop to rebind the values of the
standard streams named in <name list> to themselves, not to CLIM
panes, even when there are suitable panes available. The default
case is as if you said:
(make-application-frame ... :non-frame-stream-names '(*error-output*))
And you can inhibit the new behaviour by saying:
(make-application-frame ... :non-frame-stream-names '())
or providing this as a default-initarg in a frame class definition.
Note that this behaviour is controlled in terms of stream *names*
not streams, and in fact it is more general than just
*error-output*. The names that make sense in the list are
*standard-output*, *standard-output*, *error-output*, *query-io*
and *pointer-documentation-output*.
The behaviour of the generic functions frame-standard-output,
frame-standard-input, frame-query-io, frame-error-output and
frame-pointer-documentation-output are altered by this change. If
the corresponding stream will be rebound to its old value in the
frame, the methods defined on standard-application-frame for these
generic functions will return nil rather than a stream.
5. rfe4072. On Unix, more of the scrollbar functionality defined in
the CLIM spec is now supported, and the values of scrollbars have
much finer quantisation, which allows scrolling panes with very
many lines accurately.
:scroll-to-bottom-callback [scroll-bar initarg]
-- specify a callback that is called on scroll to bottom. The
callback should be a function of one argument, the scrollbar
(scroll-bar-scroll-to-bottom-callback <scroll-bar>) [generic function]
-- return the callback called when scrolling to bottom, or NIL if
none is defined. This corresponds to the value of the
:scroll-to-bottom-callback initarg.
(scroll-to-bottom-callback <scroll-bar> <client> <gadget-id>
<value>) [generic function]
-- callback function called when the scrollbar scrolls to bottom.
Similar sets of initargs and functions exist for
...to-top... -- scroll to top
...down-line... -- scroll down single line
...up-line... -- scroll up single line
...down-page... -- scroll down page
...up-page... -- scroll up page.
Note the behaviour of these functions is that, for instance, the
default method on scroll-to-bottom-callback will call the value of
(scroll-bar-scroll-to-bottom-callback <scrollbar>) on the scrollbar
if it is non-NIL.
On Windows the names exist but the functions are not called.
Release notes entries for the next release. -*- mode: text -*-
rfe4169: items 1-5
************* add new entries below this line *********************************
1. rfe3925. CLIM now works in a case-sensitive Lisp. CLIM now will
work in two flavours of Lisp: `traditional' ANSI Lisp -- standard
CL symbols are uppercase, the reader converts non-escaped symbols
to uppercase; `modern' Lisp -- standard CL symbols are lowercase,
and the reader does no case conversion. In the former case, all
exported CLIM symbols are uppercase as before; in the latter they
are lowercase.
2. spr21587. On Windows platforms, NOTIFY-USER now always raises the
dialog box it creates to the top of the window stack. Formerly it
could be buried behind other windows if the CLIM application frame
was itself buried.
3. bug8764. Lisp will not prompt you to be sure you want to exit Lisp
if CLIM timers have been used. Previously if exited Lisp it would
ask you to confirm that you wanted to do so if you'd ever used a
timer.
4. <norfe>. For Unix/Linux the CLIM debug fasls (clim-debug.fasl,
clim-debugwnn.fasl and clim-debuxm.fasl) are empty. The debugging
code is now included in the normal fasls and the empty files
included for backwards compatibility. In a future release they
will disappear.
5. <norfe>. CLIM has been changed so that, the standard frame
top-level loop defaultly rebinds *error-output* to itself, and not
to one of the frame panes. This is an incompatible change, which
was made to stop problems when Lisp messages (unrelated to the CLIM
application) were getting printed to CLIM panes. This is at best
annoying, and at worst can cause errors in incremental redisplay.
Rather than hard-wire this change, it is controlled by an argument
to make-application-frame / make-instance of
standard-application-frame:
(make-application-frame ... :non-frame-stream-names <name list>)
Will cause the default top-level loop to rebind the values of the
standard streams named in <name list> to themselves, not to CLIM
panes, even when there are suitable panes available. The default
case is as if you said:
(make-application-frame ... :non-frame-stream-names '(*error-output*))
And you can inhibit the new behaviour by saying:
(make-application-frame ... :non-frame-stream-names '())
or providing this as a default-initarg in a frame class definition.
Note that this behaviour is controlled in terms of stream *names*
not streams, and in fact it is more general than just
*error-output*. The names that make sense in the list are
*standard-output*, *standard-output*, *error-output*, *query-io*
and *pointer-documentation-output*.
The behaviour of the generic functions frame-standard-output,
frame-standard-input, frame-query-io, frame-error-output and
frame-pointer-documentation-output are altered by this change. If
the corresponding stream will be rebound to its old value in the
frame, the methods defined on standard-application-frame for these
generic functions will return nil rather than a stream.
5. rfe4072. On Unix, more of the scrollbar functionality defined in
the CLIM spec is now supported, and the values of scrollbars have
much finer quantisation, which allows scrolling panes with very
many lines accurately.
:scroll-to-bottom-callback [scroll-bar initarg]
-- specify a callback that is called on scroll to bottom. The
callback should be a function of one argument, the scrollbar
(scroll-bar-scroll-to-bottom-callback <scroll-bar>) [generic function]
-- return the callback called when scrolling to bottom, or NIL if
none is defined. This corresponds to the value of the
:scroll-to-bottom-callback initarg.
(scroll-to-bottom-callback <scroll-bar> <client> <gadget-id>
<value>) [generic function]
-- callback function called when the scrollbar scrolls to bottom.
Similar sets of initargs and functions exist for
...to-top... -- scroll to top
...down-line... -- scroll down single line
...up-line... -- scroll up single line
...down-page... -- scroll down page
...up-page... -- scroll up page.
Note the behaviour of these functions is that, for instance, the
default method on scroll-to-bottom-callback will call the value of
(scroll-bar-scroll-to-bottom-callback <scrollbar>) on the scrollbar
if it is non-NIL.
On Windows the names exist but the functions are not called.
...@@ -16,7 +16,7 @@ ...@@ -16,7 +16,7 @@
;; Commercial Software developed at private expense as specified in ;; Commercial Software developed at private expense as specified in
;; DOD FAR Supplement 52.227-7013 (c) (1) (ii), as applicable. ;; DOD FAR Supplement 52.227-7013 (c) (1) (ii), as applicable.
;; ;;
;; $Id: packages.lisp,v 1.103 2000/07/06 20:46:02 layer Exp $ ;; $Id: packages.lisp,v 1.104 2000/07/06 20:49:37 layer Exp $
(in-package :common-lisp-user) (in-package :common-lisp-user)
...@@ -3308,7 +3308,7 @@ ...@@ -3308,7 +3308,7 @@
(cl:defvar *clim-major-version* 2) (cl:defvar *clim-major-version* 2)
(cl:defvar *clim-minor-version* 2) (cl:defvar *clim-minor-version* 2)
(cl:defvar *clim-generation-version* 2) (cl:defvar *clim-generation-version* 2)
(cl:defvar *clim-build-version* 18) (cl:defvar *clim-build-version* 19)
(cl:defparameter *clim-version* (cl:defparameter *clim-version*
(cl:format () "~d.~d.~d.~a" (cl:format () "~d.~d.~d.~a"
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment