Trapping Key Presses

[Deskin, Bob]

The last time we did a major enhancement review (I mean everything on
the books), this was on the list. We rated a long list of enhancements
based on risk to stability, ease of implementation, customer demand,
increased functionality, etc. While the feeling was that it was a low
risk feature and not very difficult to implement (meaning it would
probably take less than 2 weeks), it scored low on the other scales
relative to other enhancements. And really that's what it comes down to
- how important something is relative to how much we can do. So while
it's still a good idea, I don't expect that we'll see it implemented.

Bob

-----Original Message-----
From: Pickering, John (NORBORD) [mailto:John.Pickering@norbord.com] 
Sent: November 17, 2004 11:08 AM
To: Deskin, Bob; powerh-l@lists.sowder.com
Subject: RE: Trapping Key Presses


Nice segway to an old enhancement request of mine :-)

Below is the text of an old enhancement request which, judging by its
nicely formatted Courier nature, was probably faxed to Cognos at some
time long ago. The layout mimics an official Cognos enhancement request
form from the glory days of PowerHouse -- does anybody else remember
those?

I first made this enhancement request when dfk's were introduced because
without it I was not prepared to use them. I would like to use them but
we have one key set to the "$" character which means something to all
our apps and without the ability to set a key to this character, dfk's
are useless :-(

And I'd still like the enhancement implemented!


Product Enhancement Request
===========================

Client:         (two client numbers removed)

Name:           John Pickering
Address:        (removed)
                
Phone:          (removed)
Fax:            (removed)

Category:       Software
Product:        Powerhouse
Platform:       All

Title:          Allow input of data in conditional-command list.

Description:    Expand syntax of the conditional-command list to
                allow for data to be entered via the command list.
                The effect would be the same as if the data had been
                entered by the screen operator.
                Suggest syntax such as INPUT expression but will
                settle for INPUT string for now.

Benefits:       Simulate user input with PUSH and with
                PRE and POSTCOMMAND.
                Load dfk's with other than Quick navigation commands.

Examples:       >PUSH ID 01, INPUT "XX", UPDATE STAY
                             -----------
                >KEY 1 LEVEL 1 LABEL "Lookup" DATA INPUT "$"
                                                   ---------
Comments:       This is a resubmission of a previous request, last
                submitted on 92/12/18.


Regards,
JWP 
  
       This message may contain privileged and/or confidential information.  If you have received this e-mail in error or are not the intended recipient, you may not use, copy, disseminate or distribute it; do not open any attachments, delete it immediately from your system and notify the sender promptly by e-mail that you have done so.  Thank you.