Simon Large wrote:
> 2008/9/19 Stefan Küng <tortoisesvn_at_gmail.com>:
>> In your case, it's a little bit different: you have the svn:needs-lock
>> set. When you get a lock, Subversion first removes the 'readonly'
>> attribute from the file, then changes the entries file inside the .svn
>> folder to mark the file as being locked. Only after that happens, TSVN
>> can send the refresh notification to the explorer.
>> Since the explorer also constantly monitors the current folder for
>> modifications (you can check that: if you run a batch file which creates
>> new files, explorer will show them without you having to press F5), it
>> detects that the readonly attribute was removed and refreshes the view.
>> If it does that before TSVN sends the notification, then the
>> notification from TSVN will be ignored because it will be sent within
>> the refresh-timeout (see my explanation above).
> Does this warrant a request to change the subversion code to update
> the entries file first and then change the read-only status?
No, not for such a non-issue. All you have to do is hit F5 to refresh
the explorer view, so I don't think it is a big deal.
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
Received on 2008-09-20 17:31:52 CEST