Compare and edit is disabled when file has line with 24k len

[MVV]

I've wasted some time to determine why TC doesn't allow to edit these two files during compare, and finally discovered that one of them contains 24k line that caused this. It is quite confisuing and sad, I think that there is no reason to block editing in case of such long lines, or at least user should be informed why editing is disabled...

[ghisler(Author)]

The problem is that some GDI functions crash with such long lines. I cannot draw shorter bits because it would break right to left/left to right mixed text. That's why such long lines are always shown in red (as a difference), cut to 16k, and editing is disabled.

[Hacker]

Christian,
I agree with MVV, an informational message would be nice here.

Roman

[ghisler(Author)]

Where? Show a messagebox for each such line? That would be really annoying.

[Hacker]

Christian,
Well, either a message:

"File <FILENAME> contains a line that is longer than <LIMIT_VALUE> bytes. Editing is therefore disabled."

or e.g.:

"The following line numbers in file <FILENAME> contain more than <LIMIT_VALUE> bytes:
Line <LINE_NUMBER1>
Line <LINE_NUMBER2>
Line <LINE_NUMBER3>

Editing is therefore disabled."

Roman

[MVV]

E.g. as TC does for deleting files: show numbers of first N long lines and an ellipsis if more.

Or maybe a better solution would be to allow editing but w/o long lines (show some read-only text in them).

[Dalai]

2ghisler(Author)
Instead of showing a (blocking) messagebox, I think you could easily add the explanation to some area of the compare by contents window, maybe with a yellow(?) background color, just like browsers do today for some informational stuff.

Regards
Dalai