#lisp - Tue 6 Mar 2007 between 00:00 and 00:47

NY Lost Funds



slyrusmorning beach
rpghi, beach. Is your paper for ILC available to those of us who don't get to go?
actionrpg beats head on desk and groans...
rpgbeats head on desk and groans...
beachrpg: I would have to check the policy of ILC on that one before distributing something.
rpgbeach: OK, thanks. Hoping for fair use... ;-)
beach: One more question --- antifuchs told me that arguments to a command cannot be designated by pointer when reading a frame command.
Is this discussed anywhere that I could read (like on mcclim-devel), do you know?
And do you know if it's a problem with accepting-values or the command-parser proper?
beachrpg: I am afraid I haven't looked into that for a long time.
rpg: it must be a problem of a presentation-to-command translator taking priority, which it probably shouldn't.
rpgDo you know why antifuchs would say it's an accepting-values problem? I'm just looking for a hint or two...
I fixed a minor bug that made arguments not work, and now I'm hooked to pick off whatever else is wrong...
beachrpg: I am just guessing here, but unless you use accepting-values explicitly, I would not have thought the problem was there.
rpg: what happens when you try to select a command with the pointer?
rpg: oh, wait, maybe I am misunderstanding what you are saying.
rpgbeach: What I can't do is type in a command name, and then select the command's arguments with the pointer.
beachrpg: I thought you were saying that the arguments to your command is another command, and when you try to select that argument, you can't.
ah, ok. I did misunderstand.
rpgActually, my first test *was* a case where I was trying to select a command-name, but it turns out that this was just a specific instance of a general problem.
beachrpg: but you can select the arguments some other way.
rpgI can only select them by typing them in.
beachhmm, that used to work.
rpgIt's interesting, I went looking and I couldn't find any of the examples (I didn't look deeply into the applications) where anyone was using menu items with any arguments at all.
beach: I don't *believe* I could have messed it up. Let me see about another test...
beachare you selecting arguments from menus? As opposed to selecting them from some arbitrary visible presentation?
rpgNo some arbitrary visible presentation.
beachthat *definitely* used to work.
rpgE.g., I can use a presentation-to-command translator to do "describe" on graph nodes in my application.
s/describe/inspect/
But when I type "inspect", I get the text input box in my interactor window and now nothing on the screen's selectable...
except, weirdly, when I wave my mouse over the interactor window, I get the "select me" box around the command area in the interactor window.
rahulhow selfish of the command
what's the defintion of com-inspect?
beachrpg: OK, so the "input box" that you are talking about is the result of using accepting-values?
_deepfirebeach, another CLIM question: the spec says that open-w-s "Creates and returns a sheet that can be used as a standalone window that obeys CLIM's extended input and output stream and output recording protocols"
beach_deepfire: hold on a sec. I can only deal with one thing at a time.
lisppasterpg pasted "com-inspect-object" at http://paste.lisp.org/display/37769
rahulDESCRIBABLE? is that standard?
rpgbeach: I think so. AFAICT from the prompt, this is going pear-shaped inside make-partial-parser-fun
mppf has prompt "You are being prompted for arguments to ~S~%~%" and that's what I'm seeing.

Page: 2 9 16 23 30 

IrcArchive

NY Lost Funds