If I divide the view into 2 parts so that one half displays a function with the "Hex Editor" view, and the other half displays the same function with the "Linear" and "Disassembly" views... then only the cursor position is synchronized!
If I start allocating a sequence of bytes, then I expect that in the other half of the screen the command sequence will be allocated, which corresponds to the allocated bytes. But in fact, in the other half, the cursor just moves towards the selection and stops at the instruction that corresponds to the last allocated byte.
And vice versa:
If I start allocating a sequence of instructions, I expect that in the other half of the window a sequence of hex bytes will be allocated, which corresponds to the allocated instructions. But in fact, in the other half of the window, just the last byte of the last instruction is allocated from the allocated array (and by the way, byte allocation in Hex View is almost invisible)
If I divide the view into 2 parts so that one half displays a function with the "Hex Editor" view, and the other half displays the same function with the "Linear" and "Disassembly" views... then only the cursor position is synchronized!
If I start allocating a sequence of bytes, then I expect that in the other half of the screen the command sequence will be allocated, which corresponds to the allocated bytes. But in fact, in the other half, the cursor just moves towards the selection and stops at the instruction that corresponds to the last allocated byte.
And vice versa:
If I start allocating a sequence of instructions, I expect that in the other half of the window a sequence of hex bytes will be allocated, which corresponds to the allocated instructions. But in fact, in the other half of the window, just the last byte of the last instruction is allocated from the allocated array (and by the way, byte allocation in Hex View is almost invisible)