Re: Screen Designer for VSCode Code for i -- MIDRANGE-L

Subject: Re: Screen Designer for VSCode Code for i
From: cesco <emaxt6@xxxxxxxxx>
Date: Wed, 16 Apr 2025 08:34:27 +0000 (UTC)
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

Yes, beside proc/routine, indicators , DS navigation, a reasonable outline (like of rdi) should clearly mark where the var is referenced and - most importantly - (M)oved /set.

Usually you can have tens of reference to lines of codes that use the var, but you are after who alters it and with that you pinpoint in an instant.
We don't need AI for that ;P

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Screen Designer for VSCode Code for i , Daniel Gross

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