--- In [email protected], "Derek" <delwo...@...> wrote: > > I can either > > > > (1) new plugin could convert every powerpro ANSI string > > to unicode; any scripts now using autoit plugin should work > > unchanged > > > > (2) new plugin could expect only handles to unicode strings > > generated by unicode plugin; less wrok for me, but would > > require user to get and master unicode plugin, and change > > existing scripts > > > > (3) new plugin could check for handles to unicode strings; > > if found, process, otherwise assume standard ANSI string and > > convert to unicode. This is most work for me.
> > Any preferences? > I would prefer aption 2 as: > (1) I dont want you to have to work too hard OTOH keeps me off streets and out of trouble. > (2) We users of you (free) efforts shouldnt mind working a bit ourselvs Just depends if there's anyone wedded to autoit who doesn;t want to learn yet another plugin. But I suspect anyone far enough gone to know about autoit and be writing pp scripts probably not much bothered by how many plugins they use. > My only request would be that the time you saved on just doing option 2 - > well in that case could you spend a little time including a simple text file > with a bit of help + example? Huh. Though there was an example already in the plugin distro. Just checked. There is. Okay, if that's not enough, how about you make up another one, or a more complicated one, and I'll chuck it in with next version. Docs: for most point automatically generated by Perl script from the autoit header file. I assume from that jumping off point you'd go back to the autoit dll docs E.g. AutoItX.chm in C:\Program Files\AutoIt3\AutoItX. Hmm. Now there's a point (he said having just bothred to read some of AutoItX.chm). In addition to a C/C++ interface, AutoItX3.dll provides a COM interface to exactly the same functions. So in principle I could forget updating autoit plugin, and everyone could just use the COM interface instead. What about that?
