Okay, Well, I can't remember where I got that portable version. It seems to do
little more than filter out a few registry entries which PP makes (5 or 6).
But I think those portable setups slow things down and complicate issues. If
you are unaware of a portable version, then I will try to make PP run on my
thumbdrive by itself. As for the other problems, I attribute part of it to
poor coding (my own problem) and part to the new usb drive (which I am
returning...). Thanks for the tip about clearing the cache.
--- In power-pro@yahoogroups.com, "brucexs" <bruc...@...> wrote:
>
>
>
> --- In power-pro@yahoogroups.com, "brother.gabriel" <brgabriel@> wrote:
> >
> > Hello, y'all!
> >
> > I use Powerpro portable on my usb drive, but I always have problems with
> > it. For example, I add win.debug(somevariable) to a function and call it.
> > Okay, it gives me the value. Then I delete win.debug from the script and
> > call it again. The win.debug remains! But it isn't even in the script!
> >
> > Must I use the portable version for PP or can I just use regular PP?
> >
>
> The only explanation I can see for this is as follows: PowerPro keeps a copy
> of scripts in memory to save time running them. It tries to detect whether
> the file containing the script has changed each time the script is started,
> but some people have said that it fails to do so in some cases (I have never
> seen this in my tests). Pls make sure you updated the actual file where the
> script was loaded from.
>
> If that does not solve the issue, then you can have a hot key which runs this
> command
> exec.scriptcache("clear")
> which will clear all scripts from memory and force a load from the file.
>
> There is no special portable version of PPro that I am aware of, although I
> know some people have developed configuration hints to use it effectively
> from a portable drive.
>
