I am currently using the 010-Editor to document a file-format that I am trying to understand and reverse engineer.
Doing so I was trying to copy snippets of the 010’s display into a document using the [Copy as …] → [Hex Editor Areas]. In principle that method works nicely, i.e. I almost get what I need, however, as I had to learn this copy-operation ignores the current LittleEndian vs. BigEndian setting.
I.e in the display I have defined the data to be grouped as “Shorts“ (16-Bit) and I have checked the “Swap Little Endian Bytes by group“-option for easier reading. But in the copied text that byte swapping is not done.
Example:
On screen a snippet is displayed as:
When I paste that into my document after copying it as described from the 010-Editor I get:
1800 FEFF 4FFF FD7F BBFF 8AFF 9AFF FFFF FCFF þÿOÿý.»ÿŠÿšÿÿÿüÿ
i.e. in the copy&pasted text the bytes are in their original order and NOT swapped as in the 010’s display.
I think this is a bug or in my opinion at least a short-coming. I would have preferred to copy-paste the text EXACTLY as displayed in the editor-display.
I guess one can not trick the 010 in exporting the bytes in that order, can one?