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
As part of support for debugger memory, we wanted to refactor the hex editor to support arbitrarily large files. This was a significant set of changes. While we still use extension host APIs which only support reading entire files into memory, the infrastructure is there to remove this restriction and add use cases and we focused on reaching parity with the previous version of the hex editor.
Therefore, please go through the hex editors and verify everything works using this vsix: hexeditor-1.8.2.vsix.zip
Viewing of bytes and scrolling works
Navigation works via keyboard
Selections work. Selections can be added/altered with modifier keys
Editing bytes work. Edits should be shown with a diff background (blue by default) while unsaved
Undo/redo works
Find works (ctrl/cmd+F for the widget as usual). The total number of results is limited to 10k by default, but can be increased by clicking the result number.
Find and replace works
The data inspector works
The "Hex Editor: Go to Offset" command works
The text was updated successfully, but these errors were encountered:
Ref #15756
Complexity: 5
Authors: @connor4312, @lramos15
Create Issue
As part of support for debugger memory, we wanted to refactor the hex editor to support arbitrarily large files. This was a significant set of changes. While we still use extension host APIs which only support reading entire files into memory, the infrastructure is there to remove this restriction and add use cases and we focused on reaching parity with the previous version of the hex editor.
Therefore, please go through the hex editors and verify everything works using this vsix:
hexeditor-1.8.2.vsix.zip
The text was updated successfully, but these errors were encountered: