Simon Large wrote:
> 2009/6/11 Stefan Küng <tortoisesvn_at_gmail.com>:
>> Karlos wrote:
>>> OK. I know how to reproduce the icon problem. Steps:
>>>
>>> 1. add a new file "File.bad" with "read only" attribute in the working
>>> copy, without property svn:needs_lock
>>> 2. add a new file "File.ok" normal attribute in the working copy, with
>>> property svn:needs_lock
>>> 3. commit to repository
>>> 4. get lock for both files.
>>> 5. "file1.bad" icon is wrong
>>> 6. "file2.ok" icon is ok.
>> Yes, unfortunately the svn lib doesn't remove the readonly attribute
>> anymore when getting a lock. So "file1.bad" still has the readonly
>> attribute, and that's why the icon overlay is wrong.
>
> Do we still need to rely on the read-only attribute? I thought that
> the WC improvements in 1.4 meant that the svn:needs-lock property is
> quick to access. But maybe not quick enough ...
Done in r16576.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=2361619
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-06-12 16:08:51 CEST