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

Re: IBugTraqProvider2 method CheckCommit can be passed an empty commonURL parameter

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Tue, 17 Aug 2010 19:18:17 +0200

On 17.08.2010 14:36, Jim Brooks wrote:
> IBugTraqProvider2 method CheckCommit(). The CommonURL parameter is empty
> if all of the files in the “Changes made” grid are new files, even if
> the checkbox is checked for each. The CommonURL is populated if I cancel
> out of the first commit and start another commit.
>
> To reproduce this I can commit all of the files under my branch. Create
> a new folder locally and create a new text file in that folder. Right
> clicking the branch and select Commit. Check the checkbox for each of
> the 2 new items. Click OK and the CheckCommit() method fires, but the
> commonURL value is empty. The documentation says this should be “*the
> root path of all checked items.” *at this point.
>
> As a potential work around - At the same time on the dialog form I can
> see in the top left hand corner the "Commit to: " label that contains
> the URL to the branch. Is there any way I could get this value in my
> CheckCommit method? Maybe using IntPtr hParentWnd?
> thanks,
> Jim

The problem is that added files don't have an url assigned to them until
you actually commit them. At least with 1.6.x.
In the upcoming 1.7 however, added items do have an url, so that will be
fixed automatically.

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=2647895
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-08-17 19:18:37 CEST

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.