Re: [TSVN] Resolving Conflicts

>> I greatly prefer things be greyed out - but even more so, *tell me WHY* I can't
>> do that right now.
>
>Many people do, actually. But that's a conflicting issue:
>If you always show ALL commands, but grey out the ones you can't use
>then there will be so many commands there that you won't be able to find
>the one(s) you need - it will be too overloaded.

Yeah, that's the problem... And I'm real big on options and configurability;
seems I like to work differently than most people... :) compounds the problem
with more menus and options...

>> So (when I become King...) the menu would show "Edit Conflict" but be grey (or
>> otherwise visually modified as to be "not valid right now") and when I click on
>> it anyway it would pop up a dialog saying "This is to merge files when there is
>> a conflict between the repository version and your baseline. You do not have
>> such a conflict with file Foo.C"
>
>Ahem: GUI guidelines request that a menu entry greyed out must not be
>clickable!

um... (evil grin!) the guidelines are wrong? (big grin!)

The idea is to help the user *understand* - they think they want to do
something, and whatever they *want to do* isn't the right thing - so a message
can help them learn, instead of their sitting frustrated and turning the machine
into an adversary.

(machines should make our lives *easier*... :)

- Al -

-- 
--  Alan Weiner  --  alan_at_ajw.com  --  http://www.ajw.com
Palm OS Certified Developer
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org