v4.1
I have the "use read-only flag for files that are not checked out" option checked.
Normally my files are R but not A (i.e. Read-Only set, Archive bit cleared)
Here are the unexpected R/A attribute handling I've seen:
1) Check out a file (now R bit is cleared).
Undo check out (without touching the file).
=> file's R bit stays cleared but it should
bug!
2) Check out a file (now R bit is cleared)
edit the file so the A bit gets set
optionally manually clear the A bit, the result is the same
Undo check out, say Overwrite to the prompt
=> RA bits both get set
feature request? I would expect jthe A bit to be cleared
3) Checking in a file clears the A bit, but adding a file does not
feature request? I would expect it to.
For points 2 and 3, I like to just have A bit set when the file is different than what is in VSS. It depends how you like to use the A bit wrt VSS.
Maybe for those 2, an additional option (even if it's just a registry entry would be nice.
Thanks,
JT
file attributes handled inconsistently (feature request?)
Moderator: SourceGear
1) Check out a file (now R bit is cleared).
Undo check out (without touching the file).
=> file's R bit stays cleared but it should
bug!
This is a known bug that will be fixed for SOS 4.1.2, due out later this summer.
As for the "A bit," we'll have to check the code to see how this is/should be handled. I'll log it to our bug/features database.
Thanks for the report.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager