Let me start by saying that I've been using TSearch since I can't remember when (Windows 98 or Windows ME, anyway) and switching over to MHS has been one of the most difficult--though also most rewarding--things I've done. If you feel that some of these suggestions are just me asking for things to be similar to TSearch and are unnecessary, they probably are and I'll completely understand if they're 100% ignored
Your hex editor is far superior except for one aspect: if I do a ctrl+g for a certain address and it's not within the current scope of the hex editor, it'll just bring me to the last address in the current scope. It seems to me that this annoyance could be resolved by either automatically opening the memory NEAR where the user wants to GoTo in a new tab or adding it to the current scope. This is probably something that I can't live without simply because I'm so used to TSearch's hex editor, so disregard if it's not a quick, simple fix and/or too low on the todo list to attend to until you get entirely bored (which I don't see happening anytime soon =p).
When you override the simple address of a cheat table entry with an expression AND the entry is of type 'string,' it only displays the first 8 characters of the string. Say I have a multi-level pointer expression that points to the string 'abcdefghijklmnop' and add it to the cheat table: it displays 'abcdefgh.' If I add that same address as a static, simple address to the cheat table, it displays the full null-terminated string.
Would it be possible to switch out the right-click menu in the disassembler based upon whether a line has a breakpoint on it or not? If I set a bp on, say, 0x680EF8, it adds it to the breakpoint table. If I right-click on the operation at 0x680EF8 in the disassembler, it still asks me if I'd like to add a breakpoint instead of, perhaps, edit the breakpoint or remove the breakpoint.
The 'Close' button at the bottom of the allocator doesn't do anything.
I thought I had more, but apparently not; I'l continue to use it today and see what I can come up with to help, but I hope these (few) suggestions help get you closer to a final release product.
Hopefully, as I get more and more versed with MHS, I'll write a few in-depth tutorials for some of the more common (to me) but also more complex and less talked about uses.
Keep up the good work
-Shynd
Edit1: Oh, in the breakpoint table, it'd be wonderful if a 'goto breakpoint in disassembler' option was added to the right-click menu. I feel like I'm being nitpicky, now, and I promise that's not the case; I hope you don't find this post annoying.