March 2007 - graphic-forms-devel@lists.common-lisp.net

[graphic-forms-devel] Undefined alien: "func_ptr"
by David Lichteblau 30 Mar '07

30 Mar '07

Hi, I get this error when trying to build graphic-forms-uitoolkit with SBCL 1.0.2 on Windows XP. d. Undefined alien: "func_ptr" [Condition of type UNDEFINED-ALIEN-ERROR] Restarts: 0: [RETRY] Retry performing #<ASDF:LOAD-OP NIL {A8AF309}> on #<ASDF:CL-SOURCE-FILE "metrics" {B31B561}>. 1: [ACCEPT] Continue, treating #<ASDF:LOAD-OP NIL {A8AF309}> on #<ASDF:CL-SOURCE-FILE "metrics" {B31B561}> as having been successful. 2: [ABORT] Return to SLIME's top level. 3: [CLOSE-CONNECTION] Close SLIME connection 4: [ABORT] Exit debugger, returning to top level. Backtrace: 0: (SB-SYS:ENSURE-DYNAMIC-FOREIGN-SYMBOL-ADDRESS "func_ptr" #<unused argument>) 1: (SB-IMPL::LINK-FOREIGN-SYMBOL "func_ptr" NIL) 2: (SB-IMPL::ENSURE-FOREIGN-SYMBOL-LINKAGE "func_ptr" NIL) 3: (SB-SYS:FOREIGN-SYMBOL-ADDRESS "func_ptr" NIL) 4: (SB-FASL::FOP-FOREIGN-FIXUP) 5: (SB-FASL::LOAD-FASL-GROUP #<SB-SYS:FD-STREAM for "file C:\\cygwin\\home\\david\\clbuild\\source\\graphic-forms\\src\\uitoolkit\\system\\metrics.fasl" {BC57C79}>) 6: (SB-FASL::LOAD-AS-FASL #<SB-SYS:FD-STREAM for "file C:\\cygwin\\home\\david\\clbuild\\source\\graphic-forms\\src\\uitoolkit\\system\\metrics.fasl" {BC57C79}> NIL #<unavailable argument>) 7: (SB-FASL::INTERNAL-LOAD #P"C:\\cygwin\\home\\david\\clbuild\\source\\graphic-forms\\src\\uitoolkit\\system\\metrics.fasl" #P"C:\\cygwin\\home\\david\\clbuild\\source\\graphic-forms\\src\\uitoolkit\\system\\metrics.fasl" :ERROR NIL NIL :BINARY NIL) 8: (SB-FASL::INTERNAL-LOAD #P"C:\\cygwin\\home\\david\\clbuild\\source\\graphic-forms\\src\\uitoolkit\\system\\metrics.fasl" #P"C:\\cygwin\\home\\david\\clbuild\\source\\graphic-forms\\src\\uitoolkit\\system\\metrics.fasl" :ERROR NIL NIL NIL :DEFAULT) 9: (LOAD #P"C:\\cygwin\\home\\david\\clbuild\\source\\graphic-forms\\src\\uitoolkit\\system\\metrics.fasl") 10: ((SB-PCL::FAST-METHOD ASDF:PERFORM (ASDF:LOAD-OP ASDF:CL-SOURCE-FILE)) #<unavailable argument> #<unavailable argument> #<ASDF:LOAD-OP NIL {A8AF309}> #<ASDF:CL-SOURCE-FILE "metrics" {B31B561}>) 11: ((LAMBDA (SB-PCL::.PV-CELL. SB-PCL::.NEXT-METHOD-CALL. SB-PCL::.ARG0. SB-PCL::.ARG1.)) #<unavailable argument> #<unavailable argument> #<ASDF:LOAD-OP NIL {A8AF309}> #<ASDF:CL-SOURCE-FILE "metrics" {B31B561}>) 12: ((LAMBDA ())) 13: (SB-C::%WITH-COMPILATION-UNIT #<CLOSURE (LAMBDA #) {AC447C5}>) 14: (NIL ASDF:LOAD-OP :GRAPHIC-FORMS-UITOOLKIT) 15: (ASDF::MODULE-PROVIDE-ASDF :GRAPHIC-FORMS-UITOOLKIT) 16: ((LAMBDA (#:G21)) ASDF::MODULE-PROVIDE-ASDF) 17: (SB-IMPL::%MAP-FOR-EFFECT-ARITY-1 #<CLOSURE (LAMBDA #) {B3FDFE5}> (ASDF::MODULE-PROVIDE-ASDF SB-IMPL::MODULE-PROVIDE-CONTRIB)) 18: (REQUIRE :GRAPHIC-FORMS-UITOOLKIT NIL) 19: (SB-INT:SIMPLE-EVAL-IN-LEXENV (REQUIRE :GRAPHIC-FORMS-UITOOLKIT) #<NULL-LEXENV>) --more--

2 7

Available widgets (was: Re: [graphic-forms-devel] Dialogs return values)
by Edgar Gonçalves 25 Mar '07

25 Mar '07

On 3/25/07, Jack Unrue <jdunrue(a)gmail.com> wrote: > On 3/25/07, Edgar Gonçalves <edgar.goncalves(a)gmail.com> wrote: > > > > Hi! I've just started playing with graphic-forms, and I wanted to > > build some macros to generate message-boxes (which I did based on your > > demo about-dialog), and some input-prompts, like Yes/No questions, or > > a simple OK/Cancel. But I'm not figuring how I can set a return value > > for such functions (they seem to return the value 4 once (gfw:show dlg > > t) is called). Right now I managed a dirty hack by placing a global > > variable and making the dialog change it. but this is not as > > functional as I would want... Any suggestions? > > > > Hi Edgar. Your macros could be written to establish a lexical binding > and then use a closure as a callback for each widget in the dialolg. > Or you could define a new dispatcher class and specify that for each > widget, with one or more slots carrying important return info. You > might consider constructing your macros such that the user of the > macro provides one or more symbols to identify bindings whose values > are to carry whatever result info your dialogs will provide, which can > then be accessed within the body of the macro. The WITH-* macros > for the color, file, and font dialogs work this way. > > The exact return value of GFW:SHOW is whatever the underlying > window system returns -- I might change the function to return (values) > just to emphasize that it's not a value that the application can use. > But you could obviously implement a wrapper around GFW:SHOW if > you wanted a function-based API. > That's what I was getting at. I'll make some wrappers to do it. On another subject, the list of controls you make available in graphic-forms is still limited. Is that because you haven't needed more, yet, or are there technical impediments? I would like to use most of the controls in MFC - http://msdn2.microsoft.com/en-us/library/47xcww9x(VS.80).aspx -, do you have some quick recipe ready for this? It'd be great to share user's widgets! Thanks again for the help! -- Edgar Gonçalves Instituto Superior Técnico, INESC-ID - Software Engineering Group, Portugal

2 1

[graphic-forms-devel] Dialogs return values
by Edgar Gonçalves 25 Mar '07

25 Mar '07

Hi! I've just started playing with graphic-forms, and I wanted to build some macros to generate message-boxes (which I did based on your demo about-dialog), and some input-prompts, like Yes/No questions, or a simple OK/Cancel. But I'm not figuring how I can set a return value for such functions (they seem to return the value 4 once (gfw:show dlg t) is called). Right now I managed a dirty hack by placing a global variable and making the dialog change it. but this is not as functional as I would want... Any suggestions? Thanks, -- Edgar Gonçalves Instituto Superior Técnico, INESC-ID - Software Engineering Group, Portugal

2 1