Multiple Monitor Debug - How Do You Do It?
I''ve tried remote debugging and I couldn''t get it to work (see my earlier post). I''m now trying multiple monitor debugging. I can get the fullscreen DX game to run in one of the monitors and I have MSVC++6 running in the other monitor. The game uses DInput with the keyboard and mouse. How do I get the focus back on MSVC++ so that I can step, etc? I can''t get the mouse there. Alt-Tab doesn''t work. How do you do multiple monitor debugging?
Thanks,
Dan
Good question. I''m starting to come to the conclusion that you can''t in exclusive/fullscreen mode. If I''m wrong I''d sure like to find out how to do it too. I can use the keyboard to step/jump, etc, but if I hit a problem I can''t do anything but exit.
Still Learning...
Still Learning...
Still Learning...
try dragging the IDE onto the second screen, then when your app goes FS/exclusive on the primary, you will still see the debugger on the other monitor
-Justin Whitejowhite@bigfoot.comAIM: Just6979www.bigfoot.com/~jowhite"To infinity and beyond!" -Buzz Lightyear"I can only show you the door. You must choose to go through it." -Morpheus"Your mind is like a parachute. It works best when open." -Anonymous"I know Kung-fu." -Neo"Ignorance is bliss" -Cihper"My name...is Neo!" -Neo
I''ve done that. I can see the IDE (and run the game) just fine. I just can''t do anything with the IDE!
It´s not exactly what you are searching, but try the "extreme debugging"-article by big big Andre LaMothe:
www.gamedev.net/reference/programming/directx/article590.asp
It describes how to write an own debugger, that runs on the second monitor.
Not too comfortable, but better than nothing.
The Smiling One (:
www.gamedev.net/reference/programming/directx/article590.asp
It describes how to write an own debugger, that runs on the second monitor.
Not too comfortable, but better than nothing.
The Smiling One (:
The Smiling One (:
Look one topic above!
There you might find more useful tips?!
The Smiling One (:
There you might find more useful tips?!
The Smiling One (:
The Smiling One (:
Finally set up multi-monitor debugging! Of course it''s not perfect, but for DX fullscreen, it''s the best!!
Try this: Use run to cursor at a location in the program, and then use the keyboard shortcuts below to debug:
Step Into: F11
Step Over: F10
Step Out of: Shift+F11
Run to Cursor Ctrl+F10
Go: F5
Stop Debugging: Shift+F5
The only problem is that my DX app seems to minimize whenever it doesn''t have the focus, but I think there''s a flag for DX SetCooperativeLevel that will fix that. Haven''t tried it though...
Good Luck,
- null_pointer
Try this: Use run to cursor at a location in the program, and then use the keyboard shortcuts below to debug:
Step Into: F11
Step Over: F10
Step Out of: Shift+F11
Run to Cursor Ctrl+F10
Go: F5
Stop Debugging: Shift+F5
The only problem is that my DX app seems to minimize whenever it doesn''t have the focus, but I think there''s a flag for DX SetCooperativeLevel that will fix that. Haven''t tried it though...
Good Luck,
- null_pointer
null_pointer, I saw this on MSDN:
"the DirectX property sheet in Control Panel. On the DirectDraw page, click Advanced Settings and select the Enable Multi-Monitor Debugging checkbox. This setting will prevent DirectDraw from minimizing your application when it loses focus."
- Hope that helped in this focus problem
"the DirectX property sheet in Control Panel. On the DirectDraw page, click Advanced Settings and select the Enable Multi-Monitor Debugging checkbox. This setting will prevent DirectDraw from minimizing your application when it loses focus."
- Hope that helped in this focus problem
Null Pointer;
I try doing that and it works up to a point. But once the initialization is done, I lose keyboard input to my game. I have it set as nonexclusive & foreground. Is there something else I should do in order to continue being able to step with the debugger?
Still Learning...
I try doing that and it works up to a point. But once the initialization is done, I lose keyboard input to my game. I have it set as nonexclusive & foreground. Is there something else I should do in order to continue being able to step with the debugger?
Still Learning...
Still Learning...
i think i have a similar problem: each time i get the focus back to the debugger, my application disappears (crashes).
Maybe it has got something to do with keyboard and/or mouse sharing...
what cooperative levels should i use?
in the dx7 docs they say something about the SETFOCUS event that i should write a special handler for, to give the focus to the parent window. what does that mean and is it relevant??
please help me any way you can, i can''t seem to get this working well by myself...
thank you
Maybe it has got something to do with keyboard and/or mouse sharing...
what cooperative levels should i use?
in the dx7 docs they say something about the SETFOCUS event that i should write a special handler for, to give the focus to the parent window. what does that mean and is it relevant??
please help me any way you can, i can''t seem to get this working well by myself...
thank you
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement
Recommended Tutorials
Advertisement