Re: Indicator documentation

["Mark Allen" <scprideandms@xxxxxxxxx>]

I recently did a project where I was NOT allowed to use indicators in DSPF's
for controlling screen attributes, never knew it could be done
RPG Snippet:  does this line if there as an error with the SKSSKU field

eval      sksskuatr=$red
(where I have $red as a named constant set to the the hex value for red X'28
along with all the other various attributes i.e. $nd for non display,
$redhiri for red high intensity, reverse image......

kinda neat, nto sure if it really makes it any clearer or not......



A            SKSSKUATR      1A  P
A            SKSSKU    R        O  8 35REFFLD(RSKMST/SKSSKU *LIBL/
A                                      EDTCDE(Z)
A                                      DSPATR(&SKSSKUATR)


On 2/28/06, David Gibbs <david@xxxxxxxxxxxx> wrote:
>
> Paul Tuohy wrote:
> > I hope you mean RPG indicators as opposed to indicators in general.
>
> Absolutely ... I'm talking about 01-99.
>
> > Named indicators are good things and very useful.
>
> I don't consider those 'Named indicators' ... they are boolean fields.
>
> I just wish there was a way to communicate with display files with
> boolean fields instead of indicators (spit).
>
> david
> --
> This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
> To post a message email: RPG400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/rpg400-l.
>
>