If you try to display more than 100 (in dec) char per lines, the numbering will take 1 offset left over the data.
Just try to display 200 char per lines! (in decimal).
And yes, it's very important to me.
Schtrudel
Fixed: HxD: Buggy display of column-offsets >= 100
Well the reason is apparently that the numbers are getting to "wide", anything > 99 will have at least 3 digits.
The thing I could do, is use the space that separates the header offsets from each other, to print the additional digit, but this also means there is no more space between the offsets which makes it harder to read.
Another more readable possibility would be (leading digit as subscript):
Why do you need this? This could help to find better ways of solving this.
The thing I could do, is use the space that separates the header offsets from each other, to print the additional digit, but this also means there is no more space between the offsets which makes it harder to read.
Another more readable possibility would be (leading digit as subscript):
Why do you need this? This could help to find better ways of solving this.
Well, that is fine, but I look at what is doing winhex, they simply go back to 0:
98 99 00 01 02...
So it's perhaps enough (since what you will do if someone even more crazy than me wants to align every KByte!), but perhaps add on the status bar the column were the cursor is (like in some text editor or in excel when you got the line and column in the status bar)
98 99 00 01 02...
So it's perhaps enough (since what you will do if someone even more crazy than me wants to align every KByte!), but perhaps add on the status bar the column were the cursor is (like in some text editor or in excel when you got the line and column in the status bar)