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?
If you don't recurse into folders, the default is to show the
InSubversion icon, so you could also use that for
'still-fetching-status'.
The problem with whatever existing icon you use is that you don't know
how long you need to wait to see if it is going to change. Does the
cache operate on slow network shares as well? One way around this is to
add another 'fetching-status' state which shows up in the column
provider, but which shares an icon overlay with InSubversion or
Modified, or whatever the preferred 'safe' option is. For most users,
the update will be fast enough. For the paranoid or those on very slow
devices, there is a fall-back.
Simon
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Mon Jan 24 13:05:32 2005