mcclim-devel May 2009

mcclim-devel@common-lisp.net

6 participants
4 discussions

Re: [mcclim-devel] mcclim-devel Digest, Vol 39, Issue 6
by Irene DURAND 27 Mar '13

27 Mar '13

Hello, As my paste on irc lisp, did not have any answer, I turning again to this more specialized mailing list. I have this MClim problem. The application runs fine on Linux with SBCL 1.0.13, xorg-x11-server 1.3.0.0-9.fc7, a recent version of MClim. But doesn't on my Mac (Darwin PowerPC) with MacOS 10.5 (leopard), SBCL 1.0.16, cvs version of MClim, Xquartz 2.1.5 - (xorg-server 1.3.0-apple22)(2.1.5). I have tried to create the smallest as possible application where the problems occurs (attached). Just compile the file and launch mini::(start) On Linux, I have the desired behaviour: a circle blinks (red/green/red/...) on the display pane and at the bottom of the window application, the "quit" button is displayed and works. On the Mac, the circle blinks correctly but the "Quit" button never shows up. For a while the application is killable with C-c C-c (under Slime), but after a while there is no way to kill it than to stop Lisp and restart everything (even /the/ <http://www.lispworks.com/reference/HyperSpec/Body/s_the.htm> X server). Note that this application used to work on Mac OS 10.3 (Panther) with older versions of everything. I suspect the X server to behave differently from before. But now I don't see how to make the application work. This is too bad, as I usually use a similar application for my Lisp undergraduate course. If anyone has an idea, it will be welcomed. Irène (defpackage :mini (:use :clim :clim-extensions :clim-lisp)) (in-package :mini) (let ((colors (list +red+ +green+))) (setf colors (nconc colors colors)) (defun display-function (frame pane) (draw-circle* pane 10 10 10 :ink (pop colors)) (sleep 0.5) (redisplay-frame-panes frame))) (defun quit () (frame-exit *application-frame*)) (define-application-frame mini () () (:panes (display :application :display-function 'display-function :incremental-redisplay t) (quit :push-button :label "Quit" :activate-callback (lambda (x) (declare (ignore x)) (quit)))) (:layouts (defaults (vertically () display quit)))) (defun run-test (name) (loop for port in climi::*all-ports* do (destroy-port port)) (setq climi::*all-ports* nil) (let ((frame (make-application-frame name))) (run-frame-top-level frame))) (defun start () (run-test 'mini) 0) (defmethod run-frame-top-level :before ((mini mini) &key) (let* ((frame-manager (frame-manager *application-frame*)) (port (climi::frame-manager-port frame-manager)) (display (clim-clx::clx-port-display port))) (setf (xlib:display-after-function display) g#'xlib:display-force-output)))

4 4

[mcclim-devel] [PATCH] Fix copy-from-pixmap to work inside with-output-to-pixmap
by Evgeny M. Zubok 03 Jun '09

03 Jun '09

The attached patch fixes bug when I'm trying to copy pixmap to medium-var inside the body of with-output-to-pixmap macro. The explanation below. >From CLIM 2.0 (LispWorks) with-output-to-pixmap [Macro] Arguments: (medium-var medium &key width height) &body body Summary: Binds `medium-var' to a "pixmap medium" (that is, a medium that does output to a pixmap with the characteristics appropriate to the medium `medium') and then evaluates body in that context. All the output done to the medium designated by `medium-var' inside of body is drawn on the pixmap stream. The pixmap medium supports the medium output protocol, including all of the graphics functions. `width' and `height' are integers that give the dimensions of the pixmap. If they are omitted, the pixmap will be large enough to contain all the output done by body. `medium-var' must be a symbol; it is not evaluated. The returned value is a pixmap that can be drawn onto medium using copy-from-pixmap. As soon as "The pixmap medium supports the medium output protocol, including all of the graphics functions." then the copy-from-pixmap also has to work inside with-output-to-pixmap macro. I've written simple and quick example (attached) to illustrate this. In the handle-repaint method the temporary pixmap `temp-pixmap' is created with yellow background and filled circle in centre. Then `temp-pixmap' is copied with copy-from-pixmap inside with-output-to-pixmap macro into newly created `target-pixmap' and the second circle is drawn above. Finally the `target-pixmap' is copied to canvas. (copy-from-pixmap-test::run) to run the example.

2 1

[mcclim-devel] calling command from activate-callback
by Kilian Sprotte 31 May '09

31 May '09

Hi, I have a very beginners question about calling a command from a push-button. It seems that I need to call redisplay-frame-panes in the activate-callback, although this is not necessary if I invoke the command from the interactor. (button2 push-button :label "incf and call REDISPLAY-FRAME-PANES" :activate-callback (lambda (button) (declare (ignore button)) (com-incf) ;; * (redisplay-frame-panes *application-frame*))) Is an activation of a push-button not an event in the command-loop? I would be glad to know, how this is supposed to be done. Best, Kilian ================================================ My changes to the SUPERAPP: (in-package :common-lisp-user) (defpackage "APP" (:use :clim :clim-lisp) (:export "APP-MAIN")) (in-package :app) (define-application-frame superapp () ((currrent-number :initform 1 :accessor current-number)) (:pointer-documentation t) (:panes (app :application :height 400 :width 600 :display-function 'display-app) (button push-button :label "incf" :activate-callback (lambda (button) (declare (ignore button)) (com-incf))) (button2 push-button :label "incf and call REDISPLAY-FRAME-PANES" :activate-callback (lambda (button) (declare (ignore button)) (com-incf) (redisplay-frame-panes *application-frame*))) (int :interactor :height 200 :width 600)) (:layouts (default (vertically () (horizontally () +fill+ button button2 +fill+) app int)))) (defun display-app (frame pane) (let ((number (current-number frame))) (format pane "~a is ~a" number (cond ((null number) "not a number") ((oddp number) "odd") (t "even"))))) (defun app-main () (run-frame-top-level (make-application-frame 'superapp))) (define-superapp-command (com-quit :name t) () (frame-exit *application-frame*)) (define-superapp-command (com-parity :name t) ((number 'integer)) (setf (current-number *application-frame*) number)) (define-superapp-command (com-incf :name t) () (incf (current-number *application-frame*)))

2 1

[mcclim-devel] three questions
by Orm Finnendahl 06 May '09

06 May '09

Hi, still working on my specialized browser I'm starting to implement the gui part of the application. Three questions: - Can I update (redraw) a pane without activating it with the mouse? "(window-refresh pane)" doesn't actually draw unless the window gets activated in the window-manager). - How can I implement scrolling in the pane? The scroll bars are there but they don't get updated if I draw off the visible region of the pane. - Is there a straightforward way to get a reference to an output record upon creation of the output record (to store it in the object which gets presented)? I can get it by searching the list of all output records in a pane and compare it's object slot to the object, but that seems rather inefficient, especially since newly allocated output records are appended to the end of the list. Currently I'm creating the output records in a loop of "draw-line*" embedded in "(with-output-as-presentation)". Maybe I'm doing it wrong by trying to access the output records themselves. This is the idea: I want to present graphical objects and change the shape of some of them using incremental redisplay. As far as I see, this should be done by deleting the respective output record and redrawing it with the new properties. Can anybody help? Sorry if I'm missing the obvious... Thanks, Orm

3 6

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

mcclim-devel May 2009