Well yes, that's what READ EVENTS does. It just sits there and waits for events to happen.

If you're in the debugger and looking at those debug windows, then you can't be using the controls on the form and making things happen. If there are no events, then your code doesn't run.

I often end up running VFP in a normal (restored) window and not maximised, with the debugger visible to the side of the development window.
Then as I click in the VFP window I can see enough of the debugger running behind VFP to see what's going on.

You can also set the debugger to the VFP frame, which means it shares the VFP _SCREEN with your application - so you might be able to see enough of what's going on that way.

For me, two monitors would be the best solution. VFP on one and the the Debugger on the other.
It's the only way if your VFP screen has to operate at maximum resolution.