--- In [email protected], "entropyreduction" 
<alancampbelllists+ya...@...> wrote:
> 
> --- In [email protected], "Sheri" <sherip99@> wrote:
> >
> > 
> > Don't know what you mean by propttype. Doing what I outlined above
> 
>   function x(anArg, anotherArg)
> 
> is the prototype of function x: anArg, anotherArg are prototype
> argument list.
> 
> > I get:
> > 
> > ERROR: com.method: Object handle, isn't
> > 
> > when I try to use the handle
> 
> Try COMplugin0.72_091130.zip in the usual
> 
> http://tech.groups.yahoo.com/group/power-pro/files/0_TEMP_/AlansPluginProvisional/
> 
> Fixed localcopy
> 
> added com_type for create_object, get_object, etc
> 
> added unicode_args_allowed, return_unicode_strings and associated
> config ini keys:
> comPluginDemoScriptFileSysObjDotSyntaxForEach.powerpro
> illustrates 
> rtf updated, not finished; pdf, chm not yet updated
>

In my usage, unicode arguments and returns do not work with this version. 
Unicode arguments still work with previous version (both carrying com.version 
.72 unfortunately). BTW, I think in addition to having ability to set the 
unicode enablers, we should also have functions to retrieve the current 
settings.

Whether enabled or disabled, unicode handles are seen as handle labels (in 
arguments), and returns are also ansi.

e.g., for win.debug(myselect.contents), I expect to see a unicode handle. 
Instead I see the ascii text of the contents.

I am no longer using the handle form for appRef.Search because I had to switch 
to method_typed. Turned out of some of the material that needed to be seen as 
strings was composed entirely of digits.

With previous version: Unicode handles worked in method_typed and handle.method 
(as long as none of the "strings" was all numbers). With appRef.Search I got 
exceptions when "strings" got seen as numbers in non-unicode arguments. Same 
tests with unicode arguments did not get com exception errors, but also didn't 
process properly until I switched to method_typed.

I did try your comPluginDemoScriptFileSysObjDotSyntaxForEach.powerpro and it 
did seem to work, so I don't know why my script doesn't work with today's 
version.

Although Powerpro auto-localcopy does work when sending a com handle to another 
Powerpro function, what I really want is to return a local handle via 
quit(handle). Using v=com.localcopy(appRef), if I quit v, it is the string 
"OK". If I quit(appRef), when I try to use it on the other end I get ERROR: 
com.method: Object handle, isn't. Can just avoid locals.

Regards,
Sheri

Reply via email to