Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!husc6!mailrus!ames!oliveb!tymix!antares!jms
From: jms@antares.UUCP (joe smith)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Standardization
Keywords: Menus
Message-ID: <221@antares.UUCP>
Date: 24 Oct 88 07:44:47 GMT
References: <1314@nmtsun.nmt.edu> <2287@cadovax.UUCP>
Reply-To: jms@antares.UUCP (joe smith)
Organization: Tymnet QSATS, San Jose CA
Lines: 22

In article <2287@cadovax.UUCP> keithd@cadovax.UUCP (Keith Doyle) writes:
>One problem I have been struggling with somewhat with file requesters is
>that I would like to keep the file list around, but if you have multiple
>file requesters for different file operations, how many lists of files
>should you actually maintain?  

Keeping a list of what's in a directory is great, as long as you can
guarentee that nothing has changed the directory behind your back.  Think
of how frustrating it would be if a program refused to acknowlege the
existance of a file that you had just created from another window.

This is a worth-while idea; caching a list of file names.  To make it
workable though requires a change to AmigaDOS.  If programs kept a lock
on the directory that the list came from, then all we need is a new
function to tell AmigaDOS to send us a message whenever the directory
changes.  The messsage is a signal to the program to flush its file name
cache.
-- 
+----------------------------------------------------------------------------+
| TYMNET:JMS@F29  CA:"POPJ P,"  UUCP:{ames|pyramid}oliveb!tymix!antares!jms  |
| INTERNET: (Office-1.ARPA is no more)      PHONE:Joe Smith @ (408)922-6220  |
+----------------------------------------------------------------------------+