This problem is seriously disruptive to those of us who depend on stable folder views!
(I'd assume virtually every Mac user depends on stable views to at least some extent, and yet --compared to other 10.7 issues-- this issue seems to have generated relatively few complaints here and on other forums. Are just a few unlucky people like us affected, or are there many more who don't notice or care?)
From what I've seen and heard, once affected, there's apparently no escape and any folder may be affected. Exceptions: some folders seem relatively, not completely, immune, but I can't see any pattern. Sometimes only a few icons are displaced. Complaints about desktop rearrangement are rare. I've observed rearrangement to and from icon view. The only common factor I see is a tendency for the new view to be arranged alphabetically.
- - -
This may be incredibly obvious, but the rearrangement never occurs to a particular folder unless you close and then later re-open the folder, right? This suggests a partial workaround:
By carefully partitioning my various tasks into different virtual workspaces using 10.7's Mission Control I find I can minimize my need to close folders. Instead of closing a currently open folder that's in my way, I can often switch to another workspace. Presto! the folder is invisible -- but not closed.
Problems with this approach I've found so far:
- Sometimes I forget and close a key folder anyway. D'oh!
- There are some practical reasons to shut-down periodically.
- Some tasks are difficult to partition.
- I find Mission Control is, ummmm, subject to awkwardnesses and glitches.
Still, this approach has decreased my stress at losing my vital icon arrangements and allowed me to get on with my work.
- - -
I encourage others suffering from this problem to observe as carefully as possible, seek alternative workarounds, and post these. Shouting at Apple is not productive. It is possible that Apple doesn't know enough to do anything about this issue. I hope I'm wrong and there's a fix already in the works! But just in case, let's do our best to help Apple help us.
Maybe someone would collect links to all the different threads here and elsewhere? Lots of different names for this issue, leading to different threads. It could be useful to see all the postings, maybe merge some threads.
- - -
Tekkie corner: It seems generally agreed that this issue is due to corruption of .DS_Store file content. As far as I can tell, the .DS_Store mechanism is not publicly documented. (Anyone know different?) Can we tekkie users help characterize the issue by observing .DS_Store files, say, by running shell scripts or for-purpose faceless apps? Can we tell when the corrupt occurs? Sometime just after the window is closed, possibly due to the Finder writing in-memory data for the window to disk? Instrumenting this would be easier if we had a never-fail method of triggering the corruption. Some postings state that navigating an Open dialog (or similar) is reliable, but I've not been able to duplicate. Anyone?