Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Hack Debug Menu to remove...

Status
Not open for further replies.

Goofus828

Programmer
Nov 9, 2005
127
US
I know it can be done, you guys/gals are brilliant. How can I hack the Debug menu (VFP9) to remove the Window - Cascade option or at the least remove the hot key to the d. I am sooo tired of mistaking that keystroke for desktop's Window - Data Session.

Every time I do it, I have to rearrage the trace,watch,local, etc. windows to the way I like them.

Thanks in advance.

 
Let's me get this right. You are saying that when you are in the VFP development environment, you do Alt+W+D to open the data session window. When you are in the debugger, you do those same keystrokes, thinking you are going to open the data session window, but in fact you do a Cascade instead.

Have I got that right?

If so, my first reaction would be to stop using that particular key combo. There are plenty of other ways of opening the data session window. Get out of the habit of using those keys, and the problem will go away.

If that's not acceptable, how about recording a simple keystroke macro: Alt+W, followed by three Downs. If you run that in the debugger, it will restore the windows to their default state. If you accidentally run the same macro in the main development window, it will hide the window you just opened, which might be what you want.

Or have I compeltely misunderstood the problem?

Mike


__________________________________
Mike Lewis (Edinburgh, Scotland)

My Visual FoxPro site: www.ml-consult.co.uk
 
Mike,
Have I got that right?
Yes, that is correct

I use a dual monitor so I have the Debugger on one screen and the VFP Enviornment on the other.

it will restore the windows to their default state.
The Default state is not the layout that I use. I only use the debug,local and watch windows and they are spread out over the screen. So that does not appeal to me.

Or have I compeltely misunderstood the problem?
Here is what happens. I'm debugging the code. I encounter my breakpoint and instinctively hit Alt-W-D to bring up the Data Session to view the data, but Cascade the windows instead.[sad]

 
OK, that makes it very clear. But I think my original answer still stands: get out of the habit of using Alt+W+D to bring up the data session window. Use some other method, such as clicking on the relevant toolbar button.

Of course, if someone knows how to disable to Cascade option, or change the shortcut key, I agree that would work better. But, as far as I know, it cannot be done.

Mike


__________________________________
Mike Lewis (Edinburgh, Scotland)

My Visual FoxPro site: www.ml-consult.co.uk
 
This could mostly "fix" your debugger if it gets messed up. Might want to add a custom intellisense with this code :)

Brian

Code:
SYS(1500, "_MTL_DEBUGGER", "_MTOOLS")
DEACTIVATE WINDOW Trace
DEACTIVATE WINDOW Call Stack
ACTIVATE WINDOW Debug
ACTIVATE WINDOW Locals
ACTIVATE WINDOW Watch
DOCK WINDOW Debug 
DOCK WINDOW Locals
DOCK WINDOW Watch
 
Mike,

Code:
RELEASE BAR _MWI_CASCADE OF _MWINDOW

Removes the item from _screen, but not sure how to refer to the debugger's window menu. the _MWINDOW equivalent didn't jump out at me.

Brian
 
OK then does anyone know what the reserved word is for the Debuggin menu? something like _msysmenu. Maybe I can disable the prompt.

 
>>OK then does anyone know what the reserved word is for the Debuggin menu?

_MTL_DEGBUGGER

But that is only the "debug" option from the Main Menu. I don't know that the actual debugger menu is exposed.

The defined shortcuts are in the "Debugger Keyboard Shortcuts" help topic.

----
Andy Kramek
Visual FoxPro MVP
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top