Anthony Palomba

I have file that I created that was added to the file

browser. I exited Max and renamed the file to something else.

When I restarted Max, the file browser now shows the old file 

name and the new file name when I search for things. How

can I make Max forget about the old file?

I have file that I created that was added to the file
browser. I exited Max and renamed the file to something else.
When I restarted Max, the file browser now shows the old file 
name and the new file name when I search for things. How
can I make Max forget about the old file?
I am running Max5.02 on XP.


filebrowser-shows-ghost-file-names

Anybody at Cycling aware of this? Can someone confirm...

Another problem I have found is that if you a patcher

named "test.pat" and it gets added to the DB, if you

change the name to test.maxpat, the DB gets confused.

Another problem I have found is that if you a patcher
named "test.pat" and it gets added to the DB, if you
change the name to test.maxpat, the DB gets confused.
It shows "test.pat" twice.


On 2008 May 27, at 11:06 AM, Anthony Palomba wrote:

> Another problem I have found is that if you a patcher

> named "test.pat" and it gets added to the DB, if you

> change the name to test.maxpat, the DB gets confused.

Max will be confused too, should you ever try to load that as an 

abstraction. You can't have multiple patchers with the same name 

(regardless of extension) in the searchpath without causing 

> Another problem I have found is that if you a patcher
> named "test.pat" and it gets added to the DB, if you
> change the name to test.maxpat, the DB gets confused.
> It shows "test.pat" twice.

Max will be confused too, should you ever try to load that as an  
abstraction.  You can't have multiple patchers with the same name  
(regardless of extension) in the searchpath without causing  
indeterminate behavior.

On 2008 May 24, at 3:21 PM, Anthony Palomba wrote:

> I have file that I created that was added to the file

> browser. I exited Max and renamed the file to something else.

> When I restarted Max, the file browser now shows the old file

> name and the new file name when I search for things.

The strategy used by the file browser to pick up changes works most of 

the time, but sometimes it doesn't. What it is doing is checking 

folders in your searchpath to see if they are flagged as modified. 

The OS generally marks them as such when creating or deleting a file. 

I believe OS's differ in what they do when you rename something.

We could watch every single file in your searchpath (probably 

something slightly less than 10,000 files for the average user) and 

thus hog all of the CPU all of the time (and make startup times really 

unbearable). That's obviously not such a good idea.

If you want find that your database is a bit stinky and needs a wash, 

then you can rebuild it from scratch using the following message to Max:

> I have file that I created that was added to the file
> browser. I exited Max and renamed the file to something else.
> When I restarted Max, the file browser now shows the old file
> name and the new file name when I search for things.
> I am running Max5.02 on XP.

The strategy used by the file browser to pick up changes works most of  
the time, but sometimes it doesn't.  What it is doing is checking  
folders in your searchpath to see if they are flagged as modified.   
The OS generally marks them as such when creating or deleting a file.   
I believe OS's differ in what they do when you rename something.

We could watch every single file in your searchpath (probably  
something slightly less than 10,000 files for the average user) and  
thus hog all of the CPU all of the time (and make startup times really  
unbearable).  That's obviously not such a good idea.

If you want find that your database is a bit stinky and needs a wash,  
then you can rebuild it from scratch using the following message to Max:
	;max db.reset

Thanks Tim, it is good to know that such a mechanism exists.

Filebrowser shows ghost file names...