2- I'll try to come up with something for this. At the moment, pondering the idea of adding an icon on the right-hand side of the current code row that could be used to open the memory tools at that location (and potentially other things?). I'd only show the icon for the row below the mouse cursor or such. Not quite sure just yet.
3- I'll keep it like it is for now then, and see if other people ask for the same thing or not.
4- That's mostly due to the fact that I try to make each tool fit in 1024x768 res, maximum. Which leaves about 700ish pixels when you factor in the taskbar. So all that blank space can't actually have anything that's permanently there, otherwise the UI would break on smaller screens. I just added a "Use Vertical Layout" option, though. This will move the label/function lists from the right side to the empty spot, which removes any empty space and makes better use of the available space at larger resolutions.
5- I added a warning/confirmation when changing the font for any tool that warns if the font doesn't appear to be a monospace font.
6- All debugger tools should now remember their last position, and I also made the hex editor remember the memory type setting. Like you said, though, this will conflict with the F1 shortcut, but there isn't too much I can do about that.
In general, all settings should be remembered. If you find anything that doesn't get saved, let me know, it's probably a bug.
Here's a build with the changes: download
Let me know what you think.
"Additional information..." is important for me because it provides a nice seperation between frames. (I'm using a condition pc != $c2ad && pc != $c2af to skip all of the frame filler at the end of each frame. So helpful! )
Is this fixable? It has happened like four different times.
p.s. Sorry, but I feel this is important. My Override is:
Code: Select all
f[FrameCount][Align,8][A,h]|[X,h]|[Y,h] [P,8]`[SP,h] *[PC,h]:[ByteCode,11h]|[Disassembly][EffectiveAddress] [MemoryValue,h]
You can grab the latest automatic dev build with the fix from appveyor here: https://ci.appveyor.com/project/Sour/me ... /artifacts
Let me know if you still get the bug with this build.
Obviously in this case, any Appveyor build will likely end up being flagged. To be honest, I'm surprised the other builds I sent you before didn't get the same treatment.
Your description is a bit vague, so hard to say for sure. The only thing I can think of right now is.. are you pressing the Pause/Break key on your keyboard? If so, you might be triggering the internal "test recording" mode I have for my own use (which appears to be active in the appveyor builds, by mistake - it's usually disabled in any build I release manually)unregistered wrote:I feel helpless in my attempts to prevent the newest Mesen from talking about a file for recording movies on startup. I don't want it to create movie files; is this something new?
edit: Or, could you add your "test recording" mode to the short cut keys list and then we could unbind the pause button for that if we would like to? Thought maybe that suggestion would be easier on you and Mesen.
Sorry for my late reply.
Note: I have noticed that your Format: Override code must always write the entire line on every line it affects because lines that don't use the [EffectiveAddress] [MemoryValue,h] have two spaces at their end. The first space must be always added after [Disassembly] and the second space is one I kept from your example. On lines ending with an EffectiveAddress only one space is left at the end. Fix if you want to; just notifying you.
That may still be problematic for those who place Disassembly, EffectiveAddress, and MemoryValue in the middle of a line... but it sounds good to me thinking about it. Sorry, I can't test it.
I'll most likely add some code to trim the whitespace at the end of lines, just to avoid making the logs larger than they need to be, but beyond that, if you're using these in the middle of the line (like the default format), you will want to use [Align] to keep things aligned in a readable manner, anyway, so it shouldn't really matter much at all.