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?
yes, you are right.
but i fear to complicate things (the GUI), since the situation you tell is very rare and would help few people while aggravating others. If you have suggestions....
Anyway, if you ask HFS to save cfg in a file, it won't delete registry.
So you can have safely user-based settings keeping them in files.
You just have to change the "working folder", HFS will read hfs.ini from there.
The tooltip already shows me the path (second line), just no way to edit it...
you'll find it in beta19
The lock should appear next to all entries permissions apply to.
i already thought about it and think it would be a mess.
you can't have all information, always, at the same time.
i made a change in the tooltip to get this information.
Is it possible to add an option to disable inheritation of permissions for some entries?
if it is unprotected, why keep it in a protected folder?
put it elsewhere and hide it
you can have 2 links to the same file, one in the folder and visible, one out of the folder and hidden
(now I know but other's may not)
the "recursion" on a protected structure is the classic behaviour.
it is what you get if you protect a folder on your disk.
it is what you get if you use other web servers.
it tells me that there is NO restriction (no users selected)
the fact is: it doesn't tell you, and you think it is not.
this now has been solved by adding a "telling" feature.
Even M$ discovered years ago that caching icons is a good thing.
yes, i thought that too. i was about to reply you "i ask icons to Windows, and it already caches by itself".
but i decided to make a try, and found ..... it is better to not trust M$
Where does it cache? Only in RAM or also disk?
only RAM
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).
this wasting concerns only RAM. did someone noticed HFS wasting too much memory for icons? like 1MB...
my reply delayed a lot because your message was very long