[FULLY FIXED!] Bugs with rendering HEX view of a file

[white]

2white
I would be interested in seeing your reaction to the version of the hex viewer window that I presented in my code, ...

I already took a quick look, but I don't have an opinion about it at this moment.

[ghisler(Author)]

BUT IF i will try to select by mouse 2 last chars: "аж" - for the last char "ж" only
ONE byte "D0" will be selected on the left panel.

Actually it is being selected, just not drawn. When you resize the window to zero size and then back, you will see it. I will try to refresh the extra line.

[white]

BUT IF i will try to select by mouse 2 last chars: "аж" - for the last char "ж" only
ONE byte "D0" will be selected on the left panel.

Actually it is being selected, just not drawn. When you resize the window to zero size and then back, you will see it. I will try to refresh the extra line.

A similar refresh issue seems to happen when selecting only the last char "ж" using the mouse and then not releasing the mouse button but moving the mouse in the opposite direction, unselecting the character again. The hex code on the next line remains visibly selected.

[ghisler(Author)]

Same problem, it's because the character only appears on one line, but its code appears on two.

[ghisler(Author)]

This should be fixed in Total Commander 11.57 rc 4, please check it!

08.04.26 Fixed: Lister, hex mode: When selecting a character where the character codes go over 2 lines, the code on the next line wasn't refreshed (32/64)

[AntonyD]

Confirm. NO ghost symbols on next line now. That's fine, but can I repeat the question about the wrong cursor placing among chars?

Code: Select all

00000000: 45 58 49 46 4C 4E 47 00|72 75 01 01 00 00 00 01 | EXIFLNG ru..   .
00000010: 00 00 24 00 00 00 D0 A8|D0 B8 D1 80 D0 B8 D0 BD |   $   Ширин
00000020: D0 B0 20 D0 B8 D0 B7 D0|BE D0 B1 D1 80 D0 B0 D0 | а изображ
00000030: B6

Again for ex. we 'll take this small piece of a hex-code.

IF i will try to click LMB far behind each last visible char in each line - cursor will be placed only
in a begging of the NEXT line after the one - on which the click was done...
Example: I am clicking on a line with "а изображ" - but cursor will start blinking only on the next
EMPTY line! If i will click LMB on a line with " $ Ширин" - cursor will be put on the start of a NEXT line!
With "а изображ" in it ... and so on...
BUT! placing the cursor at the beginning of the first line is generally not possible now - because due to the identified
"feature/bug", I have to click the Left Mouse Button on the line ABOVE the one where I need the cursor - and there is
nothing above the first line...

Probably this same 'feature' causes incorrect cursor placement when moving with the LEFT cursor control keys.
We place the cursor on the last empty line and press LEFT – the cursor will land after the 'ж' on the line above.
We place the cursor at the beginning of the third line and press LEFT – the cursor will land after the 'и' on the line above,
EVEN THOUGH it was expected to be after 'н'.

[white]

BUT! placing the cursor at the beginning of the first line is generally not possible now - because due to the identified
"feature/bug", I have to click the Left Mouse Button on the line ABOVE the one where I need the cursor - and there is
nothing above the first line...

You don't have to click above the line at the right. You can simply click at the beginning of the first line to place the cursor there.

Probably this same 'feature' causes incorrect cursor placement when moving with the LEFT cursor control keys.
We place the cursor on the last empty line and press LEFT – the cursor will land after the 'ж' on the line above.
We place the cursor at the beginning of the third line and press LEFT – the cursor will land after the 'и' on the line above,
EVEN THOUGH it was expected to be after 'н'.

You reversed it. Given the chosen implementation, the cursor movement at the end of the file is wrong. Ghisler fixed it when the this text appears in the middle of the file, but there is a bug when it is at the end of a file. At the end of the file, cursor movement to the left does not go over the same positions as cursor movement to the right. And when holding shift when pressing Left, you can select half the character at the end. That was not the implementation that was chosen.

There is also a bug with the cursor movement when pressing the Down key. Press Ctrl+Home and press Down repeatedly and look what happens.

And there is still the bug with the End key, which places the cursor on the last byte instead of the last character. So the cursor is placed inside a multi-byte character when such character is at the end of a line and all bytes of the character are displayed at the left on the same line.
In your example file press Ctrl+Home, Down, End, Shift+Left, Shift+Right, Shift+Left, Shift+Right. You see that half of the bytes of the character is selected. That is not the implementation that was chosen.

[ghisler(Author)]

Sorry, I will keep the cursor movement the way it is. You can't put the cursor at the end of the line AND at the start, the two are the SAME position in the file. I prefer to put it at the beginning of the line, so pressing END will go to the second last character instead of the next line. Going to the next line would be even more confusing.

Because this thread contains a ton of different reports, and I will not change just one of them, I now have to move the entire thread to will not be changed.

Moderator message from: ghisler(Author) » 2026-04-16, 07:11 UTC

Moved to will not be changed

[AntonyD]

2white

You don't have to click above the line at the right. You can simply click at the beginning of the first line to place the cursor there.

Your reason is not quite correct in this application. Of course, I HAVE NO ORDERS to do ONLY one way and not another.
Thus also I MAY click at the beginning of the line.
BUT the opposite is also true - I HAVE NO RESTRICTIONS or STRICT prohibition on not clicking OUTSIDE the visible characters at the right.
That's why I'm doing this, and I find that the behavior of the program in this case is clearly different from what any other editors show us.
And we are talking about editors here, because we have enabled the cursor display mode!

And I have a suggestion - since this whole thread has been moved to the wrong place, I suggest you cut our last posts starting
with "Confirm. NO ghost symbols on next line now..........".
And separate them into a separate NEW bug-topic, where we can continue discussions with new forces.
And this topic could well be moved to the "Fixed" section! Because the original stated problem has been fixed.

[white]

BUT the opposite is also true - I HAVE NO RESTRICTIONS or STRICT prohibition on not clicking OUTSIDE the visible characters at the right.
That's why I'm doing this, and I find that the behavior of the program in this case is clearly different from what any other editors show us.
And we are talking about editors here, because we have enabled the cursor display mode!

The behavior may be different from other programs, but this is the chosen design in Total Commander. The same applies for the cursor movement when pressing End. Again, look at the behavior when viewing an ANSI file (so not containing any Unicode characters). That is the design. And it has been like that for a long time (from the beginning).
If you want, you can of course suggest a different design in the Suggestion subforum.

And I have a suggestion - since this whole thread has been moved to the wrong place, I suggest you cut our last posts starting
with "Confirm. NO ghost symbols on next line now..........".
And separate them into a separate NEW bug-topic, where we can continue discussions with new forces.

To help Ghisler, I will create separate bug reports for several things I reported here. I can understand how it can be vey hard to keep track of everything.

And this topic could well be moved to the "Fixed" section! Because the original stated problem has been fixed.

I don't think this is terribly important and will leave this up to Ghisler's discretion.

[AntonyD]

2white
Please, let's cut our communication from here, move to a new topic with new bugs and there I will express my vision of the situation. Still, to continue this conversation here is very strange and illogical. And it is also strange to leave this topic in an incorrect forum section - because regarding the REALLY FIRST problem, which was the basis of this topic - the situation is completely resolved. And the last decision to move the topic to an illogical place - just the result of the fact that we continued to discuss in it a little bit different problems and concepts.

[ghisler(Author)]

Sorry, I can't move this thread to "fixed bugs" because the discussion diverged so far from the original issue. That's why I prefer a single issue per thread.