The "Hex Find" feature makes the cursor jump to the data byte at the specified address in the hex file.
If that location is outside the current view area of the editor, currently, the cursor is then at the correct position, but invisible.
I propose to additionally scroll the editor window to the position in that case.
I think this is reasonable because the user is probably going to do something (view, edit, ...) at the location of interest.
The current behavior seems confusing to me:
As a user, I was under the impression that the Hex Find did not succeed at all.
Only after entering an invalid address later, I found that an error message is displayed if the Hex Find really failed.
The "Hex Find" feature makes the cursor jump to the data byte at the specified address in the hex file.
If that location is outside the current view area of the editor, currently, the cursor is then at the correct position, but invisible.
I propose to additionally scroll the editor window to the position in that case.
I think this is reasonable because the user is probably going to do something (view, edit, ...) at the location of interest.
The current behavior seems confusing to me:
As a user, I was under the impression that the Hex Find did not succeed at all.
Only after entering an invalid address later, I found that an error message is displayed if the Hex Find really failed.