Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!mips!sgi!shinobu!odin!socrates.esd.sgi.com!eva
From: eva@socrates.esd.sgi.com (Eva Manolis)
Newsgroups: comp.sys.sgi
Subject: Re: keeping ftrs from overriding the dumpster ftr
Message-ID: <1990Nov8.005448.25815@odin.corp.sgi.com>
Date: 8 Nov 90 00:54:48 GMT
References: <3098@ns-mx.uiowa.edu>
Sender: news@odin.corp.sgi.com (Net News)
Reply-To: eva@socrates.esd.sgi.com (Eva Manolis)
Distribution: na
Organization: Silicon Graphics, Entry Systems Division
Lines: 64

In article <3098@ns-mx.uiowa.edu>, randy@tessa.iaf.uiowa.edu (randy frank) writes:
|> 
|> 	Here's my problem (It's amazing it didn't crop up till now!!):
|> I have typed a user data directory via the presence of the file '_traces'
|> using the following excerpt from a .rtr file:
|> 
|> TYPE Traces_dir
|>         MATCH dircontains("_traces");
|>         LEGEND XXX traces directory
|>         SUPERTYPE Directory
|>         SPECIALFILE
|>         CMD OPEN dirview $LEADER
|>         CMD ALTOPEN XXX $LEADER
|>         MENUCMD "Run XXX" XXX $LEADER
|>         MENUCMD "Setup for tracing" XXX2 $LEADER
|>         ICON {
|> include("iaf.Traces_dir.pre.fti");
|>                 if (opened) {
|> include("iaf.Traces_dir.open.fti");
|>                 } else {
|> include("iaf.Traces_dir.closed.fti");
|>                 }
|> include("iaf.Traces_dir.post.fti");
|>              }                   
|> 
|> 	This all works fine in most every situation I encountered until today.
|> Today a user trashed such a directory by throwing its CONTENTS into the
|> dumpster instead of throwing the directory in or clicking on the dir and
|> selecting remove from the menu.  So what happened?  The user's dumpster was
|> typed as a 'Traces_dir' instead of a 'dumpster' and the user could not
|> empty it.  A quick removal of the _traces file and closing and reopening
|> Workspace fixed the problem but I don't know how to prevent this from
|> happening again.  Is there anyway I can guarantee the system rules for the
|> dumpster override mine?  Is there a better way for me to write the rule?
|> My application requires the typing be done at the directory level because of
|> the large number of files the application uses and generates.  Typing the
|> directory hides the inner workings of my sw from the user while allowing me
|> easy access to the data for future analysis and diagnostics.  Anyone out
|> there have a solution that preserves the dumpster (besides forcing autoempty).
|> Thanks in advance...
|> --
|> rjf.
|> Randy Frank, Engineer                       |  (319) 335-6712       
|> University of Iowa, Image Analysis Facility |  73 EMRB              
|> randy@tessa.iaf.uiowa.edu                   |  Iowa City, IA 52242  

Funny, we haven't heard anyone having this problem. Most
people use a .<something> file to key off dircontains,
and if you have the default preferences, . files are not displayed,
so if they went in and selected all the viewable contents....
well.

Here's the way to fix it :
	MATCH dircontains("_traces") && !dircontains(.dumpster);

Have fun,

eva


-- 

--- The Giraffe Person at SGI......
    eva@sgi.com