We have RPGLE copy code that was not given the RPGLE member type and I can still open it in LPEX with proper parsing (on Windows 7, RDi 9.5.1.0). In order for me to associate the member to a proper parser I have to look at the member name extension used in the edit tab. Take that extension and create a link between it and the LPEX editor (Preferences -> General -> Editors -> File Associations). I then have to look to see if a parser association is made between the member type (extension) and the parse I want Preferences -> LPEX Editor -> Parsers -> Parser Association. I might be as simple as case of the member file extension, (e.g., .java vs .JAVA).
Thanks, Matt
-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Jon Paris
Sent: Monday, September 12, 2016 1:40 PM
To: Wdsci-L <wdsci-l@xxxxxxxxxxxx>
Subject: [WDSCI-L] Source type association issue
I’ve never seen this before and I’m hoping it rings a bell with someone.
Using 9.5.1 (Mac if it matters)
If I open a .java file from the IFS or my local drive the color coding etc. works perfectly.
If I open a java file from a source physical there is no color coding - it is all just an ugly blob.
Only thing I can see is that java does not appear on the list of source types for a source physical. But it does show as a property for the file in question.
Jon Paris
www.partner400.com
www.SystemiDeveloper.com
--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & 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.
midrange.com
