Hi Grazey, > A few of additions for the debug build please (if they're easy to > implement!) > > 1) Can you include "Run to RTS" as well as "Run to RTE" or alternatively > have a Trace button (similar to Control T in Monst) eg jump into sub routine > run and return. This is much requested, so much requested even I had to get off my arse and put it in! :D I've done it the MonST trace-like way, the only problem I have now is what to name it. So far I have normal trace as "Trace Into" and the new option as "Step Over", that seems to be rather different to MonST, is there any sort of standard for naming these things? It seems to be different in every debugger I have ever used. > 2) Can you add an ascii browser which displays rows of 32 bytes? currently > the memory browser only displays 4 bytes per row. You can expand the Hex column to increase the number of bytes on a line if that helps. I have made it so in the next version shrinking the Hex column to nothing will cause 64 bytes to be displayed per line, that should come in handy for text. > 3) Timer specific trace in the debug build.... one can hope ;-) Well I thought this would be really difficult but I fiddled with it the other day and it seems to work pretty well. As long as you don't start tracing the blitter in non-hog mode it does the job. > The reason for this is I'm slowly moving over to Steem for my music ripping > and those options would certainly help the process. Well I hope they do, I've also done some more things like separating breakpoints and memory change monitoring and break on interrupts, hopefully they will be useful too. Russ -- Steem - http://www.blimey.strayduck.com/ Manage your list membership - //www.freelists.org/ Click here to unsubscribe - mailto:steem-request@xxxxxxxxxxxxx?subject=unsubscribe