RS> The previous default behavior was removed because not every RS> application wanted it (it was a rather implementation-oriented RS> feature).
Thanks. I understand and sympathize. But is there some easy recipe to get this behavior back? Either to get it for a whole application (my biggest use for McCLIM was for debugging tools), or for particular objects?
You could have your presentation types subclass a presentation type for which you have a command, say com-describe-object, and then have a presentation translator (DEFINE-PRESENTATION-TO-COMMAND-TRANSLATOR) on the superclass and middle button (:describe gesture) to invoke it.
Paul
RS> The previous default behavior was removed because not every RS> application wanted it (it was a rather implementation-oriented RS> feature).
I apologize if this is another dumb question, but wouldn't it be reasonable to allow McCLIM programmers to choose whether or not they want the old default behavior by encapsulating it in a command-table, and allowing the programmer to decide whether or not that behavior is what s/he wants?
Possibly there would also have to be a presentation type defined that we could adopt as a mixin in order to get this default behavior from a mouse click.
I'm probably just whining --- that old default behavior + graphing (format-graph-from-roots) was all I wanted for a debugger app, and now it seems like a fairly substantial amount of programming + grokking CLIM is required to recover what I used to get in about 30 loc....
One thing that still puzzles me is that there seems to be some "Describe" functionality still there, but it doesn't seem happy with ordinary presentations. Indeed, I can't get it to work at all (at least on ACL 6.2). Nothing I seem to type into the prompt box (including simple integers) does anything I recognize when I press Exit.
R
Today, rpgoldman@sift.info wrote:
RS> The previous default behavior was removed because not every RS> application wanted it (it was a rather implementation-oriented RS> feature).
I apologize if this is another dumb question, but wouldn't it be reasonable to allow McCLIM programmers to choose whether or not they want the old default behavior by encapsulating it in a command-table, and allowing the programmer to decide whether or not that behavior is what s/he wants?
Sorry if I'm missing the point of this thread, but at least on McCLIM 0.9.1, I can still access the "describe presentation" command by left-clicking on the presentation while holding the Super key.
Granted, it's not in the most accessible places on many keyboards, but it's available so it should be possible to re-map if you need it somewhere else.
Good luck,
"asf" == Andreas Fuchs asf@boinkor.net writes:
asf> Today, rpgoldman@sift.info wrote: RS> The previous default behavior was removed because not every RS> application wanted it (it was a rather implementation-oriented RS> feature). >> >> I apologize if this is another dumb question, but wouldn't it be >> reasonable to allow McCLIM programmers to choose whether or not they >> want the old default behavior by encapsulating it in a >> command-table, and allowing the programmer to decide whether or not >> that behavior is what s/he wants?
asf> Sorry if I'm missing the point of this thread, but at least on McCLIM asf> 0.9.1, I can still access the "describe presentation" command by asf> left-clicking on the presentation while holding the Super asf> key.
Perhaps the problem's at my end. I do not seem to be able to do this (although I have a super key defined, AFAICT). Further, when I explicitly add a menubar with "Describe presentation" on it:
(make-command-table 'debug-command-table :errorp nil :menu '(("Describe presentation" :command com-describe-presentation) ("Describe object" :command com-describe-object)))
(make-command-table 'menubar-command-table :errorp nil :menu '(("Describe" :menu debug-command-table)))
The "Describe presentation" menu item appears grayed out and seems inactive. I'm using a copy I pulled from CVS yesterday (and rebuilt from source).
Can anyone correct me on this?
R