Hello all!
As I have understood, it seems that :own-window t for accepting-values or NOTIFY-USER is not available yet in McCLIM. I really have my heart set on using a pop-up windows to manage prefs etc. but it seems non-trivial...
What I want to do is:
1 Create a child window 2A Populate with text-fields, checkboxes, and buttons (like gadet-test) 2B Add "Save" button and method that returns/stores the values selected 3 Move focus to child, put original window in background 4 Destroy child window, refocus on original window
It certainly seems possible looking at the Clim spec, but when I google it seems that I can't find much about it or examples. Sooo i am wondering if there is a reason for this...
So if anyone has a nice example* of how to do this that would be a dream, and if not the next best thing would be if someone had a clear understanding of how it should be donwe. And if not some vauge ideas on how to get started, and where to look would be excellent!
Thanks all!
/Peter
(*Even just a "About" pop-up example would be loveley!)
Peter Braroe peter.braroe@newsmachine.com writes:
As I have understood, it seems that :own-window t for accepting-values or NOTIFY-USER is not available yet in McCLIM. I really have my heart
As far as I know, McCLIM does support :own-window t for accepting-values.
What I want to do is:
1 Create a child window 2A Populate with text-fields, checkboxes, and buttons (like gadet-test) 2B Add "Save" button and method that returns/stores the values selected 3 Move focus to child, put original window in background 4 Destroy child window, refocus on original window
[...]
So if anyone has a nice example* of how to do this that would be a
One way to do that is by creating a full application frame for your dialog box with all the gadgets you need, and call it from your application code. It works nicely, but is rather verbose. Some time ago I posted an example here:
Poor man's CLIM text style selection dialog http://common-lisp.net/pipermail/mcclim-devel/2005-July/004113.html
Paolo
Hey!
Thanks! And that was quick!
I tried it and it worke great, nice little thing, now i have something to work from!
Regarding the accepting-values and :own-window. I didn't get that to work. Do I need to do something special to get a new window? The 0.9.1 spec said something about it beeing unimplemented so I didn't research it too much.
Here it says:
"There is no gadget-based implementation of accepting-values. own-window is not supported." http://common-lisp.net/pipermail/mcclim-announce/2005-March/000000.html
But now that I know it works I will try a bit harder to get it to work!
Thanks again!!
/Peter
On Mon, 2006-02-20 at 18:06 +0100, Paolo Amoroso wrote:
Peter Braroe peter.braroe@newsmachine.com writes:
As I have understood, it seems that :own-window t for accepting-values or NOTIFY-USER is not available yet in McCLIM. I really have my heart
As far as I know, McCLIM does support :own-window t for accepting-values.
What I want to do is:
1 Create a child window 2A Populate with text-fields, checkboxes, and buttons (like gadet-test) 2B Add "Save" button and method that returns/stores the values selected 3 Move focus to child, put original window in background 4 Destroy child window, refocus on original window
[...]
So if anyone has a nice example* of how to do this that would be a
One way to do that is by creating a full application frame for your dialog box with all the gadgets you need, and call it from your application code. It works nicely, but is rather verbose. Some time ago I posted an example here:
Poor man's CLIM text style selection dialog http://common-lisp.net/pipermail/mcclim-devel/2005-July/004113.html
Paolo
Peter Braroe peter.braroe@newsmachine.com writes:
Regarding the accepting-values and :own-window. I didn't get that to work. Do I need to do something special to get a new window? The 0.9.1 spec said something about it beeing unimplemented so I didn't research it too much.
Version 0.9.1 is quite old and a lot of progress has been made on McCLIM. I suggest that you get the latest CVS sources, which is currently the canonical way of using an up to date McCLIM.
Paolo
Paolo Amoroso amoroso@mclink.it wrote:
Peter Braroe peter.braroe@newsmachine.com writes:
Regarding the accepting-values and :own-window. I didn't get that to work. Do I need to do something special to get a new window? The 0.9.1 spec said something about it beeing unimplemented so I didn't research it too much.
Version 0.9.1 is quite old and a lot of progress has been made on McCLIM. I suggest that you get the latest CVS sources, which is currently the canonical way of using an up to date McCLIM.
Are there any plans release plans? It doesn't look as if there are many destabilizing merges are going on at the moment, so are there any arguments to just release a CVS snapshot as 0.9.2?
Of course, this violates some principals -- releases should receive a minimal amount of testing and so on -- however, as we point to the users to the CVS anyway, there is little to be lost.
Clemens Fruhwirth writes:
Are there any plans release plans? It doesn't look as if there are many destabilizing merges are going on at the moment, so are there any arguments to just release a CVS snapshot as 0.9.2?
Andreas Fuchs did the previous release and he probably had some idea as to what a release should be. At least it would be appropriate to ask him beforehand.
"RS" == Robert Strandh strandh@labri.fr writes:
RS> Clemens Fruhwirth writes: >> Are there any plans release plans? It doesn't look as if there are many >> destabilizing merges are going on at the moment, so are there any >> arguments to just release a CVS snapshot as 0.9.2?
RS> Andreas Fuchs did the previous release and he probably had some idea RS> as to what a release should be. At least it would be appropriate to RS> ask him beforehand.
How does this relate to Paolo's recent notes to the effect that the current CVS HEAD is broken for CMUCL?
Best, R
rpgoldman@real-time.com writes:
How does this relate to Paolo's recent notes to the effect that the current CVS HEAD is broken for CMUCL?
I don't know, because I only follow this discussion superficially. It would certainly be good if the latest release did not have that problem.
-
Clemens Fruhwirth -
Paolo Amoroso -
Peter Braroe -
Robert Strandh -
rpgoldman＠real-time.com