|
Jerry, this might be a dumb question but... are you sure the source member you have open is of the correct type? Is it RPGLE or what? Under Preferences/Remote Systems/iSeries/LPEX Editor Parsers/... there is CL,COBOL,DDS,ILE RPG, and RPG/400. I don't know but it sounds to me like the LPEX editor doesn't like your source type for some reason so isn't using the preference settings you are defining. John. -----Original Message----- From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Jerry Adams Sent: Monday, October 31, 2005 7:30 AM To: WDSc Midrange Subject: Re: [WDSCI-L] Preferences - LPEX Editor Well, even though I didn't hold out much hope, I uninstalled both WDSc 6.0 and 5.1.2, then installed 6.0 from scratch and installed the updates. Re-define my preferences which should handle these issues. Didn't work. All of the issues, which I stated below, still exist. Since one respondent said that these work fine for him, I can again only surmise that there is some preference, somewhere that conflicts with or overrides these. If so, it isn't obvious (to moi, anyway) as I went through every single preference section and every panel within each section. As far as the "Enter" key issue goes, there is a workaround (Ctl+Enter). The action 'newLine' may not be the proper action, but it was the only one that I could find that made sense, and it was the option I used in 5.1.2. But the change I made to the "backSpace" key ('left') works fine in 6.0. I don't expect any responses as everyone has already had a look at this, if they wanted to. But if anyone should have an epiphany, give me a buzz. Thanks. * Jerry C. Adams *iSeries/i5 Programmer/Analyst B&W Wholesale Distributors, Inc.* * voice 615.893.8633x152 fax 615.995.1201 email jerry@xxxxxxxxxxxxxxx <mailto:jerry@xxxxxxxxxxxxxxx> Jerry Adams wrote: > Well, just spent three hours downloading and installing the update. > These issues (below) remain. I checked the preferences, as indicated > below. In fact, I went through every preference panel, but could not > find anything directly relevant that I did not indicate below. > My only thoughts are that: > > 1. There is a preference setting that is indirectly affecting my > results, or > 2. The fact that I have both 6.0 and 5.1.2 running on the same PC > might be causing a clash. > > Reasonably (to me, anyway) I doubt #2 is the problem because 5.1.2 > works as advertised. > > I've had others tell me that these are not issues with them, too. So > obviously it's a personal issue. I just don't know how personal. If > not one else has any suggestions, I may just bite the bullet tomorrow: > uninstall both versions and install 6.0 alone. > Thanks. > > > * Jerry C. Adams > *iSeries/i5 Programmer/Analyst > B&W Wholesale Distributors, Inc.* * > voice > 615.893.8633x152 > fax > 615.995.1201 > email > jerry@xxxxxxxxxxxxxxx <mailto:jerry@xxxxxxxxxxxxxxx> > > > > ssc1478@xxxxxxx wrote: > >> >>> 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. >> >> After getting the updates, I have Version: 6.0.1 Build id: >> 20050725_1800. >> >>> 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). >> >> This works for me. >> >>> 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). >> >>> >> >> This works for me. >> >>> 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. >>> >> >> This works for me also. To break the line, I have to press alt-s. >> (I wish it wouldn't put the text starting at column 1.) >> >> >>> 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. >> >> >> >> I don't know if the updates fixed what you're experiencing because I >> don't recall having those problems before I got the updates. (I >> don't use the automatic closure feature so I can't comment on that.) >> >> hth, >> Phil >> >> >>> >>> Thanks. >>> >>> -- * Jerry C. Adams >> >> >> *iSeries/i5 Programmer/Analyst >> B&W Wholesale Distributors, Inc.* * >> voice >> 615.893.8633x152 >> fax >> 615.995.1201 >> email >> jerry@xxxxxxxxxxxxxxx <mailto:jerry@xxxxxxxxxxxxxxx> >> >> -- This is the Websphere Development Studio Client for iSeries >> (WDSCI-L) mailing list >> To post a message email: WDSCI-L@xxxxxxxxxxxx >> To subscribe, unsubscribe, or change list options, >> visit: http://lists.midrange.com/mailman/listinfo/wdsci-l >> or email: WDSCI-L-request@xxxxxxxxxxxx >> Before posting, please take a moment to review the archives >> at http://archive.midrange.com/wdsci-l. >> >> >> ________________________________________________________________________ >> Check Out the new free AIM(R) Mail -- 2 GB of storage and >> industry-leading spam and email virus protection. >> >
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.