Is it me, or did 993 mess up the check out functionality in Visual SourceSafe?
When I check out files. I get the prompt to add a comment. However, it
takes about 20 seconds before it knows that the file is now writeable.
Clicking the file synchornize button does not appear to help.
Is it me or do I need to file a bug?
Please sign in to leave a comment.
Seems fine over here.
Fine here as well..
--Grant
"Norris Shelton" <nshelton@appriss.com> wrote in message
news:brnlv5$7hf$1@is.intellij.net...
>
>
>
OK, I am on W2K Pro. What are you guys on?
"Norris Shelton" <nshelton@appriss.com> wrote in message
news:brnlv5$7hf$1@is.intellij.net...
>
>
>
I'm on XP..
I did notice that when I get latest version IntelliJ doesn't do a
"synchronize" operation so it looks like when I get latest versions on
things that it is still writeable until I hit synchronize.
-G
"Norris Shelton" <nshelton@appriss.com> wrote in message
news:brq7qn$kss$1@is.intellij.net...
>
>
>
That is what I saw at first. I would check out, then do a get (writeable).
This would make the file available for edit.
Once, I got distracted before I could perform the get (writeable). The file
finally became available for edit. So I started hitting synchronize after I
did the check-out. No difference. It takes about 20 seconds for it to know
that the file I checked out is available for edit. I am running some
continuous processes on my machine in the background. It will use 100% of
CPU, but with the lowest priority. Maybe the IntelliJ synchronize thread is
being denied the CPU.
"Grant Gochnauer" <grant@gochnauer.org> wrote in message
news:brqeii$v0f$1@is.intellij.net...
>
>
>
>
>
>
it
>
>
On a related note, I noticed some funny behavior when using the Expand Keywords feature of VSS. When I check in a file, the local version (which has the old log/revision/etc.) is not updated. If a do a diff with the repository, I see the difference, however a Get Latest Version won't get an updated file. To get the new file I actually have to check out the file.
--Dan