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

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] Unportable string comparing syntax in Doc/makeimages.sh
by onixie 24 Apr '11

24 Apr '11

Hi, I think there is an unportable string comparing syntax in Doc/makeimages.sh Left: portable, Right: unportble by diff ------------------------------------------------------------- 8c8 < if [ "$1" = "-e" ]; then --- > if [ "$1" == "-e" ]; then 22c22 < if [ "$NOCREATE" = "true" ]; then --- > if [ "$NOCREATE" == "true" ]; then -------------------------------------------------------------- It has expected result in bash, but reports a syntax error (as below) in dash and ash (posix compatible shell). The syntax error reported: -------------------------------------------------------------- [: 15: ==: unexpected operator -------------------------------------------------------------- This is a bug in ubuntu because it defaults to use dash. so I think it should be fixed.

1 0

[mcclim-devel] troubles with accept-popup
by Alexander Ekart 17 Apr '11

17 Apr '11

Hello, I was just trying to test the accept-popup function in the CLIM Listener (accept-popup is defined in accepting-values.lisp which is in the McCLIM Examples directory) but I ran into trouble. Executing (clim-demo::accept-popup '(one two three four)) in the Listener and clicking 'OK' or 'Cancel' in the popup yields an error: There is no applicable method for the generic function #<STANDARD-GENERIC-FUNCTION CLIM-INTERNALS::EDITING-STREAM (1)> when called with arguments (#<CLIM-INTERNALS::AV-POP-UP-MENU-RECORD X 173/2:261/2 Y 798.5d0:822.5d0 "Choose one:" {C2B96E1}>). [Condition of type SIMPLE-ERROR] Does anybody have an idee what the problem could be? Thanks! -- GMX DSL Doppel-Flat ab 19,99 Euro/mtl.! Jetzt mit gratis Handy-Flat! http://portal.gmx.net/de/go/dsl

1 0

[mcclim-devel] Help running demos
by Collin Day 10 Apr '11

10 Apr '11

Hello, I am rather new to lisp and have been learning by reading "Practical Common Lisp" online and "Land of Lisp". One thing I was just sort of interested in was seeing how you could use lisp to make GUIs. So, I decided to try McCLIM. Anyway, I use gentoo, so I just emerged mcclim and have version 0.9.6. I am using the clisp implementation and think I have everything set up correctly. Following the instructions on the cliki, I can do the following: (asdf:oos 'asdf:load-op :mcclim) - ends with 0 errors, 74 warnings NIL - so I think that is ok. Since I am using gentoo, I didn't do the ln -s mcclim/clim-examples.asd . since I am just using the stock directories. Then I can run: (asdf:oos 'asdf:load-op :clim-examples) - ends with 0 errors, 0 warnings NIL - so that seems ok as well. The problem is when I run: (clim-demo::run-test 'clim-demo::demodemo) I get: *** - Connection failure to X11.0 server display 0: No protocol specified I have clx installed - I also ran (asdf:oos 'asdf:load-op :clx) to ensure everything was built. If I build / load the gtkairo backend: (asdf:oos 'asdf:load-op :clim-gtkairo) Then the demos appear to run. I am sure I am doing something wrong - does anyone know what it might be though? Thanks! -C

1 0

[mcclim-devel] map-over-output-records-overlapping-region
by Orm Finnendahl 02 Apr '11

02 Apr '11

Hi, reading the specs, map-over-output-records-overlapping-region should map over *all* childs of the supplied output-record which overlap the supplied region. In my application, the output-records are hierarchical with the topmost output-record covering the whole drawing area and its childs occupying parts of that and their childs again parts of the parts and so forth. When calling the function on a part of the drawing area, the macro only maps the function over the topmost output record and ignores all of its childs which also overlap the region in question. I could write a similar macro which traverses the tree and checks for overlap but I ask myself, whether the behaviour of mcclim's built-in macro is correct with regards to the specs or whether I'm doing something wrong here... -- Orm

3 2