Q1. when you save cfg to a place, HFS deletes cfg in all other places, so what you are saying should never happen
That's good to know BUT:
The method of deleting works well if you only have one user (like most people have).
If you have more than one user, there could be problems:
At the moment, you have 3 choices - HFS.INI, HKCU and HKLM.
HFS.INI and HKLM - all users
HKCU - only the active user
Say you (the administrator) set up the options for all users (HKLM) and most of them are happy with it. But there's one user making a change and saving options only for him/herself. As HFS then deletes all other settings (as you stated), settings for all other users would be lost. So I recommend that HKCU should override the HKLM settings, but not delete it. Of course we need a switch so that users can delete their own HKCU settings and get HKLM settings back. Maybe you could modify the delete option a bit?
HSF.INI should be kept for people who don't like programs messing with the registry and for portability of the options.
Q2. are you talking about real folders, right? i think it may be better if HFS detects the movement and auto-update
I'm talking about real folders and virtual entries for files...
Virtual folders only exist inside the VFS, that'why they are called 'virtual', right? But, every other entry in the VFS points to a physical location on your disk(s). What I meant was that I moved the physical files/folders from one location to another. Now the VFS-entries point to the old (now invalid) targets. I just wanted an option to tell HFS 'Hey, the file is now there' without deleting and readding the entry. The tooltip already shows me the path (second line), just no way to edit it... :?
Q3. the dialog is planned for 2.1 and access permissions are already recursive
Good to know that it is already on to-do...
So the permissions are always recursive? Ok, but the VFS does not show it. The lock should appear next to all entries permissions apply to. You should change the lock's color for entries that 'inherit' permissions.
Is it possible to add an option to disable inheritation of permissions for some entries? So you could have an unprotected file in your otherwise protected folder. Everyone knowing the correct URL could access that file, but nothing else.
Example 1 - The current situation:
I restrict permissions for folder A. A has a subfolder B.
1. The lock appears next to A. NOTHING in VFS shows me than subfolder B is also protected. (now I know but other's may not)
2. If I right-click B and select 'Restrict access', it tells me that there is NO restriction (no users selected). But it's restricted.
Example 2 - How it could be better (i fear it would require a rewrite of the VFS)
I restrict permissions for folder A. A has a subfolder B. Same situation.
1. The lock appears next to A. B gets a different colored lock showing me that it inherited permissions from A (its parent).
2. The 'Restrict access' option for B is read-only until I disable 'inherit' for B. Then I can set different restrictions for B.
I wish I could speak English better...
Q4. i get the scrolling arrows. i fear it is a limit of NT4 and i don't know any way to solve this. to load an icon just add the file to HFS, then remove it. icons are saved inside the VFS.
That' why I asked for multi-column view. :roll:
Icons for files I load and then remove are saved in the VFS? Good. But icons I don't use should be thrown out after some time or else the VFS would get bigger every time I add and remove files (I do this very frequently).
Q5. i tried caching the icon of the file, and yes, it greatly improved the speed. my system32 folder was 3.3s and now is 1.5s
Very nice. I had build times of 10 seconds and more (LAN!). Even M$ discovered years ago that caching icons is a good thing. :lol: But like in Q4 the icons should get thrown out after some time to avoid excessive growth of the cache.
edit: Where does it cache? Only in RAM or also disk?
MarkV