Haha cheers Chris, without looking at Beepola's source code I arrived at pretty much the same conclusion, just haven't implemented it yet. Of course the plug-in system makes things a little more complicated. The idea is that each engine configuration should provide a list of possible breakpoints (because there are engines that don't pass through a single code point for sequence and pattern data read operations). When hitting one of the specified breakpoints, the emulator will do a callback. As long as the UI keeps track of the current playback position, it can automatically determine whether the next operation is a pattern or a sequence read. The only problem is that there may be engines that use pattern jumps. In that case, keeping track of the playback position suddenly becomes much more complicated.
Thanks for your comments 4thRock, much appreciated
Yep, agreed. Will work on that.
Well, as chrrris explained, it's not that easy to do. I do have plans however to have at least some sort of playback position indicator.
You can change the window size in the ini file. I haven't implemented in-program window resizing yet because that's quite a big can of worms to open, actually. And the graphics code in Bintracker is pretty dodgy already, so I want to rework that first before moving forward with extra features like resize, fullscreen support, different font sizes etc.
That's a good idea, hadn't thought about that. I think on the long run Bintracker also needs to have support for MIDI input