Hans-Emil Skogh wrote:
>>> Recently I had a working copy with quite a few changes. Some files
> had
>>> only text changes, some had propery changes and some had both.
>>> However, as each unchanged status is displayed with the text "normal"
> in
>>> the same color as the "modified", it makes it quite hard to see what
>>> files that has what kind of changes.
>>> I would propose to change the color of "normal" in those dialogues to
>
>>> (light) gray.
>> There's a checkbox below the file list where you can hide the 'normal'
>> entries completely.
>
> Yes, but only for files that are completely unmodified. In this case I
> have files like this:
>
> File Text status Property status
> -----------------------------------------
> File1.cpp normal modified
> Image1.png modified normal
> File1.h modified modified
>
> ...and so on.
>
> The small difference makes quick "scanning" of the list difficult.
>
>> The problem with 'gray' or any other color is that we would have to
> make
>> it configurable - some users have really strange color schemes because
>
>> of eye problems.
>
> I tend to overlook that all the time, don't I?
>
> Two possible solutions:
> 1.) Use the color that is used for files that are entirely normal (black
> that is) for the word "normal".
> 2.) Create a configurable color for "normal" (both complete files and
> the word), and let it default to some darker gray shade. I think this
> would provide improved readability for the commit and check for
> modification dialogues.
Why don't you just sort by the 'text status' or 'property status' column?
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed May 2 21:48:16 2007