Chipp Walters wrote:
On Sun, Sep 28, 2008 at 7:31 AM, Len Morgan wrote:
My problem is how to I get rid of this in-memory copy and replace it with
the new version (assuming that I had to download a new version)?
Is it as simple as:
if tVersionUpdated then
stop using tCurrentStack
end if
The application browser needs to be manually refreshed for the latest
info. Look for a little icon at the bottom of the scrollbar that will
refresh the list.
After checking all the versions of my stacks, I opened the
Application Browser and the only stacks showing were ones that had
actually
I'd say the Application Browser is the last place to look at for
verifying the existence of running stacks in rev. But you are right
about the need for a current stack to revert, but if it's the current
stack then it's always in memory. To change the current stack, you can
use the defaultSt
Try the revert command, it's perfect for this, assuming you do replace
the stacks on the hard disk, and are not creating new files.
On 28 Sep 2008, at 14:31, Len Morgan wrote:
This sounds like what I'm after but when I tried this, I observed something
that may throw a monkey wrench (spanne
On Sun, Sep 28, 2008 at 7:31 AM, Len Morgan <[EMAIL PROTECTED]> wrote:
> My problem is how to I get rid of this in-memory copy and replace it with
> the new version (assuming that I had to download a new version)?
>
> Is it as simple as:
>
> if tVersionUpdated then
> stop using tCurrentStack
> e
Try the revert command, it's perfect for this, assuming you do replace
the stacks on the hard disk, and are not creating new files.
On 28 Sep 2008, at 14:31, Len Morgan wrote:
I'm back again with an "autoupdater" question. I have an
application that is made up of a bunch of stacks. Each st
