Re: Indicators on a Window

[Pete Helgren <Pete@xxxxxxxxxx>]

Bingo! That was it.  I didn't realize that once I used INDARA I need to 
map and then USE those mapped values.

Actually, it made the RPG a whole lot easier to read since I could set 
"Protect_Dsp = *on" rather than *in30=*on

Nice.  Learned something new and on a Friday!

Thanks,

Pete


Coyle, Stephen F. wrote:
> Yes...here is a snippet from a subfile....If SltPR is seton in the RPG
> my fields are protected in the DDS:
>
> A  40                                  DSPATR(PR) 
>
> RPG:
>
> FV57550    CF   E             Workstn IndDs( NamedID )
>
> D NamedID         Ds                 
> D   SflClear             31     31N  
> D   SflNextChg           32     32N  
> D   SflMode              33     33N  
> D   SflDisplay           38     38N  
> D   SflEnd               39     39N  
> D   SltPR                40     40N  
>
> -----Original Message-----
> From: rpg400-l-bounces@xxxxxxxxxxxx
> [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Pete Helgren
> Sent: Friday, October 19, 2007 12:48 PM
> To: RPG programming on the AS400 / iSeries
> Subject: Re: Indicators on a Window
>
> Steve,
>
> Tell me more.  The INDARA was already in the DDS and I was using it to 
> map function keys.  Do I need to map all indicators used for any reason 
> in the DDS from the INDARA in my RPG code?
>
> Really haven't spent too much time using INDARA, it was just part of the
>
> DDS and RPGLE code copied from elsewhere.
>
> Pete
>
>
> Coyle, Stephen F. wrote:
>   
> > The snippet DDS code is using INDARA...this sets up different
> >     
> indicators
>   
> > for the display file as opposed to your program indicators...maybe
> > you're not setting on the indicator you think you are....
> >
> > - Steve
> >
> > -----Original Message-----
> > From: rpg400-l-bounces@xxxxxxxxxxxx
> > [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Pete Helgren
> > Sent: Friday, October 19, 2007 12:10 PM
> > To: RPG programming on the AS400 / iSeries
> > Subject: Indicators on a Window
> >
> > I am a little stumped here.  I have a window that pops up and displays
> >     
>
>   
> > some fields that can be edited.  I also wanted to protect the fields
> >     
> in 
>   
> > some cases and in other cases change color or hide the fields.  I
> >     
> added 
>   
> > display attributes conditioned on indicators in the dds and tested it 
> > while using SEU (normally would use WDSc here but I am on a box
> >     
> without 
>   
> > the requisite PTF's).  Anyway, in SEU, when I set the indicator on, a 
> > field that is supposed to be hidden IS hidden.  When I run the program
> >     
>
>   
> > that displays the window, the indicator is on (I can see it in debug) 
> > but the field still displays.  It must be something in my DDS.  Is
> >     
> there
>   
> > a trick when using Window that is different than a "regular" screen 
> > format in DDS?  Snippets of DDS for here:
> >
> > http://code.midrange.com/2965d7b14c.html
> >
> > I am missing something basic, I think.  What is it?
> >
> > Thanks
> >
> > Pete
> >
> >   
> >