RE: Re: TortoiseMerge, strike through issue

I was afraid that would be the response.
Allow me to elaborate:

I know that at the lowest level, every modification results in deleting a line, and replacing it with a modified line.
But the 'strike-through' feature, I think, should be implemented at the 'user level', that is: lines completely removed (no longer there) in the latest revision, should be 'stricken through' in the older version, so as to clearly visualize what has been removed.

It doesn't seem to make sense to use 'strike-out' on EVERY modified line: first of all, modified lines are ALREADY marked, and second, strike-out makes them hard to read (and for modified lines, you probably want to see what the modifications are).
In other words, the current implementation doesn't add anything to marking changes (other than making them harder to read), as where the idea of clearly marking DELETED lines (from the USER'S perspective, NOT from how the modify engine works behind the scenes!) simply isn't implemented.

If a USER is offered an option for a strike-out on all DELETED lines, he doesn't expect strike-out to be applied to all MODIFIED lines (which are already marked anyway).

In short, I think this should be a user level feature, not based on how things work at the lowest level.
(Other diff/compare programs, like BeyondCompare) do this correctly)

Kind regards,

~ Paul C

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3006494

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-09-17 16:51:32 CEST