I always wanted a setup like this to put debugging information on another screen. When I got to where I had the money to buy it, there were the beginnings of the much better approaches we have today.
It's probably worth mentioning that the idea of developing Windows software in Windows was something that only came around until 1990-91 or so. Prior to that, all the tooling (except for things like the message Spy and the resource editor) ran in the command line in text mode, including the debugger.
Visual Basic gets a huge amount of grief, but when it was first released, this was a huge part of the reason why it was so amazing. It took Windows development from a relatively complex and obscure process involving a multi-step build/edit/compile and turned it into 'drag the button where you want it, click, and add an event handler... all in Windows itself.'
It's probably worth mentioning that the idea of developing Windows software in Windows was something that only came around until 1990-91 or so. Prior to that, all the tooling (except for things like the message Spy and the resource editor) ran in the command line in text mode, including the debugger.
Visual Basic gets a huge amount of grief, but when it was first released, this was a huge part of the reason why it was so amazing. It took Windows development from a relatively complex and obscure process involving a multi-step build/edit/compile and turned it into 'drag the button where you want it, click, and add an event handler... all in Windows itself.'