Re: Re: Re: toroiseproc commit hangs

On Wed, Jul 1, 2009 at 05:20, Michael Corr<michael_at_aduratech.com> wrote:
> Ahh. Ok. I see that there are two separate dialog windows, now. So, the second window can be automatically closed, but not the first.
>
> Doesn't really seem to be worth the effort of offering an auto dialog close at all, if you still have to manually close the first window. I don't see the point in offering any automated steps if you don't offer complete automation.
>
> I've done plenty of windows programming - it shouldn't be too hard to grab a handle to the first commit dialog window and automatically press the 'ok' button once the list of commits fills in.

OK, so code it up & submit a patch, if you feel that strongly about it.

> I guess I'm still confused as to why the /closeonend option is even offered - if it doesn't fully automate - and from reading through some other posts, you seem to be strongly suggesting to users to use a command line svn client for automation.

The CLI client is *designed* to be built into scripts. People suggest
that you use it for automation because it's meant to be used that way.
Tortoise is a GUI client, with /some/ command-line abilities provided.
But GUI apps as a rule rarely lend themselves to non-GUI automation.

> I use Tortoise because I really like the user interface and the ease of immediate visibility to see the status of all my files. It would be nice to continue to just use Tortoise for all my needs, and not have to support two separate tools.

You'd be horrified at my workstation then; I have 4 separate SVN
clients, and use them all.

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2366985

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-07-01 11:59:53 CEST