Show mark after the end of every block (1KB, 4KB...)

[juliangruber]

@trufae which blocks should be delimited exactly?

[trufae]

Usually 4KB and 16KB but i think we can copy this from the old vialab hex
editor options

On Thursday, 11 February 2016, Julian Gruber notifications@github.com
wrote:

@trufae https://github.com/trufae which blocks should be delimited
exactly?

—
Reply to this email directly or view it on GitHub
#25.

[juliangruber]

does anyone have a screenshot of this?

[trufae]

i do

[trufae]

Oops. when i did the screenshot, the dropdown menu got shy

[trufae]

Fixed with the radical hacking technique of changing the focus

[juliangruber]

thank you. can you also show me how the rendered hex dump looks different with any of those options active?

[trufae]

Nothing changes, which is imho confusing. imho it will be good to show a

---

after every block or so

On Mon, Feb 15, 2016 at 12:10 AM, Julian Gruber notifications@github.com
wrote:

thank you. can you also show me how the rendered hex dump looks different
with any of those options active?

—
Reply to this email directly or view it on GitHub
#25 (comment)
.

[juliangruber]

ah, gotcha! thanks, i understand the problem now

[tomanderson2]

@trufae afaik the display bytes option in the hex viewer just alters how much data is loaded into the UI, nothing fancy :) I like the idea of marking blocks though +1

[radare]

yeah it looks more like a bad design decision to include that option to just change what's loaded. having block separators and doing dynamic loading is way better option imho

[tomanderson2]

Yes, thats something that should NOT be copied into this new hex viewer. I think this was something required a while back for users with slow machines due to how data was loaded. Dynamic loading FTW