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
Every feature in the File and Edit tabs that takes numerical input except Goto (Search, Select, Resize, Insert, etc.) parses its inputs as hex values by default. Goto, however, parses the target address as a decimal value, unless you deliberately prefix the input with 0x every time you want to jump to a hex address.
How can the issue be reproduced?
Create or load a file that is at least one hundred bytes large.
Execute the Goto command with the input 64.
Observe that the file position is now 0x40 instead of 0x64.
Do the Goto command again but with the input 0x64.
Observe that the file position is now 0x64.
ImHex Version
1.33.1
ImHex Build Type
Nightly or built from sources
Installation type
Portable
Additional context?
No response
The text was updated successfully, but these errors were encountered:
Hey, I can see how this is kinda confusing but this is on purpose.
If you check the interface it has this icon next to the text input which means this is a math field.
The idea is that you can enter mathematical expressions when wanting to jump to certain addresses, for example I often do 0xSomeSize + 0xSizeOfStructThere * SomeIndex. That wouldn't be possible if it was a regular hex input field.
What could maybe be done is just pre-filling the field with 0x by default or something like that
Operating System
Windows
What's the issue you encountered?
Every feature in the File and Edit tabs that takes numerical input except Goto (Search, Select, Resize, Insert, etc.) parses its inputs as hex values by default. Goto, however, parses the target address as a decimal value, unless you deliberately prefix the input with
0x
every time you want to jump to a hex address.How can the issue be reproduced?
64
.0x64
.ImHex Version
1.33.1
ImHex Build Type
Installation type
Portable
Additional context?
No response
The text was updated successfully, but these errors were encountered: