Can you try latest exe
http://powerpro.webeddie.com/download/powerpro.exe >From my testing, it seems to fix the reference error on the collection object >specified after for each. Can you also omit the objfile = "" from your script and verify via debug or trace from your plugin that references creates by objfile are deleted (last one not until script exits). --- In [email protected], "entropyreduction" <alancampbelllists+ya...@...> wrote: > > > > --- In [email protected], "brucexs" <brucexs@> wrote: > > > > I don't know how the ref count for the enumeration handle got set to > > > > two. > > > I do now based on above. > > > PowerPro creates a hidden internal local variable to keep resujlts of > > whatever expression is on the right hand side of the "in" (in this case, it > > is just hCollectionFiles). Although it will get released at end of > > function (since it is a local), (or it should, at least), it would probably > > be better if I assigned "" to that internal variable at the end of for loop > > causing a release. I'll look into that on the weekend or early next week. > > That sounds like it. Fix whenever. I'm away from compiler now til early > next week. > > I had time to a bit of debugging this afternoon. Put a breakpoint in > refcallback registered with > > ppsv->SetChangeRefCallback(.., refcallback,...) > > refcallback is called twice on the collection handle > to increment; both times before the forEach registered callback is called > > refcallback never called on the collection to decrement > > Interestingly refcallback never called on quit (to get rid of locals); but I > guess you don;t need to, cause if you're blasting them out of existence as > they go out of scope, who cares what their ref count is. >
