--- In [email protected], "Sheri" <sheri...@...> wrote:
>
> > Can either provide typeName service or add function to get_description e.g.
> > han.description("name")
> > I have to try to avoid service names that might conflict with
> > names of object methods. E.g. Name is probably a bad idea, cause
> > I bet there are a fair number of COM objects exposing a Name
> > method.
>
> OK, however you think best to name it, etc. Just at least mention in the docs
> that it does what vbscript's typeName function does.
Okay.
> Javascript btw calls it constructor.name. But according to the documentation,
> Javascript has a complication related to items in a collection, in that the
> item gets identified as an item of the type of the collection. So there is a
> workaround if using Javascript wherein you first have to do something with
> getElements().
Don't think that'll come up. Gimme a handle, I'd do
queryInterface and then GetTypeInfo, then GetDocumentation, pBstrName arg is
what you're after.
While I'm there,
http://msdn.microsoft.com/en-us/library/ms221227.aspx
do the pBstrDocString, pdwHelpContext or
pBstrHelpFile look potentially useful?
> New problem. Brother Gabe wants to process unicode strings. The
> documentation says that with vbscript, unicode strings work in
> the method we are processing because most vbscript editors
> support unicode. So I guess it might be possible to do it here.
> In the com plugin doc you say, "I have not currently dealing with
> UNICODE strings either in service parameters or results. I can
> probably do so by establishing connections between this plugin
> and the unicode plugin if there's demand."
Yeah, but not gonna happen very fast. I can do typeName thing pretty quickly:
adding unicode support will take rather more fiddling.
> In this particular case we would need to be able to send unicode in arguments.
To do it right gonna have to at least prepare for sending in unicode args and
getting back unicode results.
