Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!cica!iuvax!uxc.cso.uiuc.edu!csd4.milw.wisc.edu!lll-winken!arisia!cdp!dantz
From: dantz@cdp.UUCP
Newsgroups: comp.sys.mac
Subject: Re: Possible RETROSPECT bug
Message-ID: <141200061@cdp>
Date: 20 Jul 89 18:18:00 GMT
References: <1478@xn.ll.mit.edu>
Lines: 40
Nf-ID: #R:xn.ll.mit.edu:1478:cdp:141200061:000:1569
Nf-From: cdp.UUCP!dantz    Jul 20 11:18:00 1989



John,

Dantz is here, under the name "dantz" . I just saw 
your message this morning, and have checked out the problem. 
You did find a small bug in Retrospect in the Save Highlights 
area as follows: 

If you try to replace a save highlights selector that is in use 
by creating a new one with the same name, the first selector 
is not replaced and no warning is given. 

The intended behavior is to not allow you to replace a selector 
that is in use. This will be fixed in the next version. This 
would be consistent with the existing selector architecture which 
does not allow you to delete a selector that is in use. What 
is really happening when you save a new selector with the same 
name as an existing one is that the first one is deleted and 
the second one is created. Because of this, in the next version 
of Retrospect, an alert would appearing saying "The selector xxxx 
could not be deleted because it is in use." 


The best way to work around this is to create a new selector 
when you want to change what gets excluded from the backup, put 
it into your "Full Backup" selector, and then remove and clear 
the old selector. 

Thanks for taking the time to put up such a detailed description 
of how to reproduce it. I was able to figure out the problem
very quickly. Let me know if you have any other problems or 
questions. And, as I said, we will definitely fix this in the 
next version. 

Walt

Walt Hays                  /  CIS:        73367,2416
Technical Support          /  Connect:    dantz
Dantz Development Corp.    /  AppleLink:  D0011