mcclim-devel

mcclim-devel@common-lisp.net

820 discussions

[mcclim-devel] how to subclass a pane in good style?
by Nikodemus Siivola 29 Jul '09

29 Jul '09

Attached file canvas-pane.lisp is a work-in-progress. clim-patch.lisp provides MEDIUM-DRAW-PIXELS* it depends on, based on Andy Hefner's code that he posted a while back. I use it in my raytracer's CLIM frontend to put up the pretty pictures as they are drawn, and to provide a selection area on already rendered images. There are (currently) three major behaviours that it provides for me: (SETF (CANVAS-RGBA CANVAS) <RGBA-AS-UB32>) allows me to quickly assign color to a pixel. (REPAINT-SHEET CANVAS (CANVAS-DIRTY-REGION CANVAS)) allows me to refresh the screen during rendering, updating only those portions where pixel colors have changed. (CANVAS-SELECTION CANVAS) gives me the bounding rectangle of the selected area. (A region is selected at any time by clicking and dragging on the canvas.) There may be any number of dubious things in there, but the things that most confuse me are: * What to subclass? I currently subclass APPLICATION-PANE. I don't know if I should subclass something else instead. * Unintended overriding. I seem to accidentally override the border-building stuff from APPLICATION-PANE. It is not obvious to me why this happens, nor do I know how to avoid this should I want to. * Event handling: to get pointer events I define a method on DISPATCH-EVENT that calls HANDLE-EVENT. Is this the way it is supposed to be done? * Event handling & coordinates: to get coordinates relative to canvas when the pointer is outside the canvas area during the click-and-drag selection I transform coordinates through a common ancestor. This seems a bit awkward -- is there a better way? Any comments would be most welcome. Cheers, -- Nikodemus

2 1

[mcclim-devel] having an image icon on push-button
by Sunil S Nandihalli 23 Jul '09

23 Jul '09

Hello, I was wondering if there is a way to have image-icons on push-buttons.. Regards, Sunil -- the more you know, the more you realize of how little you know in the grander scheme of things

2 1

[mcclim-devel] Can output records be moved?
by Remco Bras 15 Jul '09

15 Jul '09

Hello. Is there a way to move an output record to another position after it has been created, that is, to modify (output-record-position some-record)? Both versions of the user guide mention output-record-set-position, which appears to be undefined. Similarly, setf*, which they mention as an alternative, is undefined. I'm using McClim 0.9.6 on SBCL 1.0.18.

2 1

[mcclim-devel] :clipping-region woes
by Sumant Oemrawsingh 09 Jul '09

09 Jul '09

Hi guys, I'm having some problems with clipping regions (or I just don't understand the concept, which is still entirely possible). In the clim-listener, in the package clim-user, I do the following: (with-room-for-graphics (t) (draw-rectangle* *standard-output* -10 -10 10 10)) This gives a black, filled rectangle. Great, just as expected. Now, I want to try to define a clipping region: (with-room-for-graphics (t) (draw-rectangle* *standard-output* -10 -10 10 10 :clipping-region (make-rectangle* -5 -5 5 5))) What I expect is that it displays a smaller rectangle, namely the rectangle with side 20 clipped down to a side of 10. However, I don't see anything. So, I try the following: (with-room-for-graphics (t) (draw-rectangle* *standard-output* -10 -10 10 10 :clipping-region (make-rectangle* -20 -20 20 20))) Since the clipping region is _larger_ than the actual drawing, I expect to see the same as in the first sexp, where I didn't define any clipping region. Nevertheless, I see... NOTHING! Is this a bug, a feature, or am I hopelessly ignorant and should just give up ever trying to do anything remotely complicated in clim? Thanks, Sumant -- Sumant Oemrawsingh soemraws(a)xs4all.nl

3 3

[mcclim-devel] small clim-lisp:defconstant improvement
by Nikodemus Siivola 29 Jun '09

29 Jun '09

I was recently somewhat burned (performance-wise) by clim-lisp:defconstant being really a defvar. Would something like the following be an acceptable substitute? It remains portable, but allows implementations to do a much better job for important cases like numeric constants: (defmacro clim-lisp-patch:defconstant (symbol value &optional docu) (if (typep value '(or number character)) `(cl:defconstant ,symbol ,value ,@(and docu (list docu))) `(defvar ,symbol ,value ,@(and docu (list docu))))) Cheers, -- Nikodemus

1 0

[mcclim-devel] Skinning McCLIM interfaces
by Ram Vedam 25 Jun '09

25 Jun '09

I was curious if there is a possibility that McCLIM user interfaces can be skinned (change visual appearance) to look more "modern"? I haven't seen too much written on this topic and am wondering if it can currently be done, and if so, how? Ram

2 1

[mcclim-devel] [ANNOUNCE] McCLIM RPM available for Fedora
by Robert Uhl 24 Jun '09

24 Jun '09

I've packaged McCLIM for Fedora at: http://yum.octopodial-chrome.com/packages/cl-mcclim Probably the easiest thing to do is to install the octopodial-chrome package and then run 'yum install cl-mcclim.' -- Robert Uhl <http://public.xdi.org/=ruhl> Man, the creature who knows he must die, who has dreams larger than his destiny, who is forever working a confidence trick on himself, needs an ally. Mine has been tobacco. --John Boynton Priestley

1 0

Re: [mcclim-devel] mcclim on windows
by Patrik Magnusson 19 Jun '09

19 Jun '09

Hello again, Sorry but it turns out that an explicit (asdf :clim-clx) was what was missing. I didn't see the Cliki page about asdf-installing until yesterday and I was fooled by the fact that it wasn't necessary on linux. So, now it works. Both with the lispbox version of Clisp (2.37) and the small sourceforge binary (2.47). BR, /Patrik. On Fri, Jun 19, 2009 at 12:49:10AM +0400, Evgeny M. Zubok wrote: > Patrik Magnusson <magnusson.patrik(a)bredband.net> writes: > > > Could someone perhaps tell me the names of some good functions to > > trace, and so see how far the demodemo comes? > > You could try to load only clx (without mcclim) and run the examples > from clx/demo. For example, to load clx/demo/menu.lisp and run > > (xlib::just-say-lisp) > > The connection with X server is established in CLX (open-default-display > funtcion), so if you didn't see the simple menu from this example then > problem, more probably, laying in CLX-Xming interaction, not in McCLIM.

1 0

[mcclim-devel] Error: Class not yet defined: CLIM:INTERACTOR-PANE
by Cyrus Harmon 19 Jun '09

19 Jun '09

I think this is one of those errors that goes away upon zapping fasls, but I also think I've seen it before. Any clues? thanks, cyrus Class not yet defined: CLIM:INTERACTOR-PANE [Condition of type SIMPLE-TYPE-ERROR] Restarts: 0: [TRY-RECOMPILING] Recompile commands and try loading it again 1: [RETRY] Retry performing #<ASDF:LOAD-OP NIL {131F6EF1}> on #<ASDF:CL-SOURCE-FILE "commands" {12811131}>. 2: [ACCEPT] Continue, treating #<ASDF:LOAD-OP NIL {131F6EF1}> on #<ASDF:CL-SOURCE-FILE "commands" {12811131}> as having been successful. 3: [RETRY] Retry SLIME REPL evaluation request. 4: [ABORT] Return to SLIME's top level. 5: [TERMINATE-THREAD] Terminate this thread (#<THREAD "repl-thread" RUNNING {11A9D949}>) Backtrace: 0: (SB-KERNEL:FIND-CLASSOID-CELL CLIM:INTERACTOR-PANE)[:EXTERNAL] 1: (SB-FASL::FOP-FUNCALL) 2: (SB-FASL::LOAD-FASL-GROUP #<SB-SYS:FD-STREAM for "file /Users/ sly/src/lisp/mcclim/mcclim/sbcl-1.0.29.13-darwin-x86/ commands.fasl" {119F2639}>) 3: ((FLET SB-THREAD::WITH-RECURSIVE-LOCK-THUNK)) 4: ((FLET #:WITHOUT-INTERRUPTS-BODY-[CALL-WITH-RECURSIVE-LOCK]291)) 5: (SB-THREAD::CALL-WITH-RECURSIVE-LOCK ..) 6: (SB-FASL::LOAD-AS-FASL #<SB-SYS:FD-STREAM for "file /Users/sly/ src/lisp/mcclim/mcclim/sbcl-1.0.29.13-darwin-x86/ commands.fasl" {119F2639}> NIL #<unavailable argument>) 7: ((FLET SB-FASL::LOAD-STREAM) #<SB-SYS:FD-STREAM for "file /Users/ sly/src/lisp/mcclim/mcclim/sbcl-1.0.29.13-darwin-x86/ commands.fasl" {119F2639}>) 8: (LOAD #P"/Users/sly/src/lisp/mcclim/mcclim/sbcl-1.0.29.13-darwin- x86/commands.fasl")[:EXTERNAL] 9: ((SB-PCL::FAST-METHOD ASDF:PERFORM (ASDF:LOAD-OP ASDF:CL-SOURCE- FILE)) #<unavailable argument> #<unavailable argument> #<ASDF:LOAD-OP NIL {131F6EF1}> #<ASDF:CL-SOURCE-FILE "commands" {12811131}>) 10: ((LAMBDA (SB-PCL::.PV. SB-PCL::.NEXT-METHOD-CALL. SB-PCL::.ARG0. SB-PCL::.ARG1.)) ..) 11: ((SB-PCL::FAST-METHOD ASDF:PERFORM ASDF:AROUND (ASDF:LOAD-OP ASDF:CL-SOURCE-FILE)) ..) 12: ((LAMBDA ())) 13: ((FLET SB-THREAD::WITH-RECURSIVE-LOCK-THUNK))

1 0

[mcclim-devel] pathname completion on SBCL
by Cyrus Harmon 19 Jun '09

19 Jun '09

On recent SBCLs, at least, (directory "fo*.*") only finds foo if foo is a file, not a directory. Not sure if this is a bug or a feature, but it breaks my understanding of how filename completion should work. The following (slightly ugly) patch fixes things for me: diff --git a/presentation-defs.lisp b/presentation-defs.lisp index 8661046..fb2de97 100644 --- a/presentation-defs.lisp +++ b/presentation-defs.lisp @@ -1629,8 +1629,21 @@ protocol retrieving gestures from a provided string.")) do (replace so-far "\ \*" :start1 occurence) (setf start (+ occurence 2)) finally (return so-far))) + #+sbcl and #+sbcl wildcard-directories #+sbcl = + #+sbcl (format nil "~A*" + (loop for start = 0 ; Replace * -> \* + for occurence = (position #\* so-far :start start) + until (= start (length so-far)) + until (null occurence) + do (replace so-far "\\*" :start1 occurence) + (setf start (+ occurence 2)) + finally (return so-far))) for path in - #+(or sbcl cmu lispworks) (directory wildcard) + #+sbcl (remove-duplicates + (append (directory wildcard) + (directory wildcard-directories)) + :test #'equal) + #+(or cmu lispworks) (directory wildcard) #+openmcl (directory wildcard :directories t) #+allegro (directory wildcard :directories-are-files nil) #+cormanlisp (nconc (directory wildcard) Any suggestions on the best way to handle this? thanks, cyrus

1 1

← Newer
1
...
15
16
17
18
19
20
21
...
82
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

mcclim-devel