Annoying VC6 Disassembly Window
-
Hi Does anyone know of a way to completely disable the Disassembly window? Currently when the window appears, I always press CTRL+F4 to close it, as it's completely meaningless to me. Ideally I would like to NEVER show the Disassembly window. Or does anyone know of a macro which could close the Disassembly window straight after it opens? There must be a way...........
Cheers d3m0n
-
Hi Does anyone know of a way to completely disable the Disassembly window? Currently when the window appears, I always press CTRL+F4 to close it, as it's completely meaningless to me. Ideally I would like to NEVER show the Disassembly window. Or does anyone know of a macro which could close the Disassembly window straight after it opens? There must be a way...........
Cheers d3m0n
And thus another example of the problem with the current state of Software Development education programs! :) Heh - I think that the Disasm. window is one of your best friends. Nothing better than seeing exactly what your code did or is about to do. Its best use so far was using to track down a compiler bug in an older version of the VC++ compiler that involved returning the result of a boolean operation from a function. Something like:
bool bValueA = false;
bool bValueB = true;return( bValueA || bValueB ) // or maybe it was bValueA
&&bValueBThe compiler generated code that performed he operation, but then returned the value of one of the operands instead of the result of the operation. I know I could not do it it without that window handy... Peace!
-=- James
Please rate this message - let me know if I helped or not! * * *If you think it costs a lot to do it right, just wait until you find out how much it costs to do it wrong!
Avoid driving a vehicle taller than you and remember that Professional Driver on Closed Course does not mean your Dumb Ass on a Public Road!
See DeleteFXPFiles -
> Heh - I think that the Disasm. window is one of your best friends Nope, it really isn't. :) If you know how to use the Disassembly, it can be very powerful, but the source files, call stack and quickwatch is all I need. I just don't ever use the Disassembly and for me it's just annoying. Please someone tell me how to make it go away!!
Cheers d3m0n
This is strange I have never seen that the disassembly view keeps coming up, when its closed from the user. It normally only shows when you debug into a line of code that doesn't contain any debug info, like debugging into 3th party libraries. If thats the case you should step over instead of step into.
codito ergo sum
-
And thus another example of the problem with the current state of Software Development education programs! :) Heh - I think that the Disasm. window is one of your best friends. Nothing better than seeing exactly what your code did or is about to do. Its best use so far was using to track down a compiler bug in an older version of the VC++ compiler that involved returning the result of a boolean operation from a function. Something like:
bool bValueA = false;
bool bValueB = true;return( bValueA || bValueB ) // or maybe it was bValueA
&&bValueBThe compiler generated code that performed he operation, but then returned the value of one of the operands instead of the result of the operation. I know I could not do it it without that window handy... Peace!
-=- James
Please rate this message - let me know if I helped or not! * * *If you think it costs a lot to do it right, just wait until you find out how much it costs to do it wrong!
Avoid driving a vehicle taller than you and remember that Professional Driver on Closed Course does not mean your Dumb Ass on a Public Road!
See DeleteFXPFiles> Heh - I think that the Disasm. window is one of your best friends Nope, it really isn't. :) If you know how to use the Disassembly, it can be very powerful, but the source files, call stack and quickwatch is all I need. I just don't ever use the Disassembly and for me it's just annoying. Please someone tell me how to make it go away!!
Cheers d3m0n
-
This is strange I have never seen that the disassembly view keeps coming up, when its closed from the user. It normally only shows when you debug into a line of code that doesn't contain any debug info, like debugging into 3th party libraries. If thats the case you should step over instead of step into.
codito ergo sum
It also comes up when the "User breakpoint called from code at 0x..." dialog appears. I use 3rd party libs without the source, and so if you get an assertion in that code, the Disassembly window shows its ugly head again. I even tried to undock the Disassembly window and make it really small and just off my screen - this worked for a while but then for some reason it maximized again. Gah. X|
Cheers d3m0n