|
Post by nicc on May 22, 2016 9:45:37 GMT -5
Hi
I had trouble cretaing a new file with 'HEX ON'. I selected NEW from FM and when the edit screen showed I turned hex on. I got this:
***** top of data *****
---------------- **** bottom of data **
----------------
instead of:
**** top of data ***** ---------------- ---------------- **** bottom of data ***
This occurred both on the latest version and the last XP version.
And, whilst we are at it, I needed to put in a lot of x'00' so I put the cursor on the top line of the hex and held down the 0 key. This worked fine until I got to the right margin when the cursor suddenly jumped to the 'ascii' line and continued merrily on its way as the screen scrolled right. This also upset the alignment of the ascii text and the hex representation. This, again, was tested on the latest and the last XP versions.
Nic
|
|
|
Post by George on May 22, 2016 11:29:30 GMT -5
Nicc: The layout of the empty Hex file is just as it's supposed to be, I see nothing wrong. Here's what I get: The Top and Bottom lines are not displayed in hex, but the upper/lower lines are inserted to maintain the normal vertical line spacing. As to the action on entering characters in the last position of the line, this is a much thornier problem, right now I have no simple fix. It gets wrapped up with redrawing the whole window because of the shift) and the cursor re-positioning routines right now all assume entry on the character line, they basically ignore positioning to the upper/lower lines. Adding that will require changing the positioning calls throughout the entire code. George [Update] Corrected. Managed to use optional parameters to keep the number of changes down to a dull roar. Will be in the next release. George
|
|
|
Post by nicc on May 22, 2016 13:31:48 GMT -5
What is that dashed line doing AFTER the 'bottom of data' line? Surely the 'bottom of data' line should be the LAST line. I know that it is not ISPF but there the dashed lines com between the top and bottom of data lines. On SPF/Pc and Pro I only get the one line and it is between the Top and Bottom of data lines. I believe the dashed lines are supposed to demarcate the data lines thus:
**** Top of Data *** ---------- data line 1 hex line 1 hex line 2 ----------- data line 2 hex line 1 hex line 2 ----------- **** Bottom of Data ***
|
|
|
Post by George on May 22, 2016 13:38:49 GMT -5
nicc: Each line becomes 4 lines The character line The Upper hex The Lower hex and the dash line as a delimiter.
I don't do any mucking about with line types, top, bottom, data lines, cols, tabs, whatever -- they all get the same formatting. If it wasn't consistent for all lines, then the backward translation of cursor location to what data line, which of the hex lines etc. would just become even more complicated.
As to how the other guys format things, each to their own. I've never tried to make SPFLite a 100% clone of any of them.
George
|
|
|
Post by nicc on May 23, 2016 2:51:26 GMT -5
Hi George
Ok, I see what it all means - the first dashed line separates the 'Top of data' line from the first data line and the second delimits the 'Bottom of data' line from...nothing in particular. That last threw me because I never saw it that way before - unfamiliarity cause my little brain cell huge confusion!
Regards Nic
|
|
|
Post by George on May 23, 2016 10:54:12 GMT -5
nicc: It's always clear when you 'get it', but until then .... And of course, with JUST the top/bottom lines visible it's even harder to see the pattern.
George
|
|