Hi Scott,

it seems to me that the support of RDi for sources in stream files is not so good as for sources in source files. I detected that when opening a stream file in LPEX editor the stream file will not be locked. When opening members in source files the members will be locked.

Perhaps we should collect all the things RDi should have for handling sources in stream files and then we open a "Request for Enhancement".

Frank



-----Ursprüngliche Nachricht-----
Von: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx> Im Auftrag von Scott Klement
Gesendet: Samstag, 5. März 2022 05:59
An: wdsci-l@xxxxxxxxxxxxxxxxxx
Betreff: Re: [WDSCI-L] LPEX editor and stream files containing ILE RPG source

Hey, Frank... I'd love to see this as well! The fact that the include directory is one global setting for all files is clumsy

I'd also like to see some way of just typing the name of a file to open, instead of having to create a filter, get a list of hundreds of files in the directory, and having to scroll through it and find the one I want. For source members, I can just type the file/lib/member name, but for IFS I have no choice but to sift through the files in the file system to find it.

IMHO, using stream files in the IFS is the future, so these would be a great way to keep RDi as the leading IDE for IBM i as times continue to change.

On 3/4/22 2:34 PM, fhildebrandt@xxxxxxxxxxxxxxx wrote:
Hi Steve,

this is what I was looking for. Thank you.

I have another question. The section "Include Directory" is on a
global level. I have a lot of connections in the remote systems
explorer and the different connections need different include
directories. Is there a way to handle this?

Frank


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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

This mailing list archive is Copyright 1997-2022 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.