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

[mcclim-devel] clim-listener's show-directory and non-ascii filenames
by Samium Gromoff 18 Feb '07

18 Feb '07

Here's what i get with CVS mcclim while trying to Show Directory my ~: c-string encoding error (:external-format :ASCII): the character with code 208 cannot be encoded. [Condition of type SB-INT:C-STRING-ENCODING-ERROR] Restarts: 0: [ABORT] Return to application command loop 1: [ABORT] Return to SLIME's top level. 2: [TERMINATE-THREAD] Terminate this thread (#<THREAD "repl-thread" {AFC6941}>) Backtrace: 0: (SB-INT:C-STRING-ENCODING-ERROR :ASCII 208) Locals: SB-DEBUG::ARG-0 = 2 SB-DEBUG::ARG-1 = :ASCII SB-DEBUG::ARG-2 = 208 1: (SB-IMPL::OUTPUT-TO-C-STRING/ASCII "/home/deepfire/14 - Ð¡Ð²Ð¸Ð´ÐµÑÐµÐ»Ð¸.mp3") 2: (SB-UNIX:UNIX-LSTAT "/home/deepfire/14 - Ð¡Ð²Ð¸Ð´ÐµÑÐµÐ»Ð¸.mp3") 3: (SB-UNIX:UNIX-FILE-KIND "/home/deepfire/14 - Ð¡Ð²Ð¸Ð´ÐµÑÐµÐ»Ð¸.mp3" T) 4: (SB-IMPL::%ENUMERATE-FILES "/home/deepfire/" #P"/home/deepfire/14 - Ð¡Ð²Ð¸Ð´ÐµÑÐµÐ»Ð¸.mp3" T #<CLOSURE (LAMBDA #) {AAB93E5}>) 5: (SB-INT:UNIX-NAMESTRING #P"/home/deepfire/14 - Ð¡Ð²Ð¸Ð´ÐµÑÐµÐ»Ð¸.mp3" T) 6: (PROBE-FILE "/home/deepfire/14 - Ð¡Ð²Ð¸Ð´ÐµÑÐµÐ»Ð¸.mp3") 7: ((LAMBDA (SB-IMPL::MATCH)) "/home/deepfire/14 - Ð¡Ð²Ð¸Ð´ÐµÑÐµÐ»Ð¸.mp3") 8: (SB-IMPL::%ENUMERATE-FILES "/home/deepfire/" #P"/home/deepfire/*.*" T #<CLOSURE (LAMBDA #) {BE12D35}>) 9: ((LABELS SB-IMPL::DO-DIRECTORY) #P"/home/deepfire/*.*") 10: (DIRECTORY #P"/home/deepfire/*.*") 11: ((FLET #:DESTINATION-CONTINUATION5413)) 12: (SB-INT:SIMPLE-EVAL-IN-LEXENV (CLIM-LISTENER::COM-SHOW-DIRECTORY #P"/home/deepfire/") #<NULL-LEXENV>) 13: (CLIM-LISTENER::COM-EVAL (CLIM-LISTENER::COM-SHOW-DIRECTORY #P"/home/deepfire/")) regards, Samium Gromoff

2 2

[mcclim-devel] reinitializing panes
by Christophe Rhodes 17 Feb '07

17 Feb '07

Hi, A question came up on #lisp yesterday: essentially, it asked how to dynamically change the contents of a pane, in a similar way to changing layouts of a frame. My intuitive answer was to reinitialize the pane with a new :contents initarg, which was quickly followed by an intuitive suspicion that this wouldn't actually work in McCLIM currently. (The suspicion was strengthened by the example in the spec in 29.5.2, which doesn't define any bookkeeping for reinitialization, and confirmed when I actually tried it...) So, the first question: should what I suggested work in principle, or is there a reason why we shouldn't allow it (and what should be allowed instead?). The second question: if it should work, is there anything wrong with the attached implementation, apart from its cut-and-paste nature? Is there something in the protocols that I am not following? To try it out, run the vbox's toplevel, then issue the commands Double, followed by Draw. Comments? Cheers, Christophe

3 2

[mcclim-devel] request for help with accepting a complex object
by Robert Goldman 13 Feb '07

13 Feb '07

I have a complex object of two parameters that I would like to be able to accept. I.e., I would like to be able to prompt the user to enter the two parameters, and I will build an object out of them. I have been trying to do this in an interactor window using accepting-values and get the following error: GRAPH-MDP(13): (accept 'termination-function :stream pane :prompt "Termination function:") Error: No methods applicable for generic function #<STANDARD-GENERIC-FUNCTION INVOKE-UPDATING-OUTPUT> with args (#<STANDARD-INPUT-EDITING-STREAM @ #x9c015cc2> #<Closure (FLET CLIM-INTERNALS::INVOKE-ACCEPTING-VALUES #:UPDATING-OUTPUT-CONTINUATION105288) @ #x9c02ab02> CLIM-INTERNALS::ACCEPTING-VALUES-RECORD (NIL) #<Function EQL> CLIM-INTERNALS::NO-CACHE-VALUE #<Function FORCE-UPDATE-CACHE-TEST>) of classes (STANDARD-INPUT-EDITING-STREAM FUNCTION SYMBOL CONS FUNCTION SYMBOL FUNCTION) I was wondering if anyone could see their way to providing me a hint about what's wrong. Thanks, R

1 0

[mcclim-devel] Gtkairo/demodemo bug
by Samium Gromoff 12 Feb '07

12 Feb '07

When trying out the drawing part of demodemo, with mcclim using gtkairo, after drawing some lines i decided to draw an ellipse. This had the following effect: Attempt to invert the probably singular transformation #<CLIM-INTERNALS::STANDARD-HAIRY-TRANSFORMATION 0 0 0 -2 156 324>. [Condition of type CLIM:SINGULAR-TRANSFORMATION] Restarts: 0: [USE-VALUE] Supply a transformation to use instead of the inverse. 1: [ABORT] Return to application command loop 2: [ABORT] Return to application command loop 3: [ABORT] Return to SLIME's top level. 4: [TERMINATE-THREAD] Terminate this thread (#<THREAD "repl-thread" {AFDE919}>) Backtrace: 0: ((SB-PCL::FAST-METHOD CLIM:INVERT-TRANSFORMATION (CLIM-INTERNALS::STANDARD-TRANSFORMATION)) #<unavailable argument> #<unavailable argument> #<CLIM-INTERNALS::STANDARD-HAIRY-TRANSFORMATION 0 0 0 -2 156 324>) 1: ((SB-PCL::FAST-METHOD CLIM:INVERT-TRANSFORMATION :AROUND (CLIM-INTERNALS::CACHED-INVERSE-TRANSFORMATION-MIXIN)) (#(0) . #()) #S(SB-PCL::FAST-METHOD-CALL :FUNCTION #<FUNCTION #> :PV-CELL NIL :NEXT-METHOD-CALL NIL :ARG-INFO (1)) #<CLIM-INTERNALS::STANDARD-HAIRY-TRANSFORMATION 0 0 0 -2 156 324>) 2: (CLIM-GTKAIRO::SYNC-TRANSFORMATION #<CLIM-GTKAIRO::CAIRO-MEDIUM {DE8A9B9}> #<CLIM-INTERNALS::STANDARD-HAIRY-TRANSFORMATION 0 0 0 -2 156 324>) 3: ((LAMBDA ())) 4: ((LAMBDA ())) 5: (CLIM-GTKAIRO::INVOKE-WITH-GTK #<CLOSURE (LAMBDA #) {DD6018D}>) 6: ((SB-PCL::FAST-METHOD CLIM-INTERNALS::DO-GRAPHICS-WITH-OPTIONS-INTERNAL (CLIM:MEDIUM #1="#<...>" . #1#)) #<unused argument> #<unused argument> #<CLIM-GTKAIRO::CAIRO-MEDIUM {DE8A9B9}> #<CLIM-DEMO::CANVAS-PANE CLIM-DEMO::CANVAS {A8BB111}> #<CLOSURE (FLET CLIM-INTERNALS::GRAPHICS-OP) {DD59E2D}> :INK #<CLIM-INTERNALS::NAMED-COLOR "blue"> ..) 7: ((SB-PCL::FAST-METHOD CLIM:INVOKE-WITH-OUTPUT-RECORDING-OPTIONS (CLIM:OUTPUT-RECORDING-STREAM T T T)) #<unavailable argument> #<unavailable argument> #<CLIM-DEMO::CANVAS-PANE CLIM-DEMO::CANVAS {A8BB111}> #<CLOSURE (FLET #:CONTINUATION160) {DD59B5D}> NIL T) 8: ((LAMBDA (SB-PCL::.PV-CELL. SB-PCL::.NEXT-METHOD-CALL. SB-PCL::.ARG0. SB-PCL::.ARG1. SB-PCL::.ARG2. SB-PCL::.ARG3.)) #<unavailable argument> #<unavailable argument> #<CLIM-INTERNALS::FRAME-TRACKING-POINTER-STATE {DD56F69}> #<CLIM:POINTER-MOTION-EVENT {DD51929}> 156 322) 9: ((FLET CLIM-INTERNALS::DO-TRACKING)) 10: ((LABELS #:G103) #<CLIM-GTKAIRO::CAIRO-MEDIUM {DE8A9B9}>) 11: ((LAMBDA (SB-PCL::.PV-CELL. SB-PCL::.NEXT-METHOD-CALL. #1="#<...>" . #1#)) #<unused argument> #<unused argument> #<CLIM-INTERNALS::FRAME-TRACKING-POINTER-STATE {DD56F69}> #<CLIM-DEMO::CLIM-FIG {A8A9AC1}> #<CLIM-DEMO::CANVAS-PANE CLIM-DEMO::CANVAS {A8BB111}> -308893239 8) 12: (CLIM-DEMO::HANDLE-DRAW-OBJECT #<CLIM-DEMO::CANVAS-PANE CLIM-DEMO::CANVAS {A8BB111}> 156 324) 13: ((SB-PCL::FAST-METHOD CLIM:DEFAULT-FRAME-TOP-LEVEL (CLIM:APPLICATION-FRAME)) #<unused argument> #<unused argument> #<CLIM-DEMO::CLIM-FIG {A8A9AC1}> :COMMAND-PARSER CLIM:COMMAND-LINE-COMMAND-PARSER :COMMAND-UNPARSER CLIM:COMMAND-LINE-COMMAND-UNPARSER :PARTIAL-COMMAND-PARSER ..) 14: ((SB-PCL::FAST-METHOD CLIM:DEFAULT-FRAME-TOP-LEVEL (CLIM:APPLICATION-FRAME)) #<unavailable argument> #<unavailable argument> #<CLIM-DEMO::CLIM-FIG {A8A9AC1}>) 15: ((SB-PCL::FAST-METHOD CLIM:RUN-FRAME-TOP-LEVEL (CLIM:APPLICATION-FRAME)) #<unused argument> #<unused argument> #<CLIM-DEMO::CLIM-FIG {A8A9AC1}>) 16: ((SB-PCL::FAST-METHOD CLIM:RUN-FRAME-TOP-LEVEL :AROUND (#1="#<...>" . #1#)) #<unused argument> #S(SB-PCL::FAST-METHOD-CALL :FUNCTION #<FUNCTION #> :PV-CELL NIL :NEXT-METHOD-CALL NIL :ARG-INFO (1 . T)) #<CLIM-DEMO::CLIM-FIG {A8A9AC1}>) 17: ((LAMBDA (&REST IGNORE))) 18: (CLIM-INTERNALS::INVOKE-CALLBACK #<CLIM-GTKAIRO::GTK-BUTTON "(Unnamed Pane)" {DDAED39}> #<CLOSURE (LAMBDA #) {DDD0365}>) 19: (CLIM-EXTENSIONS:SIMPLE-EVENT-LOOP #<CLIM-DEMO::DEMODEMO {DC5B199}>) 20: (CLIM-EXTENSIONS:SIMPLE-EVENT-LOOP #<CLIM-DEMO::DEMODEMO {DC5B199}>) 21: ((SB-PCL::FAST-METHOD CLIM:READ-FRAME-COMMAND :AROUND (#1="#<...>" . #1#)) #<unused argument> #S(SB-PCL::FAST-METHOD-CALL :FUNCTION #<FUNCTION #> :PV-CELL NIL :NEXT-METHOD-CALL NIL :ARG-INFO (1 . T)) #<CLIM-DEMO::DEMODEMO {DC5B199}> :STREAM ..) 22: ((SB-PCL::FAST-METHOD CLIM:DEFAULT-FRAME-TOP-LEVEL (CLIM:APPLICATION-FRAME)) #<unused argument> #<unused argument> #<CLIM-DEMO::DEMODEMO {DC5B199}> :COMMAND-PARSER CLIM:COMMAND-LINE-COMMAND-PARSER :COMMAND-UNPARSER CLIM:COMMAND-LINE-COMMAND-UNPARSER :PARTIAL-COMMAND-PARSER ..) 23: ((SB-PCL::FAST-METHOD CLIM:DEFAULT-FRAME-TOP-LEVEL (CLIM:APPLICATION-FRAME)) #<unavailable argument> #<unavailable argument> #<CLIM-DEMO::DEMODEMO {DC5B199}>) 24: ((SB-PCL::FAST-METHOD CLIM:RUN-FRAME-TOP-LEVEL (CLIM:APPLICATION-FRAME)) #<unused argument> #<unused argument> #<CLIM-DEMO::DEMODEMO {DC5B199}>) 25: ((SB-PCL::FAST-METHOD CLIM:RUN-FRAME-TOP-LEVEL :AROUND (#1="#<...>" . #1#)) #<unused argument> #S(SB-PCL::FAST-METHOD-CALL :FUNCTION #<FUNCTION #> :PV-CELL NIL :NEXT-METHOD-CALL NIL :ARG-INFO (1 . T)) #<CLIM-DEMO::DEMODEMO {DC5B199}>) 26: (SB-INT:SIMPLE-EVAL-IN-LEXENV (CLIM-DEMO::RUN-TEST 'CLIM-DEMO::DEMODEMO) #<NULL-LEXENV>) 27: (SWANK::EVAL-REGION " (clim-demo::run-test 'clim-demo::demodemo) " T) 28: ((LAMBDA ())) 29: ((LAMBDA (SWANK-BACKEND::FN)) #<CLOSURE (LAMBDA #) {DBBCE35}>) 30: (SWANK::CALL-WITH-BUFFER-SYNTAX #<CLOSURE (LAMBDA #) {DBBCE35}>) 31: (SWANK:LISTENER-EVAL " (clim-demo::run-test 'clim-demo::demodemo) ") 32: (SB-INT:SIMPLE-EVAL-IN-LEXENV (SWANK:LISTENER-EVAL " (clim-demo::run-test 'clim-demo::demodemo) ") #<NULL-LEXENV>) SBCL is 1.0, McCLIM is very recent CVS. regards, Samium Gromoff

2 1

[mcclim-devel] presentation example from docs
by Cyrus Harmon 11 Feb '07

11 Feb '07

Hi mcclim devels, Well, I'm finally getting around to learning how to write a mcclim app. For a change, I figured i'd read the documentation first this time. Granted this is a minor gripe but when I run the presentation example given in the manual, the manual says I should see that output "the 15 or The third month" when I click on the shown objects. In fact I get "the 15 of THE". Is the manual in error or is something wrong here? Thanks, Cyrus

2 4

[mcclim-devel] while I'm picking minor mcclim nits...
by Cyrus Harmon 10 Feb '07

10 Feb '07

This fixes a few compile warnings. Of course, I have no idea what this does :) but the changes look like the right thing to do. Cyrus --- presentation-defs.lisp 10 Feb 2007 15:11:02 -0800 1.71 +++ presentation-defs.lisp 10 Feb 2007 15:17:12 -0800 @@ -1121,11 +1121,11 @@ &key view (default nil defaultp) (default-type nil default-type-p) - activation-gestures + (activation-gestures nil activationsp) (additional-activation-gestures nil additional-activations-p) - delimiter-gestures + (delimiter-gestures nil delimitersp) (additional-delimiter-gestures nil additional-delimiters-p) @@ -1136,13 +1136,11 @@ (with-activation-gestures ((if additional-activations-p additional-activation-gestures activation-gestures) - :override activationsp) - (with-delimiter-gestures ((if additional-delimiters-p + :override activationsp) (with-delimiter-gestures ((if additional-delimiters-p additional-delimiter-gestures delimiter-gestures) :override delimitersp))) - (when (or (zerop (- end start)) - (let ((maybe-end)))) + (when (or (zerop (- end start))) (if defaultp (return-from accept-from-string (values default (if default-type-p

1 0

[mcclim-devel] Drei and input focus
by Christophe Rhodes 06 Feb '07

06 Feb '07

Hi, I am pretty sure that Drei gadgets are doing something naughty with input focus. My X11 window manager has focus-follows-mouse (well, strictly, sloppy focus) for top-level windows. If I make a CLIM application containing a drei pane, then the application window will steal focus: if I have my mouse over the drei buffer, and then move it into a window which is above some portion of the drei pane, that window will get focus for a brief moment, and then the drei application will take it back... Cheers, Christophe

3 10

[mcclim-devel] Delimiter gestures and the bowels of input editing
by Troels Henriksen 30 Jan '07

30 Jan '07

Observe the following presentation definitions: (define-presentation-type unacceptable ()) (define-presentation-method accept ((type unacceptable) stream view &key) (with-delimiter-gestures (#\Space) (list (accept 'package :stream stream :view view :prompt nil) (accept 'package :stream stream :view view :prompt nil)))) (defun test-unacceptable (&optional (stream *standard-input*)) (with-input-editing (stream) (replace-input stream (format nil "CLIM-USER CL-USER~%") :buffer-start 0) (accept 'unacceptable :stream stream))) When (test-unacceptable) is run, I'd expect a return value of (#.(find-package :clim-user) #.(find-package :cl-user)). In Drei, this won't work, because the call to `replace-input' in `complete-input' will trigger a rescan, and since the delimiter gesture is left unread once "CLIM-USER" has been read, it will prevent the proper parsing of the second element of input (to be specific, it will see it as empty). Goatee gets around this by introducing a nonspecified hack in `replace-input' whereby passing :rescan nil explicitly causes the function to not queue a rescan, even if it is necessary. (This example doesn't work in Goatee anyway, though, but I guess that's for another reason). My question is this: do you think the above code should work and do as I think, and how exactly are delimiter gestures supposed to be handled? -- \ Troels "Athas" /\ Henriksen

1 0

[mcclim-devel] Problem with scrolling windows and repainting
by Robert P. Goldman 24 Jan '07

24 Jan '07

I have a problem with scrolling not properly syncing with repaint, I believe. See the picture at http://rpgoldman.real-time.com/inspector-bug.png that shows that I can (in Clouseau, the CLIM inspector) scroll off to the right into what looks like space that is never painted, and so is just gray emptiness. -- Robert P. Goldman Senior Scientist Smart Information Flow Technologies (d/b/a SIFT, LLC) 211 N. First St., Suite 300 Minneapolis, MN 55401 Voice: (612) 384-3454 Email: rpgoldman(a)SIFT.info

2 1

[mcclim-devel] Re: [mcclim-cvs] CVS mcclim (scroll-extent vs. move-sheet)
by Andy Hefner 23 Jan '07

23 Jan '07

On 10/28/06, thenriksen <thenriksen(a)common-lisp.net> wrote: > + ;; XXX: We cannot use `scroll-extent', because McCLIM ignores it > + ;; unless the scrollee happens to be drawing. Very weird, should > + ;; be fixed. I think I finally deciphered the purpose of the method in recording.lisp which defines this odd behavior: to supress scrolling of the stream when recording output to an offscreen record (such as using with-output-to-output-record). This is a legitimate concern, and simply removing the method would be wrong. This suggests that output to an offscreen output record should also not cause the stream-pane to be resized. McCLIM does not guard against this case. The following program demonstrates the problem: (in-package :clim-user) (define-application-frame oops-1 () () (:pane (scrolling (:width 300 :height 300) (make-pane :application-pane :end-of-line-action :allow :end-of-page-action :allow :display-function (lambda (frame stream) (with-output-to-output-record (stream) (dotimes (i 200) (format stream "~&You never see this.~%"))) (format stream "All those scrollbars for this little line of text?~%")))))) The correct solution might involve checking that the open output record is connected to the stream output history, and supressing resizing and scrolling only if it is not (indicating offscreen drawing). Hmm.

1 0