You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Attempting to examine large quantities of data (gigabytes) is cumbersome since most of the display views work in lines of 256 bits, so it would be very handy to be able to know the byte offset within the data (perhaps a bar across all data views indicating the current location) and to be able to easily jump to a specific offset (not necessarily a known bit of data, just a specific position). This may already be achievable using one of the modes of existing plugins, but it wasn't self-evident or easily accessible (in the program or in the help). At the moment the process seems to require choosing the rough location in the overview of the data and then scrolling (possibly large amounts, with very big data files) to find the wanted location (after having calculated the line number needed from the offset).
The text was updated successfully, but these errors were encountered:
I think the bit offset shows when hovering, but yeah, it would be nice for the top offset to always show up, and it would be nice to be able to jump to a specified offset.
Attempting to examine large quantities of data (gigabytes) is cumbersome since most of the display views work in lines of 256 bits, so it would be very handy to be able to know the byte offset within the data (perhaps a bar across all data views indicating the current location) and to be able to easily jump to a specific offset (not necessarily a known bit of data, just a specific position). This may already be achievable using one of the modes of existing plugins, but it wasn't self-evident or easily accessible (in the program or in the help). At the moment the process seems to require choosing the rough location in the overview of the data and then scrolling (possibly large amounts, with very big data files) to find the wanted location (after having calculated the line number needed from the offset).
The text was updated successfully, but these errors were encountered: