discuss-gnustep
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GNUstep Window Manager (was RE: Idea)


From: Enrico Sersale
Subject: Re: GNUstep Window Manager (was RE: Idea)
Date: Sun, 7 Jan 2001 13:13:42 +0200 (EET)

On Sun, 7 Jan 2001, Richard Frith-Macdonald wrote:

> 
> On Sunday, January 7, 2001, at 12:40 AM, Enrico Sersale wrote:
> 
> > > > - go with the Finder in a directory. 
> > > >  
> > > > - now open a terminal on the same dir and do something (ex. create or 
> > > >   delete a file). 
> > > >  
> > > > Is the content of the finder window updated automatically? 
> > >  
> > > Forget about the Finder on MOSX, it is more than buggy... To answer 
> > > your question (w/o actually trying it out), it *should* be updated, 
> > > perhaps after some delay, but I doubt that it happens in that version 
> > > (sometimes, I remember, you can't even force it to recognise new 
> > > directory content)... 
> > >  
> > > cheers, Phil 
> > > -- 
> >  
> > Ok. But what, which *object*, should notify the finder? 
> 
> The workspace manager should have a timed event to check to see if the 
> directories
> displayed in any of its viewer windows have been modified.
> Thus, if a GNUstep app modifies a directory using the NSWorkspace APIs, the
> workspace is notified immediately and windows are updated at once, and if you
> modify things in any other way (like from a terminal window) the application
> will update after a short dalay.
> I think it takes about four seconds for the workspace to notice a modification
> to the filesystem on my NeXTstep system, but if I remember correctly there is 
> a
> user default to modify the period at which the filesystem is checked.
>  

Well, I know this way. My old file manager, WMFinder, uses something like
this...

But in wmfinder each window shows only one directory; in a browser based
view of the filesystem the directories to verify are many and the check
can be very time-consuming.

I was only wondering if there is an other, more elegant, solution...




reply via email to

[Prev in Thread] Current Thread [Next in Thread]