Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Another solution' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Another solution
Authored by: mj on Mar 08, '03 05:52:04PM

What seems like a good solution to me is to do something similiar to the .DS_Store files, but much more cleanly. Let all view information be stored in a .DS_Store file that is located in the highest directory in which you have write access, or if you have a home directory on the disk, to somewhere in your prefs folder. Then when a directory or file is copied to another disk, that information can be merged rather easily into the appropriate .DS_Store on the other disk. To find the view info, just traverse the directory tree to the root and use the first .DS_Store relevant.

Something else that could be done instead of/in addition to this is to store info for other disks in your home prefs folder, and have this info perged every so often, though for disks that you really do use more than once, just rarely, this would have an unsettling effect, but in this case, the .DS_Store files idea I mentioned above would kick in.



[ Reply to This | # ]
Another solution
Authored by: punkmanandy on Mar 09, '03 03:59:12PM

what happens if it is a shared volume that can be accessed at several different points in the directory hierarchy, ie a users home folder?



[ Reply to This | # ]
Another solution
Authored by: GaelicWizard on Mar 09, '03 06:47:25PM

This all depends on the user using Finder. Most (not all) of the Finder-set settings in the .DS_Store files are retained whether I move the folder in Path Finder or in the terminal. But if there is no *real* file in a folder, then unless i use the finder to move it ALL my settings are lost for that folder.

---

Pell



[ Reply to This | # ]