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

[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] space requirements :min-:max options
by Clemens Fruhwirth 04 Jan '06

04 Jan '06

According to the CLIM spec 29.3.1 Layout Pane Options: "If either of the :max-height or :min-height options is not supplied, it defaults to the value of the :height option." However in panes.lisp, I see: ;; NOTE: The defaulting for :min-foo and :max-foo is different from MAKE-SPACE-REQUIREMENT. ;; MAKE-SPACE-REQUIREMENT has kind of &key foo (min-foo 0) (max-foo +fill+) ;; While user space requirements has &key foo (min-foo foo) (max-foo foo). ;; I as a user would pretty much expect the same behavior, therefore I'll take the ;; following route: ;; When the :foo option is given, I'll let MAKE-SPACE-REQUIREMENT decide. May I urge you to change revert that change. The :height and :width initargs loss their usefulness this way. Also it's a bit counter-intutive. Look at (define-application-frame only-red () () (:pane (vertically () (make-pane 'application-pane :background +red+ :min-height 100) +fill+ (make-pane 'application-pane :background +blue+ :height 100)))) Wouldn't you expect to see two panes, one blue with height 100 and a red one at least 100 pixel high? The reason for this query is that I have troubles explaining the readers of my CLIM tutorial why McCLIM violates the spec and why :height as well as :width are mostly useless at the moment. See panes.lisp "merge-one-option" (Line 549) and the commented code ;; (setf user-max-foo (or user-max-foo user-foo) ;; user-min-foo (or user-min-foo user-foo)) Thanks, -- Fruhwirth Clemens - http://clemens.endorphin.org for robots: sp4mtrap(a)endorphin.org

1 0

[mcclim-devel] repaint-sheet, +everywhere+ and output recording
by Clemens Fruhwirth 02 Jan '06

02 Jan '06

(repaint-sheet instance-inheriting-from-output-recording-stream +everywhere+) does not work. The reason is %handle-repaint in recording.lisp. It rewrites region to a bounding-rectangle regardless the type of the region. Hence, %handle-repaint needs to check whether region is region-equal to +nowhere+ or +everywhere+, the only unbounded region types that do not participate in the bounding rectangle protocol. Please comment on my patch, because I personally don't like it. It seems a bit ackward to make explicit checks for these two regions, probably there are better solutions. If you need something to reproduce the bug, try http://paste.lisp.org/display/15284#3 - uncomment standard-output-recording-stream from the long list of superclasses that imitate those of application-pane to reproduce the error. -- Fruhwirth Clemens - http://clemens.endorphin.org for robots: sp4mtrap(a)endorphin.org

1 0

[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

Re: with-output-as-gadget (was Re: [mcclim-devel] Missing realizer in
by pw＠snoopy.mv.com 23 Dec '05

23 Dec '05

> 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? The problem here is caused by the call to allocate-space in the initialize-instance :after on gadget-output-record. Not calling that results in no errors and a check-box gadget being displayed. I have no idea if this is an appropriate fix but hopefully this will provide food for thought for those that are in the know. Paul

1 0