Good point, I see that under this:
Which I added *.RPGLEC copy-book, which I actually ALWAYS use the "/include" statement, instead of the old "/copy". But, I still call them "Copy-Books" <grin>
So, I know about file associations! Cool!
But, I was wondering if I am not using iProjects properly to reflect that...
So, although I use iProjects, when I need to. I am afraid I don't have 100% understanding of the proper way to use iProjects in the best way. Due to my lack of knowledge...
I also change the Parser associations to get the correct colors:
windows>Preference...>LPEX Editor>Parsers>Parser Associations
Where I set RPGLEINC/RPGLEC to show the RPGLE colors with the document parser: "ILErpg". <Big Smile>
I am not nit-picking here. But, rather pointing out that I am probably not utilizing iProjects to their full potential. Instead I might do the "Caveman" thing, and just manually update the "COMPILE.CLLE" source file, and remove the automatic creation of the "Compile.clle" program. When perhaps it could be more "automatic" with the correct source type.
Summary: I am probably not using iProject more do to my lack of knowledge to use iProject to their maximum utilization.
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Barbara Morris
Sent: Thursday, April 20, 2017 12:44 PM
Subject: Re: [WDSCI-L] Feedback on iProjects - good, bad and ugly
On 2017-04-20 11:00 AM, Ken Killian wrote:
I wish we could define more source types. Maybe something as "RPGLEC" RPGLE-Copy-Book, where it does not need to be compiled.
Source type .rpgleinc already exists.
As an Amazon Associate we earn from qualifying purchases.