- mcclim-devel - mailman3.common-lisp.net

[mcclim-devel] McCLIM 2.0 in 2008
by Troels Henriksen 30 Jan '08

30 Jan '08

So, McCLIM is already pretty old, and while I can't claim to have worked on it for more than a year and a half, I feel like I have a pretty good grasp of what it does, and how well it does it. Perhaps we should start wondering about releasing a "stable" McCLIM, that is, one that is feature complete (with relation to the CLIM spec) and more tested than out usual releases. I'm not saying we should slap a stable version number on the 0.9.6 release, just that I think it would be a good, and achievable, goal to release a stable version this year. What would need to be done to make this happen? Here's a preliminary list, if you feel it is incomplete, please add to it: * First, implement all the reasonable parts of the CLIM 2 spec, with the exception of things that are unimplementable, underspecified or just really hard to do properly (fully generic designs, alpha blending and all, falls in this last category, I think). Things that are underspecified should probably be implemented by looking at later CLIM specs, as well as classic CLIM behaviour. We are already mostly there. Does anyone know exactly what is missing? * Create a better test suite, at least something that can actually be called a test suite, though it may not fully test the entire system. This is probably a must if a "stable" release is to have any meaning at all, and fortunately, many of the tricky aspects of CLIM do not actually need a graphical interface, and the Null backend may suffice for the majority of the rest. I would prefer using an actual regression testing library (such as FiveAM) compared to files filled with asserts. * Select a number of extensions (not necessarily all of them) and make sure they're as well tested as the core CLIM functionality. These extensions should also be documented. * Have at least one backend without major flaws. I think the CLX backend is good enough, apart from some suboptimal performance. Gtkairo may not reach that level this year. * Insert docstrings for all exported functionality. If I recall correctly, Robert Strandh spoke with one of the original CLIM spec authors and was told not to worry about copyright issues, so we could just copy from there. The following is what is NOT necessary for a McCLIM 2.0 release: * Support for LispWorks and Allegro CLIM extensions. * Fully working and tested extensions. We only need to select those that are feasible to bring up to a sufficiently high level of stability and performance (does this leave out mcclim-freetype?). Of course, we should document which ones. * More than one fully working backend. * Documentation covering CLIM itself. The spec will have to do for now. Finally: when you saw this email, none of you thought "I wonder what insightful observations this thoughtful engineer has about a stable release", you thought "why is this crazy hacker talking about a 2.0 version, we're still pre-1.0!". My idea is to make the McCLIM version number follow the CLIM spec version number. While this is not terribly useful for a 2.0 release in isolation, it makes it easier to design similar 2.1 and 2.2 releases for the LispWorks and Allegro extensions, as well as the hypothetical future CLIM 2.3 spec that will fix all the ambiguous and underspecified details and bring CLIM into the 90's. What are your thoughts? -- \ Troels /\ Henriksen - who's quite sleep-deprived

7 15

[mcclim-devel] Building on OpenMCL
by David Lichteblau 30 Jan '08

30 Jan '08

Hi, McCLIM currently has trouble building on OpenMCL. Do you have a fix for that? Thanks, David ---------------------------------------------------------------------- No MAKE-LOAD-FORM method is defined for #S(DREI:FACE :INK #.CLIM:+FOREGROUND-INK+ :STYLE #<STANDARD-TEXT-STYLE NIL :ROMAN NIL>) [Condition of type SIMPLE-ERROR] Restarts: 0: [RETRY-COMPILE-FILE] Retry compiling #P"/home/david/clbuild/source/mcclim/Drei/drawing-options.lisp" 1: [SKIP-COMPILE-FILE] Skip compiling #P"/home/david/clbuild/source/mcclim/Drei/drawing-options.lisp" 2: [RETRY] Retry performing #<COMPILE-OP NIL #x3000410B90ED> on #<CL-SOURCE-FILE "drawing-options" #x30004105FDED>. 3: [ACCEPT] Continue, treating #<COMPILE-OP NIL #x3000410B90ED> on #<CL-SOURCE-FILE "drawing-options" #x30004105FDED> as having been successful. 4: [ABORT] Abort SLIME compilation. 5: [ABORT] Return to SLIME's top level. 6: [ABORT-BREAK] Reset this process 7: [ABORT] Kill this process Backtrace: 0: (CCL::NO-MAKE-LOAD-FORM-FOR #S(DREI:FACE :INK #.CLIM:+FOREGROUND-INK+ :STYLE #<STANDARD-TEXT-STYLE NIL :ROMAN NIL>)) 1: (CCL::FASL-SCAN-USER-FORM #S(DREI:FACE :INK #.CLIM:+FOREGROUND-INK+ :STYLE #<STANDARD-TEXT-STYLE NIL :ROMAN NIL>)) 2: (CCL::FASL-SCAN-CLFUN #<Anonymous Function #x300041F0E08F>) 3: (CCL::FASL-SCAN '((23 81) (47 "home:clbuild;source;mcclim;Drei;drawing-options.lisp.newest") (4 #<Anonymous Function #x300041EF043F>) (4 #<Anonymous Function #x300041EE843F>) (4 #<Anonymous Function #x300041EE170F>) (4 #<Anonymous Function #x300041F1A9EF>) (4 #<Anonymous Function #x300041F13D7F>) (4 #<Anonymous Function #x300041F0E08F>) (4 #<Anonymous Function #x300041F0839F>) ..)))) 4: (CCL::FASL-SCAN-FORMS-AND-DUMP-FILE '((23 81) (47 "home:clbuild;source;mcclim;Drei;drawing-options.lisp.newest") (4 #<Anonymous Function #x300041EF043F>) (4 #<Anonymous Function #x300041EE843F>) (4 #<Anonymous Function #x300041EE170F>) (4 #<Anonymous Function #x300041F1A9EF>) (4 #<Anonymous Function #x300041F13D7F>) (4 #<Anonymous Function #x300041F0E08F>) (4 #<Anonymous Function #x300041F0839F>) ..))) "/home/david/clbuild/source/mcclim/Drei/drawing-options.lx64fsl" #<LEXICAL-ENVIRONMENT #x300041EF663D>) 5: (CCL::%COMPILE-FILE "/home/david/clbuild/source/mcclim/Drei/drawing-options.lisp" "/home/david/clbuild/source/mcclim/Drei/drawing-options.lx64fsl" 'NIL 'NIL 'NIL 'NIL 'T 'T 'NIL 'NIL #<BACKEND LINUXX8664 #x3000407892CD> ':DEFAULT) 6: (COMPILE-FILE #P"/home/david/clbuild/source/mcclim/Drei/drawing-options.lisp" ':OUTPUT-FILE #P"/home/david/clbuild/source/mcclim/Drei/drawing-options.lx64fsl" ':VERBOSE 'NIL ':PRINT 'NIL ':LOAD 'NIL ':FEATURES 'NIL ':TARGET ':LINUXX8664 ':SAVE-LOCAL-SYMBOLS 'NIL ':SAVE-DOC-STRINGS 'T ':SAVE-DEFINITIONS 'T ':EXTERNAL-FORMAT 'NIL ':FORCE ':DEFAULT) 7: (#<STANDARD-METHOD ASDF:PERFORM (ASDF:COMPILE-OP ASDF:CL-SOURCE-FILE)> #<COMPILE-OP NIL #x3000410B90ED> #<CL-SOURCE-FILE "drawing-options" #x30004105FDED>) 8: (CCL::%%BEFORE-AND-AFTER-COMBINED-METHOD-DCODE '(NIL #<STANDARD-METHOD ASDF:PERFORM (ASDF:COMPILE-OP ASDF:CL-SOURCE-FILE)> . 5864064454365)) 9: (CCL::%CALL-NEXT-METHOD '(NIL #<STANDARD-METHOD ASDF:PERFORM (ASDF:COMPILE-OP ASDF:CL-SOURCE-FILE)> . 5864064454365)) 10: (#<STANDARD-METHOD ASDF:PERFORM :AROUND (T T)> '(NIL #<STANDARD-METHOD ASDF:PERFORM (ASDF:COMPILE-OP ASDF:CL-SOURCE-FILE)> . 5864064454365) #<COMPILE-OP NIL #x3000410B90ED>) 11: (CCL::%%STANDARD-COMBINED-METHOD-DCODE '(#<STANDARD-METHOD ASDF:PERFORM :AROUND (T T)> (#<STANDARD-METHOD ASDF:PERFORM :BEFORE #>) (#<STANDARD-METHOD ASDF:PERFORM :AFTER #>) #<STANDARD-METHOD ASDF:PERFORM (ASDF:COMPILE-OP ASDF:CL-SOURCE-FILE)>) 5864064454365) 12: (ASDF:OPERATE 'ASDF:LOAD-OP "mcclim") 13: (#<Anonymous Function #x300040FE12BF>) 14: (#<Anonymous Function #x300040E70BFF> #<COMPILED-LEXICAL-CLOSURE #x3000410176FF>) 15: (SWANK-BACKEND:CALL-WITH-COMPILATION-HOOKS #<COMPILED-LEXICAL-CLOSURE #x3000410176FF>) 16: (SWANK::OPERATE-ON-SYSTEM "mcclim" "LOAD-OP") 17: (#<Anonymous Function #x300040FE1A5F>) 18: (SWANK::MEASURE-TIME-INTERVAL #<COMPILED-LEXICAL-CLOSURE #x30004101774F>) 19: (SWANK::SWANK-COMPILER #<COMPILED-LEXICAL-CLOSURE #x30004101774F>) 20: (SWANK:OPERATE-ON-SYSTEM-FOR-EMACS "mcclim" "LOAD-OP") 21: (CCL::CALL-CHECK-REGS 'SWANK:OPERATE-ON-SYSTEM-FOR-EMACS "mcclim" "LOAD-OP") 22: (#<Anonymous Function #x300040F344EF>) 23: (#<Anonymous Function #x300040E0C16F> #<Compiled-function SWANK:SWANK-DEBUGGER-HOOK #x300040F2BF6F> #<COMPILED-LEXICAL-CLOSURE #x3000410177AF>) 24: (SWANK-BACKEND:CALL-WITH-DEBUGGER-HOOK #<Compiled-function SWANK:SWANK-DEBUGGER-HOOK #x300040F2BF6F> #<COMPILED-LEXICAL-CLOSURE #x3000410177AF>) 25: (SWANK::EVAL-FOR-EMACS '(SWANK:OPERATE-ON-SYSTEM-FOR-EMACS "mcclim" "LOAD-OP") "COMMON-LISP-USER" 12) 26: (FUNCALL 'SWANK::EVAL-FOR-EMACS '(SWANK:OPERATE-ON-SYSTEM-FOR-EMACS "mcclim" "LOAD-OP") "COMMON-LISP-USER" 12) 27: (SWANK::READ-FROM-EMACS) 28: (#<Anonymous Function #x300040EBA10F>) 29: (#<Anonymous Function #x300040E0C16F> #<Compiled-function SWANK:SWANK-DEBUGGER-HOOK #x300040F2BF6F> #<Anonymous Function #x300040EBA10F>) 30: (SWANK-BACKEND:CALL-WITH-DEBUGGER-HOOK #<Compiled-function SWANK:SWANK-DEBUGGER-HOOK #x300040F2BF6F> #<Anonymous Function #x300040EBA10F>) 31: (#<Anonymous Function #x300040EA63AF>) 32: (SWANK::CALL-WITH-REDIRECTED-IO #<CONNECTION #x300040F7163D> #<COMPILED-LEXICAL-CLOSURE #x3000410177FF>) 33: (SWANK::MAYBE-CALL-WITH-IO-REDIRECTION #<CONNECTION #x300040F7163D> #<COMPILED-LEXICAL-CLOSURE #x3000410177FF>) 34: (SWANK::CALL-WITH-CONNECTION #<CONNECTION #x300040F7163D> #<Anonymous Function #x300040EBA10F>) 35: (SWANK::HANDLE-REQUEST #<CONNECTION #x300040F7163D>) 36: (SWANK::REPL-LOOP #<CONNECTION #x300040F7163D>) 37: (#<Anonymous Function #x300040EB4DFF>) 38: (SWANK::CALL-WITH-BINDINGS 'NIL #<COMPILED-LEXICAL-CLOSURE #x300040F882DF>) 39: (#<Anonymous Function #x300040EB4E7F>) 40: (CCL::RUN-PROCESS-INITIAL-FORM #<PROCESS repl-thread(5) [Active] #x300040F7312D> '(#<COMPILED-LEXICAL-CLOSURE #x300040F7309F>)) 41: (#<Anonymous Function #x30004045DE7F> #<PROCESS repl-thread(5) [Active] #x300040F7312D> '(#<COMPILED-LEXICAL-CLOSURE #x300040F7309F>)) 42: (#<Anonymous Function #x30004043CF1F>)

2 5

[mcclim-devel] ESA-UTILS:VALUES-MAX-MIN
by David Lichteblau 30 Jan '08

30 Jan '08

To whom it may concern: compilation aborted because of fatal error: ; READ failure in COMPILE-FILE: ; SB-INT:SIMPLE-READER-PACKAGE-ERROR at 46165 (line 1135, column 49) on #<SB-SYS:FD-STREAM for "file /home/david/clbuild/source/climacs/prolog-syntax.lisp" {1002556561}>: ; Symbol "VALUES-MAX-MIN" not found in the ESA-UTILS package.

2 2

[mcclim-devel] mcclim-images.asd
by David Lichteblau 29 Jan '08

29 Jan '08

Hi, can you please move mcclim-images into its own system file mcclim.asd, and mcclim-images-FOO into their own files mcclim-images-FOO.asd? Right now, it's not possible to load the clim-listener system without having loaded the mcclim system manually before. (It would be possible to change the order of the dependencies in clim-listener.asd so that this problem is avoided, but ISTR that older versions of ASDF expected the opposite order, and when we discussed this on #lisp, the consensus was that any system that user code would depend on needs its own .asd file.) Thanks, David

3 3

[mcclim-devel] mcclim debugger patch
by Cyrus Harmon 27 Jan '08

27 Jan '08

the following patch fixes the mcclim debugger to work with swank. The condition-references slot is now gone, although there is some remnant of this in the 'compiler-condition and in the condition-extras. I think the right thing to do is to remove the slot from 'debugger-info, BICBW. Thanks, Cyrus

1 0

[mcclim-devel] Bugs
by Daniel Herring 23 Jan '08

23 Jan '08

Hi, I've just started playing with McCLIM. Below are some issues for McCLIM CVS on SBCL 1.0.12.17. Please treat this as a bug report or tell me what I'm doing wrong (e.g. if CVS is known to be unstable). Thanks, Daniel (clim-demo::run-test 'clim-demo::demodemo) CLIM-Fig: Selecting "ellipse" and then clicking on the canvas results in "Attempt to invert the probably singular transformation #<CLIM-INTERNALS::STANDARD-HAIRY-TRANSFORMATION 0 0 0 0 266 185>. [Condition of type CLIM:SINGULAR-TRANSFORMATION]" Bezier curves are very difficult to draw (lots of errors). Calculator: The buttons frequently don't respond. Also, most calculators start a new number when a number is entered following; this calculator appends to the current result. For example, the keys "3*4=5" generally show "3", "4", "7", and "5". But I'm seeing "3", "4", "7", and "75". Draggable Graph: If I resize the window (usually a single maximize works) and then click a node, it disappears and SBCL says "There is no applicable method for the generic function #<STANDARD-GENERIC-FUNCTION CLIM:SHEET-NATIVE-TRANSFORMATION (6)> when called with arguments (NIL). [Condition of type SIMPLE-ERROR]" The node disappears for good (can't select it) even though its connections refresh when connected nodes are dragged. Only the first dragged node after the resize is affected (unless I select several nodes before acknowledging the error; then all selected nodes disappear). Misc tests: Empty Records 3 The circle is in the same location as for Empty Records 1 & 2. The bottom and right of the box are close to the circle as before. However, the top left corner is now 2 diameters from the circle.

3 5

Re: [mcclim-devel] how to do pixel-by-pixel output?
by Nikodemus Siivola 23 Jan '08

23 Jan '08

On 1/23/08, Andy Hefner <ahefner(a)gmail.com> wrote: > On Jan 22, 2008 6:28 PM, Nikodemus Siivola <nikodemus(a)random-state.net> wrote: > > > Below is what I have now, and it sucks royally: DRAW-PIXEL* calls take ~8 > > seconds on a 400*600 region, and everything else takes < 1 second... (on CLX > > backend.) > > Switching from draw-point* to medium-draw-point* with (setf > medium-ink) is likely to be a little faster, but still pretty > hopeless. > > > What I would like (and what the above tries to do, but fails) is to get hold of > > a some sort of object onto which I can efficiently blast colors pixel > > by pixel, and then update the screen using a convenient-for-me interval. > > The existing McCLIM image facilities can (I presume) efficiently > transfer RGB images, but not in the incremental manner you require. > Something analogous to xlib:put-image or xlib:put-raw-image seems > ideal for filling stripes of your pixmap. As a quick and dirty > solution, I have some old code at > http://vintage-digital.com/hefner/mcclim/medium-draw-pixels.lisp which > is a thin wrapper around xlib:put-image and will (probably) work with > your pixmap, taking a two-dimensional '(unsigned-byte 32) array of > packed RGB values as input. X11 being what it is, you might have to > twiddle the :bits-per-pixel (some machines want 32, others 24). Perfect -- this runs in < 1 second. (defun render-scene (scene sheet) (let* ((region (sheet-region sheet)) (width (bounding-rectangle-width region)) (height (bounding-rectangle-height region)) (end (- width 1)) (image (make-array (list 1 width) :element-type '(unsigned-byte 32)))) (raylisp::render scene (raylisp::scene-default-camera scene) width height (lambda (color x y) (declare (type (simple-array single-float (3)) color) (type fixnum x y)) ;; FIXME: Gamma... (let ((r (floor (* 255 (aref color 0)))) (g (floor (* 255 (aref color 1)))) (b (floor (* 255 (aref color 2))))) (setf (aref image 0 x) (logior (ash r 16) (ash g 8) b)) (when (= x end) (with-sheet-medium (medium sheet) (medium-draw-pixels* medium image 0 y))))) :normalize-camera t))) Apropos: while figuring out how use your code I came across RGB-IMAGE-DESIGN, and managed to make it work for usable well as well -- code below runs in < 2 seconds. (defun render-scene (scene medium) (let* ((region (sheet-region medium)) (width (bounding-rectangle-width region)) (height (bounding-rectangle-height region)) (end (- width 1)) (data (make-array (list 1 width) :element-type '(unsigned-byte 32)))) (raylisp::render scene (raylisp::scene-default-camera scene) width height (lambda (color x y) (declare (type (simple-array single-float (3)) color) (type fixnum x y)) ;; FIXME: Gamma... (let ((r (floor (* 255 (aref color 0)))) (g (floor (* 255 (aref color 1)))) (b (floor (* 255 (aref color 2))))) (setf (aref data 0 x) (logior (ash b 16) (ash g 8) r)) (when (= x end) (let (design) (unwind-protect (progn (setf design (climi::make-rgb-image-design (make-instance 'climi::rgb-image :width width :height 1 :data data))) (draw-design medium design :y y)) (climi::free-image-design design)))))) :normalize-camera t))) I can live with CLIMI:: prefixes, etc... but is either of these expected to land in CLIM-EXTENSIONS anytime soon? > If you can live without the incremental display, you could display the > entire image using make-image and draw-image. ...unfortunately incremental display is the only real of having a GUI on this thing -- it doesn't matter for images that render fast, but ones that take longer I want to see in progress, so I can abort if there's something wrong without waiting the whole thing out.

1 0

[mcclim-devel] how to do pixel-by-pixel output?
by Nikodemus Siivola 22 Jan '08

22 Jan '08

I realize this may be a case of "Doctor, it hurts when I do this..", but I'm hoping there is some medicine to be had. I'm displaying images from my raytracer on a canvas as they are being rendered. I don't require per pixel updating -- any buffering scheme that updates the screen "every once in a while" is fine by me. Below is what I have now, and it sucks royally: DRAW-PIXEL* calls take ~8 seconds on a 400*600 region, and everything else takes < 1 second... (on CLX backend.) (defun render-scene (scene medium) (let* ((pixmap nil) (region (sheet-region medium)) (width (bounding-rectangle-width region)) (height (bounding-rectangle-height region)) (end (- width 1))) (unwind-protect (progn (setf pixmap (allocate-pixmap medium width height)) (raylisp::render scene (raylisp::scene-default-camera scene) width height (lambda (color x y) (declare (type (simple-array single-float (3)) color) (type fixnum x y)) (progn (draw-point* pixmap x y :ink (make-rgb-color (aref color 0) (aref color 1) (aref color 2))) (when (= x end) (copy-from-pixmap pixmap 0 y width 1 medium 0 y)))) :normalize-camera t)) (when pixmap (deallocate-pixmap pixmap))))) What I would like (and what the above tries to do, but fails) is to get hold of a some sort of object onto which I can efficiently blast colors pixel by pixel, and then update the screen using a convenient-for-me interval. Cheers, -- Nikodemus

1 0

[mcclim-devel] [PATCH] fix undefined-variable warnings in commands.lisp
by Nikodemus Siivola 22 Jan '08

22 Jan '08

...for once, these are mostly really undefined variables, left over from some refactoring or another... --- commands.lisp | 16 ++++++++-------- frames.lisp | 7 ++++--- 2 files changed, 12 insertions(+), 11 deletions(-) diff --git a/commands.lisp b/commands.lisp index 66db758..5d163a9 100644 --- a/commands.lisp +++ b/commands.lisp @@ -332,7 +332,7 @@ (command-name-from-symbol command-name)) (errorp (error 'command-not-accessible :command-table-name - (command-table-designator-as-name table))) + (command-table-designator-as-name command-table))) (t nil))) (defun find-menu-item (menu-name command-table &key (errorp t)) @@ -436,7 +436,7 @@ (in-table (position gesture keystroke-accelerators :test #'equal))) (when (and in-table errorp) (error 'command-already-present :command-table-name - (command-table-designator-as-name table))) + (command-table-designator-as-name command-table))) (if in-table (setf (nth in-table keystroke-items) item) (progn @@ -474,7 +474,7 @@ (setf (cdr items-tail) (cddr items-tail)))) (when errorp (error 'command-not-present :command-table-name - (command-table-designator-as-name table))))))) + (command-table-designator-as-name command-table))))))) nil) (defun map-over-command-table-keystrokes (function command-table) @@ -499,7 +499,7 @@ do (return-from find-keystroke-item (values item command-table))) (if errorp (error 'command-not-present :command-table-name - (command-table-designator-as-name table)) + (command-table-designator-as-name command-table)) nil))) (defun lookup-keystroke-item (gesture command-table @@ -522,11 +522,11 @@ (values sub-item sub-command-table)))))) command-table)))) -(defun partial-command-from-name (command-name) +(defun partial-command-from-name (command-name command-table) (let ((parser (gethash command-name *command-parser-table*))) (if (null parser) (error 'command-not-present :command-table-name - (command-table-designator-as-name table)) + (command-table-designator-as-name command-table)) (cons command-name (mapcar #'(lambda (foo) (declare (ignore foo)) @@ -549,7 +549,7 @@ (if item (let* ((value (command-menu-item-value item)) (command (case (command-menu-item-type item) - (:command + (:command value) (:function (funcall value gesture numeric-arg)) @@ -558,7 +558,7 @@ (if command ; Return a literal command, or create a partial command from a command-name (substitute-numeric-argument-marker (if (symbolp command) - (partial-command-from-name command) + (partial-command-from-name command command-table) command) numeric-arg) gesture)) diff --git a/frames.lisp b/frames.lisp index 92376d3..ce7a551 100644 --- a/frames.lisp +++ b/frames.lisp @@ -521,13 +521,14 @@ documentation produced by presentations.") (object) (call-next-method) (menu-item - (let ((command (command-menu-item-value object))) + (let ((command (command-menu-item-value object)) + (table (frame-command-table frame))) (unless (listp command) - (setq command (partial-command-from-name command))) + (setq command (partial-command-from-name command table))) (if (and (typep stream 'interactor-pane) (partial-command-p command)) (command-line-read-remaining-arguments-for-partial-command - (frame-command-table frame) stream command 0) + table stream command 0) command))))) (defmethod read-frame-command ((frame application-frame) -- 1.5.3.1-dirty

2 1

[mcclim-devel] [PATCH] one more undefined variable
by Nikodemus Siivola 21 Jan '08

21 Jan '08

* Looks like a simple typo. --- recording.lisp | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/recording.lisp b/recording.lisp index b113b1c..8bb234a 100644 --- a/recording.lisp +++ b/recording.lisp @@ -1730,7 +1730,7 @@ were added." (:bottom (incf top (- point-y descent)) (incf bottom (- point-y descent))) (:center (incf top (+ point-y (ceiling (- ascent descent) 2))) - (incf bottom (+ point-xy (ceiling (- ascent descent) 2))))) + (incf bottom (+ point-y (ceiling (- ascent descent) 2))))) (values left top right bottom)))) (defmethod* (setf output-record-position) :around -- 1.5.3.1-dirty

1 0