Re: Push Button fields in a DSPF

[Booth Martin <booth@xxxxxxxxxxxx>]

Hmmmm....  Have you considered a check box instead of a push button? 
That solution might be a saved preference for the user, and be 
persistent from day to day?  Sort of like a Preferences choice?  (Very 
easy to do, if desirable.)

(I believe that push buttons have to respond to keyboard keys, too, not 
just to a mouse event.  There has to be a way to identify where the 
cursor is located, at all times.  So it isn't clear to me what the 
alternative behavior might be.)

On 2/26/2013 9:13 PM, Matthew Kelly wrote:
> Booth, thanks for the reply.
> I do have a 1-byte input field with DSPATR(PC ND) on the screen.  Unfortunately, our applications are cursor-position intensive... and the subscribers to our software product are "conditioned" to the cursor positioning features of the software, and forcing the cursor to an unfamiliar location on the screen is unacceptable to them.  In addition to that, in order for that 1-byte field to be effective it would need to be positioned BEFORE the push button field on the screen, which is not always possible (we decided to use push buttons on the screen because we didn't have room for anything else).
>
> I have other applications that do use push buttons for the command keys, but this particular application isn't one of them.  The push button field I have has only one choice and, when clicked, additional features of the software are executed.  The functionality the push button field provides is not always allowed, which is why I'd like to be able to condition it's appearance... if at all possible.
>
>
> Matt Kelly | Sr. Programmer/Analyst, MED/MC Division
> CPU Medical Management Systems | Outcomes Matter
> 9235 Activity Road | Suite 104 | San Diego, CA | 92126-4440
>
> 800-597-0875 ext. 278 Direct
> 800-597-0875 Office
> 858-530-2615 Fax
> matt@xxxxxxxxxx | www.MED3000.com | www.CPUMMS.com
>
>
> CONFIDENTIALITY NOTICE: Privileged and/or confidential CPU information may be contained in this message and may be subject to legal privilege. This e-mail and any attachments are intended only for the person or entity to which it is addressed. If you are not the intended recipient any dissemination, distribution or copying is strictly prohibited. If an addressing or transmission error has misdirected this e-mail, please notify the author by replying to it and delete this e-mail from your system and destroy any hard copy printouts. Any views or opinions presented are solely those of the author and do not necessarily represent those of CPU. The recipient should check this e-mail and any attachments for the presence of viruses. CPU accepts no liability for any damage caused by any virus transmitted by this e-mail.
>
>
> -----Original Message-----
> From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Booth Martin
> Sent: Tuesday, February 26, 2013 6:23 PM
> To: RPG programming on the IBM i (AS/400 and iSeries)
> Subject: Re: Push Button fields in a DSPF
>
> I am not entirely clear on the issue.
>
> You could put an unused one-character input field,
> marked as DSPATR(PC ND) at the place om the screen where you want the
> cursor to actually park when the format is displayed?
>
> Another possible choice is to add push buttons so that the display uses
> push buttons for the enabled Command Keys?
>
> On 2/26/2013 5:37 PM, Matthew Kelly wrote:
> > When using push button fields on a screen with no other input-capable
> > fields, how can I condition the push button field so that it doesn't
> > inadvertently highlight (because it's the only input-capable field on
> > the screen) on the first output operation to the DSPF?
> >
> > Also, is there a way to either hide or protect a push button field?
> >
> > I'm working on an iSeries running V6.R1 of the OS.
> >
> >
> >
> >
> >
> > Matt Kelly | Sr. Programmer/Analyst, MED/MC Division
> >
> > CPU Medical Management Systems | Outcomes Matter
> >
> > 9235 Activity Road | Suite 104 | San Diego, CA | 92126-4440
> >
> >
> >
> > 800-597-0875 ext. 278 Direct
> >
> > 800-597-0875 Office
> >
> > 858-530-2615 Fax
> >
> > matt@xxxxxxxxxx | www.MED3000.com <http://www.MED3000.com>  |
> > www.CPUMMS.com <http://www.CPUMMS.com>
> >
> >     <http://www.twitter.com/CPUMMS>
> > <http://www.facebook.com/pages/CPU-Medical-Management-Systems/2314314568
> > 97085>
> >
> >
> >
> > CONFIDENTIALITY NOTICE: Privileged and/or confidential CPU information
> > may be contained in this message and may be subject to legal privilege.
> > This e-mail and any attachments are intended only for the person or
> > entity to which it is addressed. If you are not the intended recipient
> > any dissemination, distribution or copying is strictly prohibited. If an
> > addressing or transmission error has misdirected this e-mail, please
> > notify the author by replying to it and delete this e-mail from your
> > system and destroy any hard copy printouts. Any views or opinions
> > presented are solely those of the author and do not necessarily
> > represent those of CPU. The recipient should check this e-mail and any
> > attachments for the presence of viruses. CPU accepts no liability for
> > any damage caused by any virus transmitted by this e-mail.