>
>
>>I hardly think users would be confused by a second checkbox, especially
>>if it's labeled. But if you insist they would be, how about a toggle
>>control that looks like a lock?
>>
>>
>
>Bad UI is bad UI. We shouldn't be adding a bunch of check boxes because
>someone wants to use a feature. There will be many, many more users that
>do not want to use this feature. Setting this property recursively from
>the top of your WC is trivial.
>
>
>
We're talking about one checkbox, toggle button, whatever works. My
interface suggestions may be inadequate, but you'll never convince me
that there is no way to provide a quick, easy, and unobstrusive UI to
the needs-lock property.
And the whole point of this thread is that it's not "somone" asking for
a feature. It's likely a compelling amount of users. Now, I may be off
base with this estimate, but you seem to be dismissing it without any
actual consideration.
>>I don't pretend to have the greatest ideas on interface design.
>>However, I'd appreciate it if you'd respond to the general suggestion
>>that the needs-lock property will be heavily used by many users and
>>deserves a more prominent, easily accessable interface.
>>
>>
>
>I agree with Stefan. TortoiseSVN already provides more than adequate UI
>for using this feature. The Subversion autoprops enhancement is what is
>really needed. I would hate to see the UI cluttered up as a stop-gap.
>
This is a user telling you that TortoiseSVN does not provide an adequate
UI for this feature.
An autoprops enhancement by the subversion guys would be great, I agree,
but I still wouldn't expect all of my users to hand-edit a config file,
echoing what Ron said.
-Owen
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Thu Jun 2 21:29:57 2005