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

[mcclim-devel] dragging-output and patterns
by Stas Boukarev 16 Apr '09

16 Apr '09

The attached file demonstrates the following behaviour: * When dragging over a pattern, pattern becomes distorted. * When dragging over a circle it is ok. And sometimes I get the following error, backtrace shows that it's signaled while doing DRAG-OUTPUT-RECORD: There is no applicable method for the generic function: #<STANDARD-GENERIC-FUNCTION SHEET-NATIVE-TRANSFORMATION #x300041532E4F> when called with arguments: (NIL) With gtkairo pattern doesn't become distorted. -- With best regards, Stas.

1 1

None
by None 14 Mar '09

14 Mar '09

1 0

[mcclim-devel] event handling outside the top-level loop
by Sascha Wilde 10 Mar '09

10 Mar '09

Hi *, I'm playing around with an mandelbrot explorer with an simple clim interface. This means the application spends a lot of time in an local loop[0]. During this time the interface is "dead" as no events are handled. So I would like to trigger the event handling from time to time in my own code -- is there an easy way to do so? cheers sascha [0] actually an recursion with the algorithm I'm using -- Sascha Wilde Real programmers don't want "what you see is what you get", they want "you asked for it, you got it". They want editors that are terse, powerful, cryptic, and unforgiving. In a word, Teco.

2 1

[mcclim-devel] For panes, :menu-bar height is always zero.
by Dave Goel 09 Mar '09

09 Mar '09

I am playing with a new mcclim, downloaded yesterday or so via clbuild. If I specify a :menu-bar for a pane explicitly, the height is always zero, no matter what. My current workaround is to use clim-internals:make-menu-bar. As an example, I am attaching a file, with several menubars. Moreover, I switch the layout of the menu-bars dynamically (and can even show/hide some bars as I want) using the movethingsaround button. See the commented out parts in there like: ;;(pane2 :menu-bar :command-table 'menubarb-command-table :min-y 100 which I had to replace with clim-internals:make-menu-bar. I am both attaching as well as including the file below. Thanks a lot. -dave -- ;; 2009-03-08 T19:39:18-0400 (Sunday) D. Goel ;; Some of this came from http://constantly.at/lisp/ui.html ;;; This example manually specifies the menu-bar panes. ;; Not only that, each menu-bar's submenu is further a command-table ;; rather than a simple command.. ;; Notice that the quit button is greyed out for mcclim because we ;; defineed it via define-command-table. We should have defined it via ;; define-frame-tag-command-table instead! ;; This method does not work for mcclim. ;; (pane2 :menu-bar :command-table 'menubarb-command-table :min-y 100 ;; The height is 0 no matter what you do. So, instead we call ;; clim-internals! (define-command-table menubar-command-table :menu (("Menub" :menu menu-command-table) ;;("Move 2nd bar" :command move-things) ("Exitb" :command com-quit-frame))) (define-command-table menubarb-command-table :menu (("Menu" :menu menub-command-table) ("Quit" :command com-quit-frame))) (define-application-frame tags-frame () ((message :initform "Message" :accessor tags-message)) (:panes ;; The commented out should be the best method, but broken. ;; This should be the actual method in clim, but is broken ;; (invisible bar, so make-menu-bar instead. ;;(pane2 :menu-bar :command-table 'menubarb-command-table :min-y 100 ;;:min-height 100 :height 100) ;; ;; This one is broken in mcclim for the same reason! ;;(pane2 (make-pane :menu-bar :command-table 'menubar-command-table ;; :height 100 :min-height 30)) ;; We next explore two other methods to make menubar. (pane1 (clim-internals::make-menu-bar 'menubar-command-table)) (pane2 (clim-internals::make-menu-bar 'menubarb-command-table)) (some-pane :application :display-function 'display-some-pane) (my-interactor :interactor) (mouse :pointer-documentation)) (:layouts (default (vertically () (1/3 pane1) (1/3 pane2) (1/3 some-pane) (:fill my-interactor) mouse)) (moved (vertically () (1/3 pane1) (1/3 some-pane) pane2 (:fill my-interactor) mouse)))) ;; Notice that while it serves as a quit function within pane1 and ;; pane2, it also shows as a "Quit frame" command on the very top ;; menu. That part happens because we have included a :menu t below. (define-tags-frame-command (com-quit-frame :menu t) () (frame-exit *application-frame*)) ;; this was in there originally, but these are greyed out! ;; (define-command com-hello () ;; (setf (tags-message *application-frame*) "Hello there!")) ;; Now see, the introduction of this move-things causes mcclim to come ;; up with its own menubar as well. If this hadn't been there, mcclim ;; would not have its own menubar. Of course, we can also make it a ;; subpart of one of the menubars we have defined. (define-tags-frame-command (com-move-things :menu t) () (setf (frame-current-layout *application-frame*) (if (eql (frame-current-layout *application-frame*) 'default) 'moved 'default))) (define-tags-frame-command com-hello () (setf (tags-message *application-frame*) "Hello there!")) (define-tags-frame-command com-exclaim () (setf (tags-message *application-frame*) "You there!")) ;; Notice how this one shows greyed out!! This is because it is not ;; defined as a tags-frame command table. (define-command com-hi () (setf (tags-message *application-frame*) "Hi there!")) (define-command-table menu-command-table :menu (("Say Hello" :command com-hello) ("Say Hi" :command com-hi))) (define-command-table menub-command-table :menu (("Exclaim" :command com-exclaim) ("Exclaim" :command com-exclaimb))) (defun test () (flet ((run () ;; Intentional sleep to test the sleep-enough function below. (sleep 1) (let ((frame (make-application-frame 'tags-frame :top 0 :left 0 :right 3000 :bottom 30000 ))) (setq *test-frame* frame) (run-frame-top-level frame)))) (mp:process-run-function "tags" #'run))) (defmethod display-some-pane ((frame tags-frame) stream) (format stream (tags-message frame))) (defmethod display-another-pane ((frame tags-frame) stream) (declare (ignore stream)) (let ((pane (get-frame-pane *application-frame* 'another-pane))) (window-clear pane) (draw-rectangle* pane 10 10 200 150 :filled nil :line-thickness 2) (draw-ellipse* pane 150 100 10 0 0 30)))

1 0

[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