bytes per row slider

[QuantumApprentice]

I have a workflow that requires inspecting small images of different widths, and I've found it very helpful to visually see the image frames by adjusting the bytes per row to match their widths.

Unfortunately the slider for this is hidden in the "Extras->Settings" menu and doesn't have a lot of direct adjust-ability, but fortunately I can use ctrl-click to manually set the value.

It would be nice to have this on the front page (probably above the address bar) and expand the range to something in the 1k to 5k range, or at least prevent the program from crashing if an excessively large value is set, or maybe allow the user to set the upper range value.

[WerWolv]

1k to 5k is an absolute MASSIVE number of bytes that need to be displayed on the screen and this is in my opinion really not how this feature is intended to be used.

Instead you should consider writing a pattern that highlights the images (and potentially use the bitmap visualizer to turn it into an image right away)

[shodanx2]

Hello,
First time using imhex today.
How can I view more bits is my first question that lead me here.
I don't understand why the hex editor view is not set to auto-resize with its view
Here is what it looks like to me right now. Only 137 rows of 16 bytes each.

On my 4k 40" TV there is space to show 112 by 137, or 15K of data

And that's if I don't use my side-monitors

In which case 45K of data can be seen at once

[WerWolv]

You can click on the little up arrow in the hex editor footer and then adjust the value of the marked slider. By default it only goes up to 32 but you can CTRL click it and enter a much larger number if you want to

About your proposal, keep in mind that ImHex uses Immediate Mode rendering. That means the entire data you're seeing on the screen is being re-rendered every single frame. So the thing you want will require a pretty beefy GPU to work nicely. Besides, personally I think having this much data on the screen will just give you cognitive overload, at least it would do that to me.

[QuantumApprentice]

"1k to 5k is an absolute MASSIVE number of bytes that need to be displayed on the screen"

1. I don't need them all displayed on the screen at the same time.
2. Microsoft Visual Studio can show 512, and HxD Hex Editor (my go to hex editor until I was introduced to this one) will go as high as 4096, 1k-5k is not unusual.
   The bigger problem for me is this editor crashes whenever I put anything above 108 into the slider.

"this is in my opinion really not how this feature is intended to be used."
3) Interesting opinion, not sure how most people think a hex editor should be used, but ok.
I'm reverse engineering a proprietary image format from a game from 1996.

"Instead you should consider writing a pattern that highlights the images"
4) This sounds useful, I'll look at the pattern language, but at a brief glance I'm not sure I can use this to align the image in such a way to make it viewable because...

"(and potentially use the bitmap visualizer to turn it into an image right away)"
5) The image format is 8-bit paletted indexed, based on a 256 color palette, some of which cycle.
Ignoring the cycling, the indexing itself doesn't translate easily to a 3 color bitmap, but I can easily see the outlines of the image itself (and thus where a frame [there are multiple frames in a file] begins and ends) if I just set the slider width to match the image width.

That being said, the visualizer looks cool, but I can't figure out how to get it to visualize anything.
Is there a tutorial I can follow that shows how to get the Read node to access the data starting at a hex address? I keep putting the address in but it keeps removing the hex value (maybe truncating it to decimal? the docs don't say). Selected region doesn't seem to work as described either.

I'm sure I'm just doing something wrong, but I can't figure out what right away :(

Whatever you decide to do with this feedback, I like this hex editor.
It seems to have a bunch of interesting features that I'm interested in, just wish I had a better understanding how to use.
Nice job! :)

[Calinou]

5. The image format is 8-bit paletted indexed, based on a 256 color palette, some of which cycle.
   Ignoring the cycling, the indexing itself doesn't translate easily to a 3 color bitmap, but I can easily see the outlines of the image itself (and thus where a frame [there are multiple frames in a file] begins and ends) if I just set the slider width to match the image width.

I wonder if it's possible to get the correct palette to show up in the image visualizer using the Data Processor to convert the paletted color data to RGBA8 colors.

That said, this would require porting the palette to the node setup, or reading it from the binary if it's stored there.