--- In [email protected], "Sheri" <sheri...@...> wrote: > > --- In [email protected], "entropyreduction" > <alancampbelllists+yahoo@> wrote: > > > > Just a change in com.object_description; can now take any of > > > > n show name > > d show description > > f show functions > > p show parameters for each function (ignored if f absent) > > t show return type and function parameters (ignored if f absent, > > latter ignored ignored if p absent) > > h get help strings for each function (ignored if f absent) > Problematic. "f" by itself generates an error. It no longer seems to be > possible to get the functions together with parameters and their types as > shown below (generated with "fdn" of an appRef.Selection using previous test > version).
So "fpt" doesn't work? "f" works on my machine: OTOH as usual I'm always tinkering, so maybe what was in 0.72 091204 isn't what I got. > Not sure what previous version did for optional parameters (hopefully > indicated in some way). Not indicated. I've just figured out how to get relevant flags, will test and post Monday. Also IN and OUT flags possible. Formatting is up for neogtiation. At moment is C-ish. Could be more VB-ish e.g. Objects* ItemByRange(VARIANT from, VARIANT to) => ItemByRange(from As VARIANT, to as VARIANT) As Objects* > Would be nice to be able to get a similar listing to that below plus the help > string. Where requested, IMO the help string should be delimited by a new > line (not a semicolon). That'll be harder to parse, surely, in that can no longer use line function to get everything to do with one function. How about a tab before help string. I'm pretty sure each parameter has a description string as well, but haven't figures out to to grab it. Can deal with it (e.g., with replacechars), but it would also be nice if get_object_description used CRLFs instead of LFs when it makes new lines. Done.
