mcclim-devel

mcclim-devel@common-lisp.net

820 discussions

clx medium-draw-text*
by Paul Werkowski 02 May '24

02 May '24

The current implementation does not handle non-default :align keywords properly except when an +identity-transformation+ is in effect. This can be fixed simply by moving the transform-position form up before the (unlesss (and (eq align-x... ) stuff as shown below. (multiple-value-bind (x y) (transform-position merged-transform x y) (unless (and (eq align-x :left) (eq align-y :baseline)) (setq x (- x (ecase align-x (:left 0) (:center (round text-width 2)) ; worst case (:right text-width)))) ; worst case (setq y (ecase align-y (:top (+ y baseline)) ; OK (:baseline y) ; OK (:center (+ y baseline (- (floor text-height 2)))) ; change (:bottom (+ y baseline (- text-height)))))) ; change (xlib:draw-glyphs mi gc (truncate (+ x 0.5)) (truncate (+ y 0.5)) string :start start :end end :translate #'translate :size 16))))))

2 2

Application-pane with only with-output-as-gadget => stack overflow
by Paul Werkowski 07 Mar '24

07 Mar '24

(in-package :clim-user) ;;; Application pane with only a ;;; WITH-OUTPUT-AS-GADGET form causes ;;; control stack overflow. (define-application-frame woag () () (:panes (application :application :scroll-bars nil :display-function #'(lambda (frame pane) (declare (ignore frame)) ;; uncomment to avoid overflow ;;(format pane "Hello~%") ; @@@ (with-output-as-gadget (pane) (with-radio-box (:orientation :horizontal) "1" "2" "3"))) ))) (find-application-frame 'woag :left 900 :top 200)

1 0

McCLIM 0.9.8 Yule
by Daniel Kochmański 27 Dec '23

27 Dec '23

Dear All, half a decade later and here we are - a new release: https://mcclim.common-lisp.dev/posts/McCLIM-098-Yule-release.html Happy New Year, 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

1 0

Pan and Zoom
by Robert Krug 17 Sep '23

17 Sep '23

Greetings,Many thanks for all your work on McClim. I have been enjoying using it while trying to work my way through Tilings and Patterns by Grunbaum and Shepard.I think I have gotten a workable approach to panning and zooming. Any comments or suggestions would be greatly appreciated, but my main purpose in posting this rather long email is so that future users might save themselves some work. Thanks again.Robert;;; This is a first attempt at implementing panning and zooming in;;; McClim. It mostly works, but after a few (say 10) zooming;;; operations (in or out), the displayed region is not correct ---;;; subsequent panning operations can leave a part of the window;;; unpainted. This may be because of the accumulating inacuracy;;; inherent in repeated floating-point operations.(defpackage #:pan-and-zoom-1 (:use #:clim-lisp #:clim))(in-package #:pan-and-zoom-1);;; This class will be our model for the infinite Euclidean plane.;;; N.B. I do not understand the McClim pane hierarchy. The below may;;; not behave correctly if plane inherits from classes of panes other;;; than basic-pane. In particular, application-pane did odd things.(defclass plane (standard-extended-input-stream basic-pane) ());;; Draw a bunch of squares, so that we can examine the effect of;;; panning and zooming.(defmethod handle-repaint ((plane plane) region) (declare (ignore region)) (window-clear plane) (dotimes (i 40) (dotimes (j 40) (let ((c-x (- (* i 40) 800)) (c-y (- (* j 40) 800))) (draw-polygon* plane `(,c-x ,c-y ,(+ c-x 40) ,c-y ,(+ c-x 40) ,(+ c-y 40) ,c-x ,(+ c-y 40)) :filled 'NIL :line-thickness 2 :ink +black+) (draw-text* plane (format nil "~A, ~A" i j) (+ c-x 20) (+ c-y 20) :align-x :center :align-y :center)))))(defun pan (dx dy) (let* ((plane (find-pane-named *application-frame* 'plane)) (plane-transformation (sheet-transformation plane)) (translation-transformation (make-translation-transformation dx dy)) (new-plane-transformation (compose-transformations translation-transformation plane-transformation)) (sheet-region (sheet-region plane)) ;; We transform sheets, and untransform (apply the inverse ;; transformation) to regions. I keep getting this confused. (new-sheet-region (untransform-region translation-transformation sheet-region))) (setf (sheet-transformation plane) new-plane-transformation (sheet-region plane) new-sheet-region)))(defun zoom (factor) (let* ((plane (find-pane-named *application-frame* 'plane)) (plane-transformation (sheet-transformation plane)) (scaling-transformation (make-scaling-transformation* factor factor)) (new-plane-transformation (compose-transformations scaling-transformation plane-transformation)) (sheet-region (sheet-region plane)) (new-sheet-region (untransform-region scaling-transformation sheet-region))) (setf (sheet-transformation plane) new-plane-transformation (sheet-region plane) new-sheet-region)))(define-application-frame tiling () () (:panes (plane plane :width 400 :height 400)) (:menu-bar t) (:layouts (default plane)));;; Without these next two methods (or an interactor pane), the;;; panning/zooming commands will not be executed!;;; From Franz's User Guide: You will often implement a method for;;; this generic function for an application frame, since CLIM cannot;;; always reliably determine which pane to use for *standard-input*.(defmethod frame-standard-input ((tiling tiling)) (find-pane-named tiling 'plane))(defmethod frame-standard-output ((tiling tiling)) (find-pane-named tiling 'plane))(define-tiling-command (com-quit :menu t) () (frame-exit *application-frame*))(define-tiling-command (com-pan-up :keystroke :up) () (pan 0 10))(define-tiling-command (com-pan-down :keystroke :down) () (pan 0 -10))(define-tiling-command (com-pan-right :keystroke :right) () (pan -10 0))(define-tiling-command (com-pan-left :keystroke :left) () (pan 10 0))(define-tiling-command (com-zoom-in :keystroke (:up :shift)) () (zoom 1.1))(define-tiling-command (com-zoom-out :keystroke (:down :shift)) () (zoom 0.9))(defun tiling () (flet ((run () (let ((frame (make-application-frame 'tiling))) (setq *test-frame* frame) (run-frame-top-level frame)))) (clim-sys:make-process #'run)));;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; This is a second attempt at implementing panning and zooming in;;; McClim. It works, but is a little messy.(defpackage #:pan-and-zoom-2 (:use #:clim-lisp #:clim))(in-package #:pan-and-zoom-2);;; This class will be our model for the infinite Euclidean plane.;;; We avoid the problems with pan-and-zoom-1's accumulating;;; floating-point inaccuracies by keeping track of the plane's;;; scaling and translations, and making the appropriate;;; transformations when needed. We also keep track of the "raw";;; sheet-region so that we can transform (really untransform) it;;; appropriately.;;; N.B. I do not understand the McClim pane hierarchy. The below may;;; not behave correctly if plane inherits from classes of panes other;;; than basic-pane. In particular, application-pane did odd things.(defclass plane (standard-extended-input-stream basic-pane) ((scale :initform 1 :accessor scale) (dx :initform 0 :accessor dx) (dy :initform 0 :accessor dy) (raw-sheet-region :initform 'NIL :accessor raw-sheet-region)));;; We catch sheet resize events here so that we can update the;;; raw-sheet-region. We transform it here so that when we untransform;;; it later, we get the original region back. This is needed because;;; generally we will transform sheets and untransform regions.(defmethod resize-sheet :after ((plane plane) width height) (let ((transformation (sheet-transformation plane))) (setf (raw-sheet-region plane) (transform-region transformation (sheet-region plane)))));;; Draw a bunch of squares, so that we can examine the effect of;;; panning and zooming.(defmethod handle-repaint ((plane plane) region) (declare (ignore region)) (unless (raw-sheet-region plane) ;; Set the raw-sheet-region. This is not available at the time of ;; the plane's initialization. (setf (raw-sheet-region plane) (sheet-region plane))) (window-clear plane) (dotimes (i 40) (dotimes (j 40) (let ((c-x (- (* i 40) 800)) (c-y (- (* j 40) 800))) (draw-polygon* plane `(,c-x ,c-y ,(+ c-x 40) ,c-y ,(+ c-x 40) ,(+ c-y 40) ,c-x ,(+ c-y 40)) :filled 'NIL :line-thickness 2 :ink +black+) (draw-text* plane (format nil "~A, ~A" i j) (+ c-x 20) (+ c-y 20) :align-x :center :align-y :center)))))(defun update-plane (plane) (let* ((scaling (make-scaling-transformation* (scale plane) (scale plane))) (translation (make-translation-transformation (dx plane) (dy plane))) (transformation (compose-transformations scaling translation))) (setf (sheet-transformation plane) transformation (sheet-region plane) (untransform-region transformation (raw-sheet-region plane)))))(defun pan (dx dy) (let ((plane (find-pane-named *application-frame* 'plane))) (setf (dx plane) (+ (dx plane) dx) (dy plane) (+ (dy plane) dy)) (update-plane plane)))(defun zoom (factor) (let ((plane (find-pane-named *application-frame* 'plane))) (setf (scale plane) (* factor (scale plane))) (update-plane plane)))(define-application-frame tiling () () (:panes (plane plane :width 400 :height 400)) (:menu-bar t) (:layouts (default plane)));;; Without these next two methods (or an interactor pane), the;;; panning/zooming commands will not be executed!;;; From Franz's User Guide: You will often implement a method for;;; this generic function for an application frame, since CLIM cannot;;; always reliably determine which pane to use for *standard-input*.(defmethod frame-standard-input ((tiling tiling)) (find-pane-named tiling 'plane))(defmethod frame-standard-output ((tiling tiling)) (find-pane-named tiling 'plane))(define-tiling-command (com-quit :menu t) () (frame-exit *application-frame*))(define-tiling-command (com-up :keystroke :up) () (pan 0 10))(define-tiling-command (com-down :keystroke :down) () (pan 0 -10))(define-tiling-command (com-right :keystroke :right) () (pan -10 0))(define-tiling-command (com-left :keystroke :left) () (pan 10 0))(define-tiling-command (com-zoom-in :keystroke (:up :shift)) () (zoom 1.1))(define-tiling-command (com-zoom-out :keystroke (:down :shift)) () (zoom 0.9))(defun tiling () (flet ((run () (let ((frame (make-application-frame 'tiling))) (setq *test-frame* frame) (run-frame-top-level frame)))) (clim-sys:make-process #'run)))

2 1

[repository migration]
by Daniel Kochmański 22 Mar '23

22 Mar '23

Dear All, I've wanted to do it after the upcoming release but it's months already and it doesn't seem to be much closer than before. Due to GitHub/Microsoft taking our work without proper attribution and not respecting the license (with CoPilot) we're moving the repository to a non-profit hosting Codeberg. The new home of the repository is: https://codeberg.org/McCLIM/McCLIM The repository on GitHub is archived and available so we won't break existing urls. During the discussion on our IRC channel some questions emerged: - why not gitlab.common-lisp.net? According to some users it is not very reliable - 2fa, repository limit per user, servers are down from time to time. - what good will that do? people will mirror on github anyway. It is a very sad state of affairs that we can't stand up against techno-bullies who take from us :| but not doing anything would be even worse because that would be a silent consent. (with-jokes (:ignorable t) - it learns like human so it is not a violation! yada yada yada :) - but but what about the stars? I'm afraid that our inflated ego may not survive this. ) With this humorous accent I wish you all the best and I hope to see you during upcoming ELS in Amsterdam. :) Best regards, 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

5 5

Re: mcclim: redisplay-frame-panes where application-pane contains a gadget fails
by Daniel Kochmański 12 Nov '22

12 Nov '22

Hey, the thing is that with-output-as-gadget is specified to return the gadget and not the output record containing it - that's really not useful, but that's what it is. That is the reason why you had to also manually specify the offset x0 y0 when drawing and add the bounding rectangle size. I don't know how this should be handled in LW CLIM, but McCLIM returns two values and the second value is the created output record. In other words, this will give you the desired result disregarding whether the display is incremental or not: (defun v-pane-df (frame pane) (declare (ignore frame)) (multiple-value-bind (gadget gadget-output-record) (with-output-as-gadget (pane :x 20 :y 20) (declare (ignore pane)) (make-pane 'label-pane :label "A Label" :background +green+)) (declare (ignore gadget)) (with-bounding-rectangle* (x1 y1 x2 y2) gadget-output-record (draw-rectangle* pane x1 y1 x2 y2 :ink +red+ :filled nil :line-thickness 1)))) Best regards, 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 Saturday, November 12th, 2022 at 16:03, Paul Werkowski <pw(a)snoopy.qozzy.com> wrote: > Hi Daniel, > > I wonder if you could tell me what is happening. Not a bug, I think, > because Lispworks CLIM does the same thing. > > If you still have that example I sent, change :incremental-redisplay to > T and run the program. > Note the blue border is does not surround the label but is size 100x100 > which is a default size somewhere. > > If I stuff the value of g into a global symbol (setq g g) and take the > bounding rectangle size I get the correct value. I'm wondering if the > problem is somehow related to dynamic-extent. Is there a correct way to > use the gadget dimensions that works both settings of > :incremental-redisplay? > > Thanks for any information you can share. > > Paul

1 0

Re: mcclim: redisplay-frame-panes where application-pane contains a gadget fails
by Daniel Kochmański 11 Nov '22

11 Nov '22

Hey Paul, sorry for taking so much time to respond. I'm answering your emails in batch. > [two down one to go] The issue was that (draw-rectangle* t 0 0 10 10 :filled nil) has the extent [-.5 -.5 10.5 10.5], I've explained that the line thickness when filled is nil is normally 1 (or 2 depending on the backend), so it extends beyond the rectangle dimensions in question. You've concured that LispWorks makes the bounding rectangle [0 0 11 11] (proving that they take into account the line thickness), but I wonder why they are doing that? If we draw a rectangle with line thickness 4 then the bounding rectangle is [0 0 14 14] and not [-2 -2 12 12]? Does it mean that drawing a border around the object may produce a result where the object is not in the center, because it is "too close to the edge"? Or does it mean that /after all drawing/ they move all output so it fits inside the sheet region defined (by them) as [0 0 width height]? McCLIM allows defining sheets with a region that is not aligned with 0X and 0Y, so perhaps it is their limitation of the implementation? > [follow up to previous convo] > > Please give the attached code a try. (clim-user::tryit) > Keep left clicking in the pane. Expected behavior? >From the file in question I think that you've mixed some other program after the initial output (starting from the function ~test-draw-line~). Either way the behavior I'm observing is expected. You take the sheet dimensions to draw on a sheet and then the sheet dimensions are computed based on the output (bar the fact that we seem to come beyond specified max-width - this is most likely a bug). > [with-radio-box] Thank you for the kind words. CAPI backend sounds nice. I'm working on SDL2 backend on the other hand (in parallel with other things, i.e today I've finished an initial port of ECL to emscripten, so it is possible to run CL in the web browser (see turtleware.eu/static/ecl/ecl.html, open the js console). Thanks for the code - it had an issue that "selected" toggle boxes did not have a desired background. I've implemented this feature by hooking the background directly in the local function MAKE-PANE (while still respecting the background if the programmer explicitly supplied one). See the recent commit if you are curious, here is the code for a simple test: ``` (define-application-frame with-boxes () () (:panes (app :application) (rad (with-radio-box (:background +light-blue+ :type :some-of) "Daniel" "Ma" (radio-box-current-selection "Kota") (radio-box-current-selection "bata") (make-pane :toggle-button :label "make-pane 1") (radio-box-current-selection (make-pane :toggle-button :label "make-pane 2")) (make-pane :toggle-button :label "make-pane 1" :background +light-pink+) (radio-box-current-selection (make-pane :toggle-button :label "make-pane 2" :background +light-pink+)))))) (find-application-frame 'with-boxes) ``` > [mcclim: redisplay-frame-panes where application-pane contains a gadget > fails] Thanks for the report. Notice that if we define a redisplay command, then the problem does not happen (when the command is activated) - that means that the issue is caused by the fact that we try to redisplay the frame asynchronously ``` (define-v-frame-command (com-redisplay :menu t) () (with-application-frame (frame) (redisplay-frame-panes frame))) ``` and indeed the issue is caused by the fact that the pane realizer is not bound. REDISPLAY-FRAME-PANES works fine if we bind it: ``` (let ((fm (frame-manager *frame*))) (with-look-and-feel-realization (fm *frame*) (redisplay-frame-panes *frame*))) ``` That said asynchronous access is not safe unless you either call EXECUTE-FRAME-COMMAND (safe!) and/or dispatch an event and handle it (safe and low level). I hope that this is a satisfying answer. Best regards, 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 Thursday, November 10th, 2022 at 19:38, Paul Werkowski <pw(a)snoopy.qozzy.com> wrote: > LispWorks 8.0.1 Windows: > McCLIM current source: > Example attached > > Paul > > CLIM-USER 5 > (redisplay-frame-panes frame) > > > Error: No applicable methods for #<STANDARD-GENERIC-FUNCTION MAKE-PANE-1 > 4160C3ACB4> with args (NIL #<CLIM-INTERNALS::DEFAULT-APPLICATION > > 405047874B> LABEL-PANE :LABEL "A Label" :BACKGROUND > > #<CLIM-INTERNALS::NAMED-COLOR "green">) > > 1 (continue) Call #<STANDARD-GENERIC-FUNCTION MAKE-PANE-1 4160C3ACB4> > > again > 2 Clear the output history of the pane and reattempt forceful redisplay. > 3 Clear the output history of the pane, but don't redisplay. > 4 Skip this redisplay. > 5 (abort) Return to top loop level 0. > > Type :b for backtrace or :c <option number> to proceed. > > Type :bug-form "<subject>" for a bug report template or :? for other > > options. > > CLIM-USER 6 : 1 >

1 0

updating-output issues
by Paul Werkowski 01 Feb '22

01 Feb '22

I've been revisiting a clim project from 15 years ago which was to provide clim graphics to Dan Corkhill's very nice GBBopen blackboard system. I have an initial version now working nicely on Lispworks clim-2.0 on Windows. It is close to running with McCLIM as well. I have two issues, updating-output appears to work in that the :cache-test is respected but where Lispworks clim calls clear-output-record when a displayed object moves or is deleted McCLIM does not do so. I have attached a simple demo that shows that problem. Just click right or left anywhere in the pane to move the green disk left or right to see the problem. The other issue is that redisplay-frame-pane (not used in the demo) always causes an infinite recursion that finally results in a blown stack. Part of the problem is with window-clear which in addition to using medium-clear-area, etc to clear the screen also sets window size to zero and then calls compose-space. I have an :around method that avoids that problem but the redisplay recursion persists. My workaround for that is to just call the display function directly but that does not allow updating-output to work correctly. Paul

2 3

scigraph datasets mixin behavior
by John Phillips 01 Oct '21

01 Oct '21

Hello, I have recently started trying to use the scigraph package in McClim for a simulation course I'm taking. I spent more time than I care to admit this morning trying to get a scatter plot dataset to show up -- I kept getting the graph with tick marks but no data. Finally after reading the code I found out that the hidden-datasets member of the graph-datasets-mixin object will by default initialize to be a copy of the datasets member. For example if I do something like this: (setf *my-graph* (make-instance 'graph:graph :datasets (list *my-graph-data*) :hidden-datasets nil)) And then this: (graph::hidden-datasets *my-graph*) I get: (#<GRAPH-DATA GRAPH-DATA-15>) In other words, all the datasets are hidden by default. Is this the way the class is meant to behave? If so, I feel like I must be doing something wrong in the way I'm constructing my graph -- although it does work (I manually set the hidden-datasets member to nil after construction). Is there anywhere where I can find example usages of this package? There don't seem to be scigraph examples in the Examples/ folder, the things that say 'graph' usually seem to be manual graph creations. Thanks, John

1 0

[new irc server]
by Daniel Kochmański 23 May '21

23 May '21

Hey, Due to the recent events revolving freenode IRC network I've moved the IRC channelto #clim @ libera.chat. The old channel is obsolete. Best regards, 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

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