Does anyone have a problem with RDi LPEX cl Parser being very slow to open local files?

I cannot argue with you.  We are using "RDp IBM i & RTC Integration Feature    3.0.1000.v20140411_1434    com.ibm.teamp.rdp.ibmi.rtc.integration.feature.group    IBM".  RTC version 4.0.7.  I don't know enough to know where RDp ends and RTC begins. 

I do not see why opening and parsing a local file would would take the amount of time it's taking if it were truly local.  This type of delay is typical to requesting data from the server.  Of course it could be the iSeries server itself, rather than the RTC server running on the iSeries. 

I do see with the newer version, that outline information is available instantly rather than requiring a manual refresh.  If this were the cause, I would expect that RPG would be slow rather than CL since RPG outline data is quite rich while CL data is not.

I don't doubt that this is not related to RTC.  I'm only reporting my problem, and observations.  I am clueless to the actual cause.

There might be other forums that would able to help. Unfortunately we don't have a lot of RDP users here, as far as I can tell. I just try to figure if it is at least somehow related to RTC - which is kind of is.

The reason is, that we see increasingly more spam and unrelated questions, sadly.
I did not ban this, because I saw a remote chance it is CLM related. Probably it is more related to Eclipse/RDP however.

Just don't be frustrated if you don't get a response.

This update was not persistent.  Resolution was fleeting.  Still looking for a complete and lasting resolution.