• View
• Edit
• History
• Print

Bugs

This is a list of known bugs and missing features.

Before you report a missing feature, please make sure it's not already available under Tips.

• Jump to Offset feature is not working in 2.1.1 on Snow Leopard or Lion. Move selection works OK.
• The buttons in the Find banner may overlap with the left side of the window
• Generating the glyphs for the HFRepresenterTextViews could be faster
• All sorts of UI artifacts when run on Tiger (will never be fixed)
• Switching the font seems to re-set the font size to 13pt every single time (Fixed in SVN, but not in tarball or pre-compiled app.)
• Changing font settings work for the current document but revert back to Monaco-10 for every new document (although I can see that the new settings are correctly saved in the preferences plist). (Fixed in SVN, but not in tarball or pre-compiled app.)
• Clicking the up arrow in the scroll bar goes to the end instead of scrolling. The down arrow is working correctly.
• The mouse wheel does not work while above the line number column.
• Doesn't enervate the framistans
• Framework: HFLineCountingRepresenter doesn't set its digit advance when unarchived from a nib (fix: call -updateFontAndLineHeight at the end of -initWithCoder:)
• Changing fonts to one with a smaller lineheight causes the view to not resize vertically; there will be a blank space at the bottom (hex view turned off may impact behavior).
• Clicking in the scroll well above the scroller causes it to jump to the bottom.
• When changing the width of a window, the content visible in the resized window should somehow match the original window. Changing a window's width will currently send the view to some totally different part in the file.
• Copying the ascii text sometimes hangs the program in [DataView copyToPasteboard], [TavlTreeByteArray subarrayWithRange:], [TavlTreeByteArray subarrayWithRange:], [TavlTreeByteArray insertByteSlice:inRange:], [TavlTreeByteArray insertByteSlice:inRange:]
• HFFastMemchr can SIGSEGV with lengths of 14 or less. I posted a diff to fix it at http://pastie.textmate.org/private/xlzndyoezcud8vmsp9y6g.
• When comparing files >6GB the progress indicator is long done before the actual comparison finishes

• Should have a command line launcher (hexf filename or hexf < filename or hexf > filename)
• Should be able to dig in to application bundles. (i.e.) to open the binary for the app.
• Dragging or dropping text is not implemented (you can drag and drop files onto the app icon, but not into the window).
• Context menus aren't provided
• Need a way to open devices
• Need a way to show hidden files
• Need support for "bookmarks"
• Need a way to edit part of a file
• When only a blank non-edited window is open, opening a file could use that one instead of opening a new window (like in TextEdit)
• Actually, why is a blank window opened at all? I think starting an empty document from scratch would be an extremely rare occurrence in a text editor, and this behaviour just forces people to close a window they didn't want. It is also not very Mac-like behaviour.
• Commands to Increase/Decrease font size (e.g. Command +/-)
• Unicode: Displaying UTF-16 (or even UTF-8) data could be rather useful (and not quite trivial, I assume), similarly supporting more than just ASCII in the Find command would be helpful
• Add a link to your web page in the Help menu, remove the dysfunctional Help menu item.
• Preferred line number mode (dec/hex) should be saved to user defaults.
• Text only mode that honors line breaks would allow for quickly viewing really long text files efficiently.
• In text mode, low-order ASCII chars: \n, \r, \t, etc, could be displayed in backslash notation instead of as dots, a la hexdump.
• Support displaying a hash of the selected data range, to facilitate manually comparing different files or chunks of files
• Binary diff UI
• "Fill" command, and/or delete in overwrite mode filling with null bytes.
• Add ability to set an offset for the starting line number, useful if you're viewing only portions of something and the first byte is at a given offset.
• Double-click to select byte group or ASCII word. Triple-click to select line.
• Detection of changed files
• Preserve undo across file saves when possible
• When jumping to an offset in a file, the location where the cursor ends up is hard to spot - it would be nice to have some sort of callout for the quad of bytes containing the cursor like how the line containing the cursor is briefly highlighted in yellow (perhaps highlight the line in yellow, the quad of bytes in red? Or maybe just flash the yellow line, and then flash a yellow block over the quad of bytes?).

• Having the old visual style back would be nice, with spaces between each byte and separators between each word.

• Move/jump to offset not just entered in decimal, but hex; maybe as a preference? hex, decimal, or the current line number display mode.