Russell Hind wrote:
> Will Dean wrote:
>
>>
>> That's right, it's the obvious solution - I was going to ponder on
>> that in my previous posting, but as we really can't 'waste' an icon
>> like that, there doesn't seem much point thinking about it.
>>
>
> That would be the ideal. Are we limited because of the amount of
> icons TCVS uses (I know explorer also has a limit too)?
>
> But if the status is only not shown for a short time then I guess it
> isn't so important. How about showing the modified state until we
> know the correct state? That way, at least no-one will think nothing
> has changed and forget to commit, when something has changed? May be
> better than showing the 'nothing changed' until we realise something
> has changed?
>
> Cheers
>
> Russell
>
As things stand thought, when doing recursive status checking, the icon
is plain yellow until the situation is known, so I know the status is as
yet unresolved (W2000).
Howver if others see something different then I wouldn't consider it a
waste of an icon to show the status is undecided, particularly for those
with big projects and or slow machines so we don't launch an
inappropriate action if a false state is indicated.
Peter McNab
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Mon Jan 24 11:32:59 2005