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

[mcclim-devel] Annc: Freeze for Mothering Sunday release
by Andreas Fuchs 28 Feb '05

28 Feb '05

Hello everybody, this message marks the begin of the freeze period of McCLIM proper (that includes all lisp files in the mcclim/ root directory, Backends/, Goatee/ and Lisp-Dep/) for the Mothering Sunday release. Apps/, Examples/ and Experimental/ are due to freeze next monday. This means for you, the user of McCLIM: Please help us test McCLIM. Running every available CLIM app, running the examples, building on different lisp implementations, trying obscure things, and sending reports of bugs you find are all very much appreciated (especially the sending reports of bugs part). The more bugs we find now, the better the release will be. the McCLIM developer: Bug fixes only, please. And please stick to conservative commits: fixing a bug in the layout protocol is ok, but rewriting the layout protocol should wait until after the release. If a bug can only be fixed by a big change, the fix should wait until after the release - the bug will be mentioned in the release notes. The intent is to release something that resembles the state of today's McCLIM as closely as possible, but without the easy-to-fix bugs. (-: Cheers, -- Andreas Fuchs, <asf(a)boinkor.net>, asf(a)jabber.at, antifuchs

2 2

[mcclim-devel] backspace at argument prompt -> infinite loop
by Luke Gorrie 26 Feb '05

26 Feb '05

Hi guys, Some IRC log to share :-) <Luke_> tbmoore: if I type command name, space (see prompt for argument), backspace -- then it goes into an infinite loop printing the "scan-pointer ~S > insertion-pointer ~S; shouldn't happen" message <Luke_> in Closure or in clim-listener <tbmoore> Luke_: Ouch <Luke_> if I nuke the listener thread at this point it seems to put things into a bad state where if I try to start a new listener it hangs before reaching the prompt (under SBCL) <tbmoore> Luke_: If you can send email to the list, that would be good. <tbmoore> But I think this should not be too hard to fix.

1 0

[mcclim-devel] Reposting gadgets.patch
by Andy Hefner 25 Feb '05

25 Feb '05

Actually neither of these patches are correct, the intent is to modify the value of the slots. :) On Thu, 24 Feb 2005 23:23:54 -0600, mikemac(a)mikemac.com <mikemac(a)mikemac.com> wrote: > > > >Index: gadgets.lisp > > >@@ -2700,7 +2700,7 @@ > > (height (space-requirement-height sr))) > > (allocate-space child width height) > > (setf (gadget record) child) > >- (with-slots (x1 x2 y1 y2) record > >+ (multiple-value-bind (x1 y1 x2 y2) (slot-value record 'coordinates) > > Try this instead: > > (multiple-value-bind (x1 y1 x2 y2) (rectangle-edges* record) > > Using internal state of classes is a no-no. Use the interfaces > provided by the spec. > > Mike McDonald > mikemac(a)mikemac.com > _______________________________________________ > mcclim-devel mailing list > mcclim-devel(a)common-lisp.net > http://common-lisp.net/cgi-bin/mailman/listinfo/mcclim-devel >

3 2

[mcclim-devel] Reposting gadgets.patch
by Anthony Juckel 25 Feb '05

25 Feb '05

I'm resending this patch (this time as a unified diff) to gadgets.lisp as, apparently, it has been overlooked. Perhaps I was a bit too terse when sending the patch the first time around. This patch is a one-line bug fix, which I believe stems from a change in standard-rectangle. Previously, rectangle coordinates were stored in slots (x1 y1 x2 y2) within standard-rectangle. In an attempt to optimize rectangle operations, these were condensed into a single coordinates slot. The problem is that an :after method on initialize-instance for gadget-output-record was never notified of said change, and was still attempting to call (with-slots (x1 x2 y1 y2) ...) on a standard rectangle. This was causing problems for me, so I swapped in a destructuring-bind on coordinates instead. Anthony W. Juckel

2 1

[mcclim-devel] mcclim.asd, defresource.lisp
by tim＠tenkan.org 24 Feb '05

24 Feb '05

Hi all, Closure uses the DEFRESOURCE macro defined in defresource.lisp. The new mcclim.asd doesn't load defresource.lisp. (system.lisp does). I don't know what defresource.lisp really depends on, but after applying the patch below and deleting all the mcclim fasls, I was still able to load mcclim. So, I propose: -- -Tim

1 0

[mcclim-devel] building probl lw darwin
by ml13＠onlinehome.de 23 Feb '05

23 Feb '05

Hi, I cannot, unfortunately, build mcclim on lw. The last form in the file "fix-lispworks.lisp" is causing trouble: (defmethod clim-mop:class-direct-superclasses ((instance (eql *ptype-t-class*))) (list (find-class 'standard-object))) ;; scary.. lw complains: Error: The variable *PTYPE-T-CLASS* is unbound. I am completely new to mcclim, so I am sorry for not backtracing this more properly. Any ideas? Thanks, Peter

1 0

[mcclim-devel] Yet another bug for the bug list
by Christophe Rhodes 21 Feb '05

21 Feb '05

Hi, I'm sure most of you know this already, but windows opened by OPEN-WINDOW-STREAM are not automatically closed when their parent is closed, even if they share the same event queue -- and once the parent is gone it is then impossible to close them short of destroying the port. (This has UI implications in my climacs/tabcode app.) Cheers, Christophe

4 7

[mcclim-devel] Re: image:write-pnm doesn't work with SBCL 0.8.17
by Christophe Rhodes 21 Feb '05

21 Feb '05

Milan Zamazal <pdm(a)zamazal.org> writes: > Image writing in Backends/CLX/image.lisp breaks with SBCL 0.8.17. The > output streams there are character streams, so if the environment is a > UTF-8 environment for instance, then the output stream is recoded and > the resulting image is broken. Can you try the attached? I haven't altered the cut-and-paste code in Backend/Beagle/; anyone who cares should probably see if the code is identical and if so refactor. In addition, someone who cares about pnm might want to make read-image-file and write-image-file or write-pnm logical inverses of each other -- I haven't tested the attached at all beyond compiling it because I have no idea how it should be used. Maybe if someone who uses it attempts to document it, it will make more sense? Cheers, Christophe

2 2

[mcclim-devel] problems with the implementation of the layout protocol
by Robert Strandh 19 Feb '05

19 Feb '05

Hello everyone, As far as I can tell, there are two major problems with the current implementation of the layout protocol: * First, compose-space and change-space-requirements have :before, :after, or :around methods that are essential for the implementation to work. The consequences of this way of doing it (it seems to me) is that client code that wishes to change the default behavior or override it in subclasses of standard CLIM layout panes cannot do so without being aware of the existence of these methods. * Second, change-space-requirements always calls itself on the parent pane. However, the definition of the restraining-pane is that it should stop propagation of change-space-requirement. After discussions with Andy Hefner, we conclude that change-space-requirement should call note-space-requirement-changed, which in turn calls change-space-requirement on its parent, unless overridden. These points make it hard to implement the restraining pane, which is probably why it is not implemented, even though it ought to be fairly easy. -- Robert Strandh --------------------------------------------------------------------- Greenspun's Tenth Rule of Programming: any sufficiently complicated C or Fortran program contains an ad hoc informally-specified bug-ridden slow implementation of half of Common Lisp. ---------------------------------------------------------------------

1 0

[mcclim-devel] Gadgets within accepting-values
by Anthony Juckel 17 Feb '05

17 Feb '05

Along the same lines as my previous email, I'm having trouble getting a gadget to display within an accepting-values dialog. Apparently the problem arises because setup-gadget-record is being called on the accepting-values-stream, and the first thing setup-gadget-record wants to do is set the height of the accepting-values-stream sheet. Unfortunately, accepting-values stream has no height slot. I'm still rather unclear about the internal workings of accepting-values, so I'm not brave enough to offer a solution, but I thought I could at least notify the list of the problem. Anthony W. Juckel Full disclosure: McCLIM was checked out and recompiled (after removing old fasls) this evening. 0: ((SB-PCL::FAST-METHOD SLOT-MISSING (T T T T)) #<unavailable argument> #<unavailable argument> #<unavailable argument> #<CLIM-INTERNALS::ACCEPTING-VALUES-STREAM {90B1EC1}> CLIM-INTERNALS::HEIGHT SLOT-VALUE NIL) 1: ("XEP for (SB-PCL::FAST-METHOD SLOT-MISSING (T T T ...))" 7 #<unavailable argument> #<unavailable argument> #<unavailable argument> #<CLIM-INTERNALS::ACCEPTING-VALUES-STREAM {90B1EC1}> CLIM-INTERNALS::HEIGHT SLOT-VALUE NIL)[:EXTERNAL] 2: (SLOT-VALUE #<CLIM-INTERNALS::ACCEPTING-VALUES-STREAM {90B1EC1}> CLIM-INTERNALS::HEIGHT) 3: (CLIM-INTERNALS::SETUP-GADGET-RECORD #<CLIM-INTERNALS::ACCEPTING-VALUES-STREAM {90B1EC1}> #<CLIM:GADGET-OUTPUT-RECORD X 0.0d0:0.0d0 Y 0.0d0:0.0d0 {90B5AC9}> 0 0) 4: ("FLET #:ACCEPTING-VALUES-CONTINUATION0" #<CLIM-INTERNALS::ACCEPTING-VALUES-STREAM {90B1EC1}>) 5: ("FLET #:UPDATING-OUTPUT-CONTINUATION415" #<CLIM:APPLICATION-PANE NET.JUCKEL.EXALTED.CLIM::INSPECTOR {A722651}>) 6: ((SB-PCL::FAST-METHOD CLIM:INVOKE-WITH-NEW-OUTPUT-RECORD (CLIM:OUTPUT-RECORDING-STREAM T T T)) #<unavailable argument> #<unavailable argument> #<CLIM:APPLICATION-PANE NET.JUCKEL.EXALTED.CLIM::INSPECTOR {A722651}> #<FUNCTION "CLOSURE" {90B3FFD}> #<unavailable argument> #<FUNCTION "FLET #:CONSTRUCTOR1076" {26F203D}> NIL) 7: (CLIM-INTERNALS::%INVOKE-UPDATING #<CLIM-INTERNALS::ACCEPTING-VALUES-RECORD X 0.0d0:0.0d0 Y 0.0d0:0.0d0 1 {90B32A1}> #<CLIM:APPLICATION-PANE NET.JUCKEL.EXALTED.CLIM::INSPECTOR {A722651}> #<FUNCTION "CLOSURE" {90B1F45}>) 8: ("FLET #:CONTINUATION2071" #<CLIM:APPLICATION-PANE NET.JUCKEL.EXALTED.CLIM::INSPECTOR {A722651}> #<CLIM-INTERNALS::ACCEPTING-VALUES-RECORD X 0.0d0:0.0d0 Y 0.0d0:0.0d0 1 {90B32A1}>) 9: ((SB-PCL::FAST-METHOD CLIM:INVOKE-WITH-NEW-OUTPUT-RECORD (CLIM:OUTPUT-RECORDING-STREAM T T T)) #<unavailable argument> #<unavailable argument> #<CLIM:APPLICATION-PANE NET.JUCKEL.EXALTED.CLIM::INSPECTOR {A722651}> #<FUNCTION "CLOSURE" {90B2755}> #<unavailable argument> #<FUNCTION "CLOSURE" {90B2725}> (:UNIQUE-ID 1 :ID-TEST #<FUNCTION "top level local call EQL" {1076E65}> :CACHE-VALUE CLIM-INTERNALS::NO-CACHE-VALUE :CACHE-TEST #<FUNCTION CLIM-INTERNALS::FORCE-UPDATE-CACHE-TEST> :FIXED-POSITION NIL ...)) 10: ((SB-PCL::FAST-METHOD CLIM:INVOKE-UPDATING-OUTPUT (CLIM-INTERNALS::UPDATING-OUTPUT-STREAM-MIXIN T T T T T T)) #<unavailable argument> #<unavailable argument> #<CLIM:APPLICATION-PANE NET.JUCKEL.EXALTED.CLIM::INSPECTOR {A722651}> #<FUNCTION "CLOSURE" {90B1F45}> CLIM-INTERNALS::ACCEPTING-VALUES-RECORD (NIL) #<FUNCTION "top level local call EQL" {1076E65}> CLIM-INTERNALS::NO-CACHE-VALUE #<FUNCTION CLIM-INTERNALS::FORCE-UPDATE-CACHE-TEST> NIL) 11: ("varargs entry for CLIM-INTERNALS::INVOKE-ACCEPTING-VALUES" #<CLIM:APPLICATION-PANE NET.JUCKEL.EXALTED.CLIM::INSPECTOR {A722651}> #<FUNCTION "CLOSURE" {9010C15}> :OWN-WINDOW #<unused argument> :EXIT-BOXES #<unused argument> :INITIALLY-SELECT-QUERY-IDENTIFIER NIL :MODIFY-INITIAL-QUERY #<unused argument> :RESYNCHRONIZE-EVERY-PASS NIL :RESIZE-FRAME #<unused argument> :ALIGN-PROMPTS NIL :LABEL #<unused argument> :SCROLL-BARS #<unused argument> :X-POSITION #<unused argument> :Y-POSITION #<unused argument> :WIDTH #<unused argument> :HEIGHT #<unused argument> :COMMAND-TABLE CLIM:ACCEPTING-VALUES :FRAME-CLASS #<unused argument>) 12: ((SB-PCL::FAST-METHOD CLIM:DEFAULT-FRAME-TOP-LEVEL (CLIM:APPLICATION-FRAME)) #<unavailable argument> #<unavailable argument> #<NET.JUCKEL.EXALTED.CLIM::EXALTED-CLIM {9EEE7D1}> NIL) 13: ("XEP for (SB-PCL::FAST-METHOD CLIM:DEFAULT-FRAME-TOP-LEVEL (CLIM:APPLICATION-FRAME))" 4 #<unavailable argument> #<unavailable argument> #<NET.JUCKEL.EXALTED.CLIM::EXALTED-CLIM {9EEE7D1}> NIL)[:EXTERNAL] 14: ((SB-PCL::FAST-METHOD CLIM:RUN-FRAME-TOP-LEVEL (CLIM:APPLICATION-FRAME)) #<unavailable argument> #<unavailable argument> #<NET.JUCKEL.EXALTED.CLIM::EXALTED-CLIM {9EEE7D1}> #<unavailable argument>) 15: ((SB-PCL::FAST-METHOD CLIM:RUN-FRAME-TOP-LEVEL :AROUND (CLIM:APPLICATION-FRAME)) #<unavailable argument> #S(SB-PCL::FAST-METHOD-CALL :FUNCTION #<FUNCTION (SB-PCL::FAST-METHOD CLIM:RUN-FRAME-TOP-LEVEL #) {26DFF05}> :PV-CELL NIL :NEXT-METHOD-CALL NIL :ARG-INFO (1 . T)) #<NET.JUCKEL.EXALTED.CLIM::EXALTED-CLIM {9EEE7D1}> NIL) 16: ("LABELS CLIM-INTERNALS::BOING") 17: ("#'(LAMBDA NIL (LET # # ...) ...)") 18: ("foreign function: call_into_lisp") 19: ("foreign function: funcall0")

2 1