h.larsen@risoe.dk wrote:
>>>Why make simple things complicated? Leave the latest log comment
>>>
>>>
>visible
>
>
>>>in the combo box, and the problem is solved.
>>>
>>>
>>Peter McNab [mailto:mcnab_p@melbpc.org.au]
>>No.
>>Better no commit log message than a wrong one.
>>
>>
>But the "wrong one" _is_ there now, just not visible. Would you suggest
>it be removed entirely then?
>
>
>Henning
>
>
>
Well there is a ComboBox nearly full of wrong ones if it comes to that.
No what I'm getting at is that it's so easy, after reviewing the files
to then forget all about the log message and just click OK. I have done
it numerous times. The post hook script on the server throws it back.
However, if your log history needs re-editing after resolving the
reason for the commit failure and you blindly click OK again then your
log history becomes less accurate.
So just that one conscious step needed to re-select the log message is
vital to inducing one to re-read it before clicking onwards.
I think the way Stefans implemented it is OK and I just floated the idea
of providing more visual cues to catch the users eye.
Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed Oct 5 01:34:11 2005