Hi!
Good tip.
We do it using another way. After using trick with command window opened by CTRL+F2 for some time ago, we stopped on the solution to use ON KEY LABEL and development environment startup program. Add to VFP running shortcut the command-line switch to use the developer environment config.fpw file. Then in the config.fpw file put line 'COMMAND=Do {path\}DevSetup.PRG'. In the DevSetup.PRG, after determining the user name, we define macros like following:
ON KEY LABEL CTRL+F5 ;
KEYBOARD "{CTRL+HOME}{ENTER}** CHANGED BY " + cDevName + " AT " + ;
TTOC(datetime()) + "{ENTER}" + ;
"** Change reason -- {ENTER}{UP}{CTRL+END}"
I'm not sure about the key names in the KEYBOARD command, but looks like that. And it works, for example, when you have a system allowing to edit reports in run-time and you modify code inside of the data environment of the report - in such case (You're in run-time) you will not have command window. There may be other situations of code editing when command window not available...
>In a multi-developer environment, we need a way to have bookmarks
>inserted into code BY USER.
>
>Soooo..
>
>I recorded a macro, assigned to F7, which is used in a code window:
>
>
>1. Press ENTER, then Up Arrow - This inserts a blank line
>
>2. Ctrl+F2 - Bring up command window
>
>3. _cliptext = "** BOOKMARK KM " + DTOC(DATE()) + " " + TIME()
>
>4. Ctrl+F1 - Set focus back to code window
>
>5. Press Ctrl+V - Paste in bookmark
>>
>
>
>Next, I created another marco, assigned to Shift+F7, again used with
>a code window open:
>
>
>1. Press Ctrl+F - Brings up Search window
>
>2. Type in "BOOKMARK KM" - To find ONLY my bookmarks
>
>3. Press Alt+A to enable 'All Objects' option button on search dialog
>
>4. Press Alt+N to search for first occurance
>
>5. Press ESCape to close the search window.
>>
>
>Don't forget to SAVE MACROS TO (HOME() + "Default") to save them
>to your default marcos.
>
>Pressing Ctrl+G will search again for the next bookmark.
Vlad Grynchyshyn, Project Manager, MCP
vgryn@yahoo.comICQ #10709245
The professional level of programmer could be determined by level of stupidity of his/her bugs
It is not appropriate to say that question is "foolish". There could be only foolish answers. Everybody passed period of time when knows nothing about something.