mcclim-devel

mcclim-devel@common-lisp.net

820 discussions

make-translator-fun
by Paul Werkowski 13 May '21

13 May '21

(defun make-translator-fun (args body) (cond ((null args) (warn "OBJECT parameter is obligatory (adding ignored parameter)") (let ((object-arg (gensym "OBJECT-ARG"))) `(lambda (,object-arg &key &allow-other-keys) (declare (ignore ,object-arg)) ,@body))) (t `(lambda (,(car args) &key ,@(cdr args) &allow-other-keys) (declare (ignorable ,(car args))) ,@body)))) I guess the above does the right thing if ARGS is NIL but won't catch the case of ARGS incorrectly given as, for instance, (x y window) instead of (object x y window). Paul

3 3

define-presentation-to-command-translator
by Paul Werkowski 13 May '21

13 May '21

Trying to run McCLIM on windows-10/LispWorks 64-bit. This issue regards define-presentation-to-command-translator. The marked lines below show the problem. Apparently the McCLIM code resulted in replacing the DEV-X argument I wanted with a DEVICE-EVENT object I did not want. I then had to use a non exported function from clim-internals to retrieve the missing value. The &rest arg I put in is NIL in both cases. I have not figured out how that happened. (defun %set-a-cursor #+clim-2.0 (chart cursor dev-x dev-y pane &rest stuff) ;<<<< #+mcclim (chart cursor event dev-y pane &rest stuff) ;<<<< (let* (#+mcclim (dev-x (climi::device-event-x event)) (x (untransform-position (medium-transformation pane) dev-x dev-y))) (with-slots (lcursor rcursor) chart (let ((newx (ecase cursor (rcursor (max (x-cursor-position lcursor) (ceiling x))) (lcursor (min (x-cursor-position rcursor) (floor x)))))) ;; args to com-set-cursor (list (slot-value chart cursor) newx pane))))) (define-presentation-to-command-translator xlate-set-rcursor (clim:blank-area com-set-cursor plotter :documentation "Set Right Cursor" :gesture :menu :tester ((object window) (declare (ignore object)) (typep window 'basic-chart-pane))) (x y window) (%set-a-cursor (chart-pane-chart window) 'rcursor x y window))

2 1

scigraph suffering from bitrot?
by John Morrison 03 May '21

03 May '21

Hi; Before I strap on my hip-waders, is my intuition that climi::pixmap type has been refactored correct? Please advise If so, that's where I'll start looking - and if you suggest a backend-independent type I should be using, I will be most grateful. I also checked scigraph-evo, and its demos fail in precisely the same way as bundled Apps/Scigraph's demos. Thanks in advance for pointing the way, -jm p.s., I was looking for a real pan-and-zoom XY canvas - if anybody has better suggestions, I'm all ears.

1 0

default-icons.lisp
by Paul Werkowski 29 Apr '21

29 Apr '21

(make-pathname :directory '(:relative "data/icons") "data/icons" is not a valid directory component unless the underlying OS allows "/" character in names. At least on Windows is should be '(:relative "data" "icons"). Paul

2 1

Current McCLIM does not load
by zbyszek 29 Apr '21

29 Apr '21

This is the message, both from quickload, and loading version taken from github debugger invoked on a ASDF/FIND-COMPONENT:MISSING-COMPONENT in thread #<THREAD "main thread" RUNNING {10005605B3}>: Component "clim" not found Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL. restarts (invokable by number or by possibly-abbreviated name): 0: [RETRY ] Retry ASDF operation. 1: [CLEAR-CONFIGURATION-AND-RETRY] Retry ASDF operation after resetting the configuration. 2: Retry ASDF operation. 3: Retry ASDF operation after resetting the configuration. 4: [ABORT ] Give up on "clim" 5: Give up on "mcclim" 6: Exit debugger, returning to top level. ((:METHOD ASDF/OPERATE:OPERATE (SYMBOL T)) ASDF/LISP-ACTION:LOAD-OP "clim" :VERBOSE NIL) [fast-method] error finding frame source: Bogus form-number: the source file has probably changed too much to cope with. source: NIL 0] What is wrong with it? Best regards, Zbyszek Jurkiewicz

2 1

Regression in compose-xx-with-transformation
by Paul Werkowski 23 Mar '21

23 Mar '21

A recent change in master branch seems to have reversed the argument order in the subject definitions. I've only checked compose-scaling-with-transformation which is again wrong causing my graphics to be written way off screen. Paul

2 3

default-icons.lisp
by Paul Werkowski 17 Jan '21

17 Jan '21

Lispworks/Windows uses :host for windows drive letter. ----------------------------------- @@ -3,10 +3,11 @@ (flet ((load-icon (name) (let* ((file-pathname #.(or *compile-file-pathname* *load-pathname*)) (icon-pathname (merge-pathnames (make-pathname :directory '(:relative "data") + :host (pathname-host file-pathname) :name name :type "png") file-pathname))) (make-pattern-from-bitmap-file icon-pathname :format :png)))) (unless *default-icon-large*

1 0

Fw: New Year's puzzle
by Daniel Kochmański 03 Jan '21

03 Jan '21

Accidently send to the sender, not the mailing list, forwarding -------- Oryginalna wiadomość -------- ‎ 3 sty 2021, 16:52, Daniel Kochmański napisał(a): > If the beer is at stake, I shall take a guess! > > When 1+ is used, we draw beyond the sheet region. That means, that *if* > we call change-space-requirements it will cause a call to resize-sheet, > which in turn will: a) clear the screen, b) call redisplay-frame-pane. > > Since the sheet region has changed, redisplaying the frame pane will > expand it even further, so we go back to the *if* part. > > Now, regarding the *if*, we have a bogus method: > > (defmethod stream-read-gesture :before ((stream clim-stream-pane) > &key timeout peek-p > input-wait-test > input-wait-handler > pointer-button-press-handler) > (declare (ignore timeout peek-p input-wait-test input-wait-handler > pointer-button-press-handler)) > (force-output stream) > ;; make the output visible > (let ((w (bounding-rectangle-max-x (stream-output-history stream))) > (h (bounding-rectangle-max-y (stream-output-history stream)))) > (unless (region-contains-region-p (sheet-region stream) > (make-rectangle* 0 0 w h)) > (change-space-requirements stream) > (finish-output stream) > (redisplay-frame-pane *application-frame* stream)))) > > that causes bogus redisplays before each gesture read, so when we move > the pointer over the window, we enter the loop: > > 1. display (and expand the output history) > 2. move the pointer > 3. change space requirements (and resize) > 4. goto 1 > > as a bonus point we have one more unnecessary redisplay. > > The fun part is that I have changes stashed that remove this method. > > All best, > Daniel > > -- > Daniel Kochmański ;; aka jackdaniel | Przemyśl, Poland > TurtleWare - Daniel Kochmański | www.turtleware.eu > > "Be the change that you wish to see in the world." - Mahatma Gandhi > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ > On Sunday, 3 January 2021 16:18, Paul Werkowski <pw(a)snoopy.qozzy.com> wrote: > >> Run the frame as is. Grab the lower corner with mouse pointer. Move it >> around. >> >> Then change either or both of the (1+ ...) forms to (1- ...) and see >> what happens. >> >> A free virtual beer to whomever solves it.

2 1

New Year's puzzle
by Paul Werkowski 03 Jan '21

03 Jan '21

Run the frame as is. Grab the lower corner with mouse pointer. Move it around. Then change either or both of the (1+ ...) forms to (1- ...) and see what happens. A free virtual beer to whomever solves it.

1 0

resize-sheet :after
by Paul Werkowski 30 Dec '20

30 Dec '20

(defmethod resize-sheet :after ((pane example-pane) width height) (window-clear pane) (redisplay-frame-pane (pane-frame pane) pane)) Apparently no developer has tried this as there are two time bombs waiting to blow up the call stack. WINDOW-CLEAR, besides writing +background-ink+ over the pane, goes on to set width and height of the sheet to zero and then call CHANGE-SPACE-REQUIREMENTS, which calls RESIZE-SHEET --> BOOM! REDISPLAY-FRAME-PANE is implemented using RESTART-CASE, which in my 35 years with CL I have never had the occasion to use. Its restartable-form manages to call itself via CALL-NEXT-METHOD (I think) which then blows the stack, which then unwinds back through various restart clauses (some which also call WINDOW-CLEAR), finally resulting in getting back to a listener prompt where one can bail out. For my use, I have re-written those two methods in a way that works for the several places where I use resize-sheet :after with good results. The attachment is one of the test cases I used to diagnose the stack blowup. It displays a green filled circle in the center of the pane. Drag a side or corner of the frame around with your pointer device to cause the resize events to occur. With those two changes my 15 year old CLIM2 plotting applications works quite well although there is still a few places where pointer motion or dragging yield strange results. One other thing, if frame startup manages to silently load the NULL port, it may take a very long time to figure out why the lisp listener is dead. 🙁 Wishing you all a great new year! Paul

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

mcclim-devel