[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: TSVN 1.7.1 annoyances

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Mon, 31 Oct 2011 15:40:56 +0100

On 31.10.2011 14:02, Gunnar Dalsnes wrote:
> On 31.10.2011 10:15, Stefan Küng wrote:
>> On 31.10.2011 09:57, Gunnar Dalsnes wrote:
>>> Hi,
>>>
>>> Here are some annoyances I see in TSVN 1.7.1 that was not present in
>>> TSVN 1.6:
>>> -The painting artifact problem in the commit dialog is still present (a
>>> 5x17 pixel gray area)
>> "still"?
>> when did you report this before? what artifact do you mean? can you
>> provide a screenshot please?
> I didn't but I remember someone else did. I have attached a screenshot
> (with private parts brushed).

Thanks for the screenshot!
Opened issue #124 for this:
http://code.google.com/p/tortoisesvn/issues/detail?id=124

>>> -I update and I get several conflicts (resolve all later). I edit the
>>> first file and resolve it, but resolve takes "forever" (30+ seconds).
>>> The next file I resolve take much shorter time (a few seconds), but
>>> still much slower than worst case in TSVN 1.6.
>> empty your crash bin folder, or got to Settings->Dialogs1->Use recycle
>> bin when reverting'
> But I didn't revert anything, I marked a file as revolved (should take
> little time, basically changing the file's local status). But I will
> turn it off/not use RecycleBin and see it improve the situation.

TSVN also checks the file to resolve for conflict markers first before
it marks it as resolved, and shows a warning if it finds such markers.
Depending on the file size, that actually can take a while.

But that feature was available also in 1.6, so it should not take longer
now...

>>> -When select several WC's in explorer and run update, and if get
>>> conflicts in some WC's in between, but not the last one, the final
>>> status is Completed (without errors) and I need to scroll up to see if I
>>> got some conflicts in other WC's. In TSVN 1.6 I believe the final status
>>> would show if any of the WC's had conflicts.
>> Nope. But there's a message at the bottom that there were conflicts.
> Yes, that's what I ment: in TSVN 1.6 there was message at the very
> bottom about conflicts, even if the only conflict was in the first (of
> many) WC updated. In TSVN 1.7 there is only a message about conflicts
> after every specific WC updated, but not at the very bottom (unless the
> last WC updated had conflicts off course:-)

Opened issue #125 for this:
http://code.google.com/p/tortoisesvn/issues/detail?id=125

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2869327
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-10-31 15:41:10 CET

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.