Ellipsis in file comparison filename dropdown
Posted: Thu Jun 01, 2017 4:20 pm
.
At the top of each filename comparison's pane is the full path of each of the two filenames being compared. When the path is too long to fit within the width of the pane, an ellipsis is used to shorten the path such that the most important part, the filename, is always visible.
This is good! BUT...
Would it be possible to try to choose a bit more intelligently where the ellipsis is placed?
Foe example: suppose the two paths were:
Today (version 9.0), the ellipses are placed as follows:
Which I hope you'll agree is not very helpful!
What I would personally prefer is to truncate (replace with an ellipsis) the longest substring the two paths have in common, or if they have nothing in common, the beginning of the path and not the end.
If such a rule were implemented then almost identical paths such as the ones I provided would instead appear as follows:
Which I hope you'll agree is much more helpful!
Thanks for a great product that just keeps getting better!
.
At the top of each filename comparison's pane is the full path of each of the two filenames being compared. When the path is too long to fit within the width of the pane, an ellipsis is used to shorten the path such that the most important part, the filename, is always visible.
This is good! BUT...
Would it be possible to try to choose a bit more intelligently where the ellipsis is placed?

Foe example: suppose the two paths were:
- C:\Users\Fish\Documents\Visual Studio 2008\Projects\Hercules\_GIT\_Fish\_BitBucket\_prometheus-0\scedasd.c
- C:\Users\Fish\Documents\Visual Studio 2008\Projects\Hercules\_GIT\_Fish\_BitBucket\_prometheus-1\scedasd.c
Today (version 9.0), the ellipses are placed as follows:
- C:\Users\Fish\Documents\Visual Studio 2008\Projects\Hercules\_GIT\_Fish\_BitBucket\_prome...\scedasd.c
- C:\Users\Fish\Documents\Visual Studio 2008\Projects\Hercules\_GIT\_Fish\_BitBucket\_prome...\scedasd.c
Which I hope you'll agree is not very helpful!
What I would personally prefer is to truncate (replace with an ellipsis) the longest substring the two paths have in common, or if they have nothing in common, the beginning of the path and not the end.
If such a rule were implemented then almost identical paths such as the ones I provided would instead appear as follows:
- C:\Users\Fish\Documents\Visual Studio 2008\Projects\Hercules\_GIT\_Fish\_BitB...\_prometheus-0\scedasd.c
- C:\Users\Fish\Documents\Visual Studio 2008\Projects\Hercules\_GIT\_Fish\_BitB...\_prometheus-1\scedasd.c
Which I hope you'll agree is much more helpful!
Thanks for a great product that just keeps getting better!
.