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

[mcclim-devel] question about curves and formatting graphs
by rpgoldman＠real-time.com 10 Apr '06

10 Apr '06

If one wanted to draw curvy lines in McCLIM, is there any way of doing this? I had assumed, foolish me, that this could be done using Bezier curves, but now I see that those were an Allegro extension to the standard, and not part of CLIM 2.0.... I'm not much of a graphics person, and don't understand X very well, so I was wondering --- is there anything about X itself that makes drawing curved lines particularly difficult? Also, has anyone been thinking about the possibility of dynamic graphs? I.e., graphs where one might want to enter leaves? Or the possibility of having a fixed graph where a user might move the nodes around to make the graph more readable. CLIM doesn't have any sort of "smart link" object that would support this, does it? Thanks, Robert

4 11

[mcclim-devel] Infinite loop in McCLIM
by Paul Werkowski 07 Mar '06

07 Mar '06

The attached program works the same in McCLIM and Lispworks CLIM, except McCLIM gets into an infinite loop (CMUCL latest) unless incremental-redisplay is enabled. The program just wants its displayed output to track resizing the frame from the window manager. The attachment should run correctly. But then comment out the :incremental-redisplay as shown below and trouble is at hand. (defclass test-pane (application-pane) () (:default-initargs :display-function 'tpdf ;;; YIKES - in McCLIM; without this, infinite loop!! ; :incremental-redisplay t ; :display-time :command-loop )) ;;; Paul

2 1

[mcclim-devel] accepting-values: prompts not clickable, no redraw, improper output recording?
by Clemens Fruhwirth 09 Jan '06

09 Jan '06

The attached test case does produce strange results for accepting-values calls. In the test case you will find 2 commands. The first one causes an implicit accepting values to be generated when you click on the menu button (or type "Implicit AV<ret>" in the interactor pane). In my CVS checkout (about 12 hours old), the Implicit AV command presents three prompts, of that only the last one accepts input. Notice, when damaging the draw area only the last one is repainted, even though not shown first. Explicit AV also generates three prompts, of that the first and the last accepts input. Both are redrawn upon X damage. I also put up a video of this behaviour in case it is not reproducable for you. They are at http://clemens.endorphin.org/strange-clim-artefacts/ (Most of them are MPEG4 provided with four different flavors of fourcc. The last is in Motion JPEG, but quite huge. I won't give an off-topic explaination here of what caused the problems seen by those participating in the IRC discussion of this bug, but when you're interested http://itdp.fh-biergarten.de/~itdp/html/mplayer-users/2005-03/msg00069.html ) Regards, -- Fruhwirth Clemens - http://clemens.endorphin.org for robots: sp4mtrap(a)endorphin.org

1 2

[mcclim-devel] Command and non-ASCII problems
by Troels Henriksen 08 Jan '06

08 Jan '06

Hi, I'm trying to learn CLIM, through McCLIM, from the ground up, but I'm having a slight problem with commands. The following example program shows the issue: (in-package :clim-user) (define-application-frame example-editor () () (:menu-bar menubar-command-table) (:panes (text-edit :text-editor)) (:layouts (default text-edit))) (define-example-editor-command com-quit () (frame-exit *application-frame*)) (make-command-table 'file-command-table :errorp nil :menu '(("Quit" :command com-quit))) (make-command-table 'menubar-command-table :errorp nil :menu '(("File" :menu file-command-table))) The "Quit" menu option shows up just fine, but nothing happens when I click it. Why is this? Furthermore, non-ASCII-input (the Danish special characters Æ, Ø and Å, for example) does not show up in the text-editor pane. I assume that McCLIM lacks support for this. Where would I want to look, if I am to hack up some support for this? -- \ Troels "Athas" Henriksen /\ sigkill.dk/blog (Danish)

5 7

[mcclim-devel] [patch] fix typos and postscript backend
by Tim Daly Jr. 30 Dec '05

30 Dec '05

Hi guys, This is a small patch to fix some typos and add output recording for NEW-PAGE in the postscript backend. When I tried to run CLIM-DEMO::POSTSCRIPT-TEST, it produced an invalid postscript file. Ghostscript failed to load it, complaining of a dictionary stack underflow. The reason was that the output from NEW-PAGE was at the top of the file, and not embedded between pages as it was meant to be. This is because WITH-OUTPUT-TO-POSTSCRIPT-STREAM uses output recording, (Perhaps this was introduced to make EPS work? Just a guess.), yet NEW-PAGE draws immediately instead of being recorded. I attempted to add output recording for NEW-PAGE. This patch fixes the postscript test mostly -- page 7 is translated to the lower right corner for some reason, but it's at least syntactically correct. I have no understanding of this stuff, so please check whether I've done something boneheaded. Thanks, Tim

2 1

[mcclim-devel] [patch] fix apparent typos
by tim＠tenkan.org 30 Dec '05

30 Dec '05

In my travels through the looking-pane, I bumped into these: -- -Tim

2 1

[mcclim-devel] Improved patch for with-output-as-gadget
by Paul Werkowski 30 Dec '05

30 Dec '05

Here is an improved patch that fixes problems in an earlier post with incorrect cursor position when incremental redisplay was active. It is still required that calls to with-output-as-gadget be wrapped in (updating-output ( ... :cache-value <some-constant>)) to avoid problems if the output-record is ever erased. Happy New Year! Paul

1 0

with-output-as-gadget (was Re: [mcclim-devel] Missing realizer in call to MAKE-PANE-1)
by pw＠snoopy.mv.com 28 Dec '05

28 Dec '05

I wrote: > I now cannot get a radio-box to appear at all, even > at the frame definition eg > > (:panes (rb (with-radio-box () :a :b :c))) > > so maybe something has regressed in that area? > No, it seems that radio/check boxes want only strings in the :choices list. I'm not sure the spec limits the items to strings - at least Lispworks CLIM is more inclusive. Anyhow, there still seems to be a problem in the with-output-as-gadget setup. I end up in the debugger with some layout function calling sheet-native-transformation on the parent of the check-box-pane which is NIL at this time. Anyone got a clue as who is responsible for providing a parent for this thing? Paul

3 7

[mcclim-devel] Re: [mcclim-cvs] CVS update: mcclim/dialog.lisp
by Paul Werkowski 26 Dec '05

26 Dec '05

> In method > #<STANDARD-METHOD LISP::PCL-CLOSE (CLIM-INTERNALS::WINDOW-STREAM) {2846A855}>: > No next method for arguments > (#<CLIM-INTERNALS::WINDOW-STREAM "(Unnamed Pane)" {58A56285}> NIL). > [Condition of type PCL::NO-NEXT-METHOD-ERROR] |That does not happen on sbcl. The last line of climi::close in |panes.lisp, the call (call-next-method) is the problem, as currently |there is no such next method. The following patch helps but I'll not |commit it as there might be such a method in the future. See The solution here is (when (next-method-p)(call-next-method))Paul

1 0

[mcclim-devel] with-output-as-gadget, again
by Paul Werkowski 24 Dec '05

24 Dec '05

Max, When you were researching this, did you notice that there is no problem with gadgets that have direct drawing methods, such as label-pane and toggle-button-pane. I wonder if there is missing replay-output-record method for the classes that have children (check-box radio-box scroller, etc). Paul

1 0