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

Re: [mcclim-devel] mcclim on windows
by Patrik Magnusson 19 Jun '09

19 Jun '09

Hello again, Sorry but it turns out that an explicit (asdf :clim-clx) was what was missing. I didn't see the Cliki page about asdf-installing until yesterday and I was fooled by the fact that it wasn't necessary on linux. So, now it works. Both with the lispbox version of Clisp (2.37) and the small sourceforge binary (2.47). BR, /Patrik. On Fri, Jun 19, 2009 at 12:49:10AM +0400, Evgeny M. Zubok wrote: > Patrik Magnusson <magnusson.patrik(a)bredband.net> writes: > > > Could someone perhaps tell me the names of some good functions to > > trace, and so see how far the demodemo comes? > > You could try to load only clx (without mcclim) and run the examples > from clx/demo. For example, to load clx/demo/menu.lisp and run > > (xlib::just-say-lisp) > > The connection with X server is established in CLX (open-default-display > funtcion), so if you didn't see the simple menu from this example then > problem, more probably, laying in CLX-Xming interaction, not in McCLIM.

1 0

[mcclim-devel] Error: Class not yet defined: CLIM:INTERACTOR-PANE
by Cyrus Harmon 19 Jun '09

19 Jun '09

I think this is one of those errors that goes away upon zapping fasls, but I also think I've seen it before. Any clues? thanks, cyrus Class not yet defined: CLIM:INTERACTOR-PANE [Condition of type SIMPLE-TYPE-ERROR] Restarts: 0: [TRY-RECOMPILING] Recompile commands and try loading it again 1: [RETRY] Retry performing #<ASDF:LOAD-OP NIL {131F6EF1}> on #<ASDF:CL-SOURCE-FILE "commands" {12811131}>. 2: [ACCEPT] Continue, treating #<ASDF:LOAD-OP NIL {131F6EF1}> on #<ASDF:CL-SOURCE-FILE "commands" {12811131}> as having been successful. 3: [RETRY] Retry SLIME REPL evaluation request. 4: [ABORT] Return to SLIME's top level. 5: [TERMINATE-THREAD] Terminate this thread (#<THREAD "repl-thread" RUNNING {11A9D949}>) Backtrace: 0: (SB-KERNEL:FIND-CLASSOID-CELL CLIM:INTERACTOR-PANE)[:EXTERNAL] 1: (SB-FASL::FOP-FUNCALL) 2: (SB-FASL::LOAD-FASL-GROUP #<SB-SYS:FD-STREAM for "file /Users/ sly/src/lisp/mcclim/mcclim/sbcl-1.0.29.13-darwin-x86/ commands.fasl" {119F2639}>) 3: ((FLET SB-THREAD::WITH-RECURSIVE-LOCK-THUNK)) 4: ((FLET #:WITHOUT-INTERRUPTS-BODY-[CALL-WITH-RECURSIVE-LOCK]291)) 5: (SB-THREAD::CALL-WITH-RECURSIVE-LOCK ..) 6: (SB-FASL::LOAD-AS-FASL #<SB-SYS:FD-STREAM for "file /Users/sly/ src/lisp/mcclim/mcclim/sbcl-1.0.29.13-darwin-x86/ commands.fasl" {119F2639}> NIL #<unavailable argument>) 7: ((FLET SB-FASL::LOAD-STREAM) #<SB-SYS:FD-STREAM for "file /Users/ sly/src/lisp/mcclim/mcclim/sbcl-1.0.29.13-darwin-x86/ commands.fasl" {119F2639}>) 8: (LOAD #P"/Users/sly/src/lisp/mcclim/mcclim/sbcl-1.0.29.13-darwin- x86/commands.fasl")[:EXTERNAL] 9: ((SB-PCL::FAST-METHOD ASDF:PERFORM (ASDF:LOAD-OP ASDF:CL-SOURCE- FILE)) #<unavailable argument> #<unavailable argument> #<ASDF:LOAD-OP NIL {131F6EF1}> #<ASDF:CL-SOURCE-FILE "commands" {12811131}>) 10: ((LAMBDA (SB-PCL::.PV. SB-PCL::.NEXT-METHOD-CALL. SB-PCL::.ARG0. SB-PCL::.ARG1.)) ..) 11: ((SB-PCL::FAST-METHOD ASDF:PERFORM ASDF:AROUND (ASDF:LOAD-OP ASDF:CL-SOURCE-FILE)) ..) 12: ((LAMBDA ())) 13: ((FLET SB-THREAD::WITH-RECURSIVE-LOCK-THUNK))

1 0

[mcclim-devel] pathname completion on SBCL
by Cyrus Harmon 19 Jun '09

19 Jun '09

On recent SBCLs, at least, (directory "fo*.*") only finds foo if foo is a file, not a directory. Not sure if this is a bug or a feature, but it breaks my understanding of how filename completion should work. The following (slightly ugly) patch fixes things for me: diff --git a/presentation-defs.lisp b/presentation-defs.lisp index 8661046..fb2de97 100644 --- a/presentation-defs.lisp +++ b/presentation-defs.lisp @@ -1629,8 +1629,21 @@ protocol retrieving gestures from a provided string.")) do (replace so-far "\ \*" :start1 occurence) (setf start (+ occurence 2)) finally (return so-far))) + #+sbcl and #+sbcl wildcard-directories #+sbcl = + #+sbcl (format nil "~A*" + (loop for start = 0 ; Replace * -> \* + for occurence = (position #\* so-far :start start) + until (= start (length so-far)) + until (null occurence) + do (replace so-far "\\*" :start1 occurence) + (setf start (+ occurence 2)) + finally (return so-far))) for path in - #+(or sbcl cmu lispworks) (directory wildcard) + #+sbcl (remove-duplicates + (append (directory wildcard) + (directory wildcard-directories)) + :test #'equal) + #+(or cmu lispworks) (directory wildcard) #+openmcl (directory wildcard :directories t) #+allegro (directory wildcard :directories-are-files nil) #+cormanlisp (nconc (directory wildcard) Any suggestions on the best way to handle this? thanks, cyrus

1 1

[mcclim-devel] mcclim on windows
by Patrik Magnusson 17 Jun '09

17 Jun '09

Hello, I am wondering about the current status of mcclim on windows. I cannot myself get it to display anything, after trying a number of approaches. For X, I am using Xming from sourceforge. I can run the demodemo from a linux box and display it on the windows box, so I think X is OK. First try was with sbcl-1.0.29, clx-0.73, flexichain_1.5.1, spatial-trees-0.2 and mcclim from CVS. When I try the demodemo, nothing gets displayed, and if I try to interrupt sbcl it just dies. If I chose to exit Xming, the confirmation box reports that 1 client is attached - so I guess something is happening. I have tried this from emacs/slime and in raw sbcl. Second try was with lispbox from "Practical Common Lisp", which is Clisp-2.37 with libs as above. Again, nothing is displayed, though lisp is running at 100% of the CPU. When I interrupt lisp, I can see from the stack frames that the event loop is running, but Xming reports no clients attached. Third try was with clisp-2.47, the small windows binary from sourceforge (without the new-clx I think). Results were the same as for 2.37. I also tried all the above with clx-0.71, since that is what I have on my linux box (and which is working there), but results were the same. I also tried compiling the source for clisp-2.47 (to make sure new-clx isn't in it), but I was unable to do that in mingw. I can't really capture any other clues, and so I'm stuck. Does anyone have any info, or request for more from me? BR, /Patrik.

2 2

[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

[mcclim-devel] patch: eliminate undefined variable warnings from the build
by Nikodemus Siivola 30 Apr '09

30 Apr '09

Cheers, -- Nikodemus

1 0

[mcclim-devel] Fix crash
by Juliusz Chroboczek 20 Apr '09

20 Apr '09

Index: stream-input.lisp =================================================================== RCS file: /project/mcclim/cvsroot/mcclim/stream-input.lisp,v retrieving revision 1.54 diff -u -r1.54 stream-input.lisp --- stream-input.lisp 1 May 2008 21:45:23 -0000 1.54 +++ stream-input.lisp 2 Mar 2009 22:12:58 -0000 @@ -215,7 +215,7 @@ ;;; Do streams care about any other events? (defun handle-non-stream-event (buffer) (let* ((event (event-queue-peek buffer)) - (sheet (event-sheet event))) + (sheet (and event (event-sheet event)))) (if (and event (or (and (gadgetp sheet) (gadget-active-p sheet))

3 2

[mcclim-devel] [PATCH] cooperate with window manager
by Juliusz Chroboczek 20 Apr '09

20 Apr '09

Hi, The attached patch makes the CLX backend cooperate better with X11 window managers by marking frames as top-level windows. Juliusz

3 3