Will Dean wrote:
>
> I suppose that at different times, different things matter - one might
> care more about versioned vs. unversioned sometimes, and more about
> modified vs unmodified at others.
>
I guess it does. Our use is that we have a few sub projects under the
project root. We don't often add/remove folders from svn so basically
know which folders are under control. Our main use is to see if we need
to browse those folders to see if files have changed in them (a couple
of the folders contain numerous sub-folders themselves, so this can take
a while also).
>
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Mon Jan 24 08:47:50 2005