22:14:08Inlinebut when i opened that file in climacs, without doing anything further, the file is displayed like there are no tabs, looks like it's all writ together words....
4:41:44lokeWhen defining a presentation method for CLIM:ACCEPT, what am I actually expected to do inside it? Bascially, if, in it, I decide that I'm done editing and X is the value to return.
4:42:13lokeSo, I return it... But nothing happens and once I click the entry box again, it calls my accept presentation method again
4:42:47lokeI have implemented a presentation method for a MAXIMA-FUNCTION-NAME (just a string, but with a presenbtation type that indicates that it's the anme of a maxima function)
4:43:10lokeSo this function then calls COMPLETE-INPUT to provide a completing version.
4:43:40lokeBut, I need to still be able to accept a user clicking on a function reference in the documentation, so I wrap it in an input context like this:
4:45:35loke(clim:with-input-context ('maxima-function-reference) (obj type ...) (clim:complete-input ...) #|here are the cases for w-i-c|# (maxima-function-reference (values (values XXXX 'maxiam-function-name))
4:45:47lokewhere XXX is the code to get the function name from a functionr eference object
4:46:18beachI am afraid your question is way beyond my knowledge of ACCEPT. :(
4:47:27beachAt this point, you know much more about CLIM than I do.
4:49:10lokeI've only ever used ACCEPT presentation methods which eventually regusively calls ACCEPT with some different paramteres.
4:49:39lokethere is some magic going on, and I've seen some code do (FUNCALL (CDAR *INPUT-CONTEXT*) magic-goes-here)
4:49:51lokethat seems to be highly suspicious to me :-)
4:50:49beachI see. Well, I don't think I was involved in writing any part of the presentation machinery, nor have I ever written an ACCEPT method I think. As I recal moore33 wrote all that stuff.