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

[mcclim-devel] does McCLIM want an issue tracker?
by Samium Gromoff 04 Mar '07

04 Mar '07

The local consensus on #lisp (roughly, lichtblau and me) was that it will do good to have an issue tracker for McCLIM. I volunteer to set up/help setting up one, as well as semi-regularly look through the issues posted there. regards, Samium Gromoff

3 3

[mcclim-devel] open-window-stream and :scroll-bars nil
by Samium Gromoff 04 Mar '07

04 Mar '07

In reasonably[1] fresh McCLIM/CLX i get a sheet with scrollbars out of that form: (open-window-stream :scroll-bars nil) regards, Samium Gromoff [1]: Reasonably as in "a cvs update did net reveal changes in essential areas"

2 2

[mcclim-devel] menu items, command arguments and read-frame-command
by Robert Goldman 04 Mar '07

04 Mar '07

I have a command in my McCLIM application that allows the user to set pathname defaults: (define-taems-mdp-app-command (com-change-taems-filename-defaults :name t) ((pathname 'directory-pathname :default (make-pathname :directory (pathname-directory (taems-pathname-defaults *application-frame*))) :prompt "New default TAEMS model directory?")) ...) You will see that it takes one argument. I have put it in the file menu of my application, and when I try to invoke it, McCLIM crashes with the following error: Error: KAUAI-GRAPHER::COM-CHANGE-TAEMS-FILENAME-DEFAULTS got 0 args, wanted 1 arg. [condition type: PROGRAM-ERROR] Restart actions (select using :continue): 0: Return to application command loop 1: Abort entirely from this (lisp) process. [Current process: TAEMS CLIM Grapher] [1] CL-USER(1): :bt Evaluation stack: GRAPH-MDP::COM-CHANGE-TAEMS-FILENAME-DEFAULTS <- (METHOD CLIM:EXECUTE-FRAME-COMMAND (CLIM:APPLICATION-FRAME T)) <- (METHOD CLIM:DEFAULT-FRAME-TOP-LEVEL (CLIM:APPLICATION-FRAME)) <- (:INTERNAL (:EFFECTIVE-METHOD 1 T ...) 0) <- (:INTERNAL (MOP:CLASS-DEFAULT-INITARGS GRAPH-MDP::TAEMS-MDP-APP :TOP-LEVEL-LAMBDA) 0) <- (METHOD CLIM:RUN-FRAME-TOP-LEVEL (CLIM:APPLICATION-FRAME)) <- (METHOD CLIM:RUN-FRAME-TOP-LEVEL :AROUND ...) <- (:INTERNAL (:EFFECTIVE-METHOD 1 T ...) 0) <- (:INTERNAL GRAPH-MDP:RUN-GRAPHER 0) My understanding from reading the manual is that when I invoke this command from the menu, it should prompt me to accept the arguments. add-menu-item-to-command-table [Function] Arguments: command-table string type value &key documentation (after :end) keystroke text-style (errorp t) button-type s Adds a command menu item to command-table's menu. The arguments are: command-table Can be either a command table or a symbol that names a command table. string The name of the command menu item. The character case and style of string are ignored. This is how the item will appear in the menu. type This is one of: :command, :menu, or :divider. (:function, called for in the CLIM spec, is not supported in this release.) When type is :command, value should be a command (a cons of a command name followed by a list of the command's arguments), or a command name. (When value is a command name, it behaves as though a command with no arguments was supplied.) In the case where all of the command's required arguments are supplied, clicking a command menu item invokes the command immediately. Otherwise, the user will be prompted for the remaining required arguments. [from the Allegro CLIM manual; the online spec has similar wording.] Can anyone say why McCLIM is crashing here? It seems like the read-frame-command :around method should have invoked command-line-remaining-arguments-for-partial-command. The code is here: (defmethod read-frame-command :around ((frame application-frame) &key (stream *standard-input*)) (with-input-context ('menu-item) (object) (call-next-method) (menu-item (let ((command (command-menu-item-value object))) (unless (listp command) (setq command (list command))) (if (and (typep stream 'interactor-pane) (member *unsupplied-argument-marker* command :test #'eq)) (command-line-read-remaining-arguments-for-partial-command (frame-command-table frame) stream command 0) command))))) Is it possible that the stream is not an interactor-pane when the menu item is selected? For other commands, I have kludged around this problem and made them take no arguments and just accept them "by hand," as it were... Any help would be much appreciated. thanks, R

2 3

[mcclim-devel] slider panes and :number-of-tick-marks
by Samium Gromoff 04 Mar '07

04 Mar '07

In cvsly fresh McCLIM/CLX i get a slider pane without tick marks out of that form: (make-pane 'slider :min-value 0 :value 0 :max-value 10 :number-of-tick-marks 3) Although quantization (:number-of-quanta) works all right. regards, Samium Gromoff

1 0

[mcclim-devel] Gtkairo and UTF-8
by David Lichteblau 03 Mar '07

03 Mar '07

Hi, thanks to recent cffi improvements, Gtkairo supports UTF-8 now. However, it will only build with the cffi-newtypes branch. http://common-lisp.net/~loliveira/darcs/cffi-newtypes/ http://article.gmane.org/gmane.lisp.cffi.devel/1034 d.

1 0

[mcclim-devel] window functions
by Bill Sauer 23 Feb '07

23 Feb '07

The CLIM user manual indicates that the following functions are available... (window-label window) (window-parent window) (window-children window) (window-inside-height window) (window-inside-width window) etc... These don't seem to exist in MCCLIM. The question is are there plans to implement them in the future or are there other functions which replaced them. Thanks for the help Bill Sauer

3 3

[mcclim-devel] getting started...
by Perry E. Metzger 22 Feb '07

22 Feb '07

Pardon the utterly naive newbie question, but I'm brand new to McClim, have never used ASDF (and barely understand what it is), etc. Say I want to get from zero (not even an installed Common Lisp) to running a McClim demo on my machine (running Ubuntu Linux) in short order. What do I need to do to get there? -- Perry E. Metzger perry(a)piermont.com

7 7

[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