|
David, What version of WDSC are you using? For V6.0.x.x Open Window > Preferences. You will get a Preferences window. Expand "LPEX Editor" and click on "User Key Actions" There you have 2 fields to put information in. The 1st is the key combination, the 2nd is what action to take. You must fill in both key and action, then press the Set button to place them in the list. Once you have all of them in the list, click on the Apply button. Key Codes, a = alt, s= shift, c= ctrl The action needs to be spelled correctly, and use the correct combination of upper and lower case. In version 6 of WDSC the action has a drop down list of actions, so you have to get it right. Here is what I have, and why. a-s --> splitAndShift: This puts everything from the cursor and right on the next line, and shifts it to the cursor position. Without this, the line gets split, and the code on the next line starts at colum 1, and errors start to pop up. a-s-left --> blockShiftLeft a-s-right --> blockShiftRight This lets you use the alt + L to highlight a line, then shift the entire line either right or left. You can also use alt + R to start a highlight rectangle, shift + arrow (up, down, left right) to expand the rectangle, and then alt + shift + (left or right) arrows to shift the highlighted text and all that is to the right of what is selected. The text to the left of the rectangle stays put. a-t --> scrollTop In SEU I had my session set up so that roll up or down would put the line that the cursor was on at the top, or bottom of the page. This lets me put my cursor on a line, and the alt + T puts that line at the top of the editor. Lets me not have to grab the mouse to position the source. c-w --> blockMarkWord ctrl + W lets me position my cursor on a word and highlight the entire word. I then copy - paste, or cut, or ... Usually when copying a section of code, and then want to replace one field name with another. Ctrl + W to highlight, ctrl + C to copy the new field name, then Ctrl + W to highlight the name I want to replace, and Ctrl + V to past over that field name. Prior to iFix 2 (according to Violine from IBM) the parser did not obey the setting for column sensitive editing. To do some of the shifting you have to view the source code as one long field, and not as separate columns. This setting is in Preferences > Remote Systems > iSeries > LPEX Editor Parsers. There is a check box for column sensitive editing, as well as other settings. If you are not at iFix 2, you will need the command ' parserProperty.fields 1' at the bottom of the LPEX editor window. This sets your WDSC to always use the editor as one field. There is a command to put the editor back to the defaults. See the tread in the archives at; http://archive.midrange.com/wdsci-l/200605/msg00184.html I will be glad to answer any more questions if the above is not clear enough. HTH On 8/31/06, David Scott <dlscott@xxxxxxxxxxxxxx> wrote:
Jim, Could you point me in the correct direction to learn more about the "(with the proper easy to customize user key action enhancements)". Thanks, David Scott SmartWeb Technology, Inc. dlscott@xxxxxxxxxxxxxx (Voice) 407-671-2277 (Cell) 407-310-8106 (Fax) 407-264-6877
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.