F5 in edit code

[Guest.Visitor]

I am interested in finding a way to make F5 work in the editor and I followed all the steps outlined bellow. So far it is not working. The CLEAN.LX macro is in C:WDT400MACROS folder along with the PROFILE.LX macro (which I backed up and modified) Additionally, when I looked in HELP under Writing Macros for Editor, I encountered the following line: "Ensure that the file is in a directory that is on your CODELPATH" I am not sure what this means. Please advise. 1) you will need to create a macro called CLEAN.LX (which will clean up the prefix area) in your user macro directory. Here is the content of the macro: /* clear prefix area */ 'EXTRACT LINENUMBER' 'EXTRACT POSITION' 'TOP' 'EXTRACT LINES' into numLines i=0; do while (i<numLines) 'SET PREFIXENTRY' 'NEXT ELEMENT' i=i+1 end 'FIND ELEMENT 'linenumber 'SET CURSORCOL 'position 2) You will need to modify your PROFILE.LX file to include the following line (at the end of the file): 'SET ACTION.F5 ;MACRO SEUCMD RESTORE;MSG ;MACRO CLEAR'

[batthish@ca.ibm.com]

Hi Valerie, The WDT400MACROS directory is already in the LPATH, so you don't need to worry about that. Please do the following: 1) In the Editor command line type QUERY ACTION.F5 (you should see 2) Try using F5 Look at the macro log (Windows->Macro Log) and see what is displayed there. If you post the log, I might be able to see what is going on. Thanks, Violaine Batthish CODE Project Lead Toronto Lab, IBM Canada

[batthish@ca.ibm.com]

Oops, I noticed that I said to call the macro CLEAN.LX, but it should be CLEAR.LX since I also said to include the following line in profile.LX: 'SET ACTION.F5 ;MACRO SEUCMD RESTORE;MSG ;MACRO CLEAR' Sorry! Violaine Batthish CODE Project Lead Toronto Lab, IBM Canada

[batthish@ca.ibm.com]

Hi Valerie, I think I just realized what the problem is: I noticed that I said to call the macro CLEAN.LX, but it should be CLEAR.LX since I also said to include the following line in profile.LX: 'SET ACTION.F5 ;MACRO SEUCMD RESTORE;MSG ;MACRO CLEAR' I'm guessing that if you rename the macro to CLEAR.LX everything should be OK. Sorry! Violaine Batthish CODE Project Lead Toronto Lab, IBM Canada