Sven Brueggemann wrote:
>>> When double clicking on a changed file, the progress
>>> dialog shows the filenames trunkated.
>> Of course. The whole URL doesn't fit into the dialog, so they're
>> truncated. That's done automatically by that windows dialog btw.
> Of course, but it's different than in other progresses. TSVN
> normally cuts off the beginning of a path or there is an elipsis
> in the middle of the path. In this case, there is an elipsis and
> the filename on the right side is cut off.
There's not much I can do about that. That dialog is part of the shell.
> You are right - the colourization shows property changes (BTW:
> Are the propery colours hardcoded?). Is the colourization done in
No, not hardcoded. We've learned that the hard way :) Some people have
color settings due to their reduced eyesight which we've never thought
of, and these people must be able to configure all colors or they can't
see some texts.
It's the same color as the 'modified' color used e.g. in the status
dialogs. You can configure that color in the settings dialog.
If you want a different color for those property modifications that for
the 'modified' color you have in the status dialog, you can manually
create a registry key under
HKCU\Software\TortoiseSVN\Colors\ProperetyChanged and set the color an
an RGB() DWORD value.
> the same was as in the commit dialog and the Check for modifications
> dialog? It looks different although I can't tell why, yet.
If it's different than those colors, then you already changed those
colors in the settings dialog. In that case, you still see that color as
the default. Just go to the settings dialog, change a color (and change
it back again), then hit "Apply". This will force the propertychanged
color to be the same as the 'modified' color.
>> If both text and props were changed, you
>> would see something else than 'normal' in the 'action' column and the
>> changed color of the entry.
> Mmmh - a double click on my "Normal"s shows differences in
> whitespace (0x13, 0x1a, 0x20) in text files and big binary changes
> in binary files. At least for the binary files I would have expected
> a "Modified" action.
Can you give a reproduction recipe (or access to your repo) when that
happens? The action is provided by the Subversion API, but since this
API is brand new (and not officially released yet), there may be a bug
in there. So, it's important to have a reproduction recipe to tell the
Subversion guys exactly what's wrong so they can fix that.
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Sun Apr 23 15:23:54 2006