× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



There are a few of irritants that I have with the LPEX editor under WDSc 6.0.0. Build 20050609_2105 as opposed to 5.1.2.

First, in fixed format RPG, when I press the /Enter/ key, it does *not* repeat the specification type (F,C, etc.). And I do have the preferences set (RemoteSystems...iSeries...LPEX Editor Parsers...ILE RPG: Repeat previous specification type = checked). Second, when typing a structured opcode (IF, SELECT, etc.), it does not automatically apply the closing ENDxx, which 5.1.2 did. And, again, the preference is set (same page as above: Automatic closure of control block = checked, Style = ENDXX).

Third, when I press the /Enter/ key, while the cursor is not at the end of the line, it breaks the line at the point of the cursor - which is what one would expect in Word or a text editor. However, 5.1.2 simply created a new line regardless of where the cursor was in the line. I even added a preference (LPEX Editor...UserKeyActions: enter = newLine). There is a "workaround" for this one, though: Hold the /Control/ key while pressing /Enter/. I have another action which says: backSpace = left. Works fine.

I use WDSc for editing RPG IV syntax primarily, not web development (yet). I do have both 6.0 and 5.1.2 installed on the same PC, but 5.1.2 works as described above, which is the way I want it to work.

Any suggestions, corrections would be appreciated.

Thanks.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.