Would love to be able to at least roll the program window while the monitor is still open.
Actually editing would even be better.
When there is an anomaly (bug) evident in the feedback it would be nice to be able to follow through the code to trace it.
Exactly. You're forced to choose between either reviewing the programming code or the serial output. Quite inconvenient at times.
btw, I think very highly of rev-ed's offerings (editors included), but as long as I'm finally posting in this thread, here are a few of my editor related issues. I should note that I use AxePad under Linux almost exclusively.
1) The keyboard buffer issue, mentioned before in this thread, is *almost* a showstopper. If you type too fast, or use autorepeat from the keyboard (eg, hold the 'del' key down to remove characters), then the buffer gets messed up. Then you need to re-edit what you typed since the editor buffer is now incorrect. I'm not sure if it's related to the keyboard buffer problem, but I've also seen instances where the display does not accurately reflect the editor buffer (eg, the same code line appears in 2 difference rows). At this point, I save/reopen the code being edited to be safe, though I guess this is what the "refresh" menu items is for. Either way, there's not much that's more important to a code editor than buffer integrity, so it's fortunate that this doesn't occur too often; but it'd be better if it didn't occur at all.
2) The lack of parity between Axepad and the Windows editor could be lessened. I can do without the simulator (though that would be really nice!), but the tune wizard is limited to ring-tones without even the basic note editor.
3) Opening the manuals via the help menu doesn't allow you to return to the editor until they are closed. Like the debug window, these windows are "modal", so you can't leave the manual open and return to writing code. This is very inconvenient, so I almost always end up opening up the manual from the OS instead of the editor for this reason.
4) Limited expression parsing in the preprocessor including constants would be nice. So instead of using "symbol SEC_PER_HR=3600" I could use "symbol SEC_PER_HR=60*60".
5) The fixed width for the "Code Explorer" pane should be variable width from the GUI. The column width can be set as an option, but draggable pane width selection from the GUI is pretty common these days. Perhaps it's already available within the toolkit with which the editor was built.
6) Tab is a fixed number of spaces instead of jumping to a fixed column. This makes lining up comments vertically very difficult. Not a serious issue, but definitely against my stylistic preferences.
7) The serial terminal window has fixed size; it would be very helpful to allow this window to be resized to accommodate longer text lines, or the ability to see more rows of text on screen. Right now, it is fixed at 9 rows of text.
