mcclim-devel February 2009

mcclim-devel@common-lisp.net

9 participants
8 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] unsupplied-argument-marker
by Christophe Rhodes 28 Feb '09

28 Feb '09

Hi, I think that *unsupplied-argument-marker* (and *numeric-argument-marker*) should not be uninterned symbols or conses. The basic reason is that (define-command-table foo-menu-table :menu (("Foo" (com-foo #.*unsupplied-argument-marker*)))) or any other use of the literal value of the markers will not survive a compile-file/load-fasl cycle: a "similar" but not EQ value will be constructed. This causes PARTIAL-COMMAND-P to fail, and confusion to reign. Patch attached (making the markers uninterned symbols -- one could imagine cleverer, interned struct representations, but that's probably overkill). Also attached is a proposed adjustment to the READ-FRAME-COMMAND :AROUND handling of menu-items and partial commands. At the moment, the method only attempts to fill in partial command arguments if the input stream is an interactor-pane; and command-line-read-arguments is hardcoded. The second piece of the attached patch removes both of these restrictions, which is what is needed for my application, but I'm unsure of the general ramifications. (I need the removal of the interactor-pane requirement because esa:minibuffer-pane is not a clim:interactor-pane. I'm not sure why not, nor what the protocol requirements on interactor-panes are.) Comments? I think that these changes are fairly safe, but there might be better fixes that are less conservative. Best, Christophe

3 4

Re: [mcclim-devel] unsupplied-argument-marker
by Brian Mastenbrook 28 Feb '09

28 Feb '09

On Feb 28, 2009, at 11:18 AM, Andreas Davour wrote: > What is Trac? http://lmgtfy.com/?q=trac -- Brian Mastenbrook http://brian.mastenbrook.net/ brian(a)mastenbrook.net

1 0

[mcclim-devel] [Patch] run-program for CCL for Listener
by Stas Boukarev 24 Feb '09

24 Feb '09

Patch attached. -- With Best Regards, Stas.

2 1

[mcclim-devel] OpenGL backend
by patrice.lespagnol＠obs-nancay.fr 22 Feb '09

22 Feb '09

Hello, I'am interessed in using the OpenGL backend of McCLIM : what is its state currently ? What would be a good start point to work on it ? Thanks for your advices.

3 2

[mcclim-devel] :scrollbars option vs (scrolling () ...)
by Nikolaus Demmel 17 Feb '09

17 Feb '09

Hi, can anyone explain to me the difference between using the application- pane's :scrollbar option or alternatively setting it to nil and using a (scrolling () ...) macro around that application pane in the layout? It looks a bit different (the scrolling macro comes with a black padding i think), but in essence, it is the same funktionality, right? Best regards, Niko Demmel

1 0

[mcclim-devel] Non shrinking panes
by Nikolaus Demmel 14 Feb '09

14 Feb '09

Hi list In the following when i talk about width of the pane, i mean the value returned by (bounding-rectangle-width pane). I have an application pane with not much output (which is not very wide and definately not as wide as the pane) at the beginning. When i resize (shrink) the whole frame (manually, using the mouse), the application pane adapts in size until it is as wide as the intial output, then the scrolling kicks in, but the size of the pane doesn't shrink further. This makes sense. Now if after a while (or due to some user action) the output on the pane becomes wider, then the "minimum pane width" that i can achieve with shrinking the frame as above becomes this new withs of the output. This also makes sense. Now if the output changes to something not as wide again, then the "minimum pane width" acheived by resizing the whole window as above doesn't shrink. It stays at the maximum width of output over the whole lifetime of the application. Does this have to do with output recording? How can i make the pane become less wide again? The background is, that i want to draw some lines as wide as the pane that adapt in size, when i resize the window. This works with enlarging the window, but as described above not with shrinking it. How could i acheive that. Regards, Niko Demmel

2 4

[mcclim-devel] Drei gadgets
by Christophe Rhodes 09 Feb '09

09 Feb '09

Hi, For the revival of an application (an editor for lute tablature) whose previous incarnation was as a Climacs syntax, I'm trying to use a Drei gadget pane. I've found the attached patch necessary: the first hunk to prevent an infinite loop in command lookup, and the second to use the minibuffer stream for extended commands. I'm not sure if either of these patches is correct. Any advice would be welcome. Best, Christophe

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

mcclim-devel February 2009