(10-27-2021, 02:40 PM)AdmiralCurtiss Wrote: Just prefix the number in your search with 0x, like this:
I figured that was intuitive, but maybe not?
As for the size issue, yeah we should probably make that window remember its dimensions. I'll do that sometime this week.
Ahh thanks. Then I at least know it works. Maybe I expected it from the old GUI design too much in which you specifically had to set if you searched in hexadecimal or decimal. Maybe some tooltip or some small info tidbit could inform about this that adding 0x turns it into a hexadecimal search.
The only annoying thing would be that you have to add 0x to every search. While I know it's the proper technical use for hexadecimal values it doesn't seem very streamlined for in a GUI. Most of the time, I either only want to search as Hexadecimal or as Decimal. So I usually do a few searches using the same type. Adding 0x everytime slows down this process a bit. A checkbox to toggle between decimal or hexadecimal input would not only be more intuitive I believe, but also would have a faster workflow. That, or maybe use both ways. So adding 0x always does a hexadecimal search and the checkbox basically toggles whatever that 0x prefix is mandatory or not for a hexadecimal search. Adding 0x isn't much of an issue that would get in your way if both methods exist.
Anyway, thanks for the answer. At least I know it's still working now.
One more question since this seems new as well? Is there any difference between "Aligned" and "Unaligned"? It does seem to affect the results (aka, addresses) you get, but I am not sure how it works.