Hi Bruce,

both temp handle release and call() parsing seem fine now.  Thanks

forxtra: if first param of file_watchfolder is a unicode handl;e constructed on 
the fly, it won't now be valid when cmd(,) is invoked.

--- In [email protected], "brucexs" <bswit...@...> wrote:
>
> --- In [email protected], "entropyreduction" 
> <alancampbelllists+yahoo@> wrote:
> >
> > --- In [email protected], "brucexs" <bswitzer@> wrote:
> > >
> > >  win.debug(unicode.from_utf8("\xC3\x80"))
> > > > 
> > > > under your debugger and see what might be going on?
> > > > 
> > > > I'm pretty sure releasing temporary handles used to work. ...
> > 
> > > Looks like I broke this when I implemetned the ref counting for objects.
> >  
> > > Try the powerpro.exe uploaded to the usual folder (exe only).
> > 
> > Fixes problem, but now finds more parentheses than it should, e.g.
> > 
> >  call(s_sGuiFile, s_sIniFile, sSect, sAsk,  s_sPreamble, iSecsDelayToStart, 
> > iPostpone, sMin, sNote)
> 
> "About powerpro" says 4.9f2, right?
> > 
> > (all one line) in a script that's run fine until now now diagnosed with 
> > unbalanced parens.
> >
>


Reply via email to