main logo
Subject: Re: Translating INKEY() codes to KEYBOARD {x} codes
Author: Nancy Folsom
Posted: 2004/06/30 12:47:23
 
View Entire Thread
New Search


Hi, Malcolm-

>Thanks for the feedback. The command buttons currently have accelerator
>(\<) keys and holding down these keys yields the expected (repeated
>click) results. The "hassle" is users working quickly and trying to
>select the correct accelerator keys in each scenario. Holding down the
>Space key is so much more natural and efficient for these users. I've
>observed their work practices first hand and agree with the
>reasonableness of their request.

Okay. FWIW, I really sympathize with your users. Accelerator keys are
good for tasks not as intensive has "heads down" data entry. I'm
trying to visualize the process that's occurring so I don't torment
you with off-topic suggestions. Is it fair to picture a data entry
from with many fields (whatever they are) and the customer moves
through the fields in order, repeatedly?

If they press any key other than a space or enter, you just want the
key to go to field that has focus. Is that correct?

If they press a space bar or enter key, you want to...move the focus
to the next field in the tab order?

I expect I'm missing something very critical about the process
because, first, I'm not sure why using a form's KeyPress instead of
INKEY(). Also, I assume that they must not need to enter spaces as a
part of text field?

Hope I'm not just being a total dolt in misunderstanding.

>I will be looking at the GetAsyncKeyState() API call as described on
>News2News.com as a possible solution. I think there's more than one way
>to skin this fox so I'm not paniced yet.

Okay. Will be interested to hear how you solve this.

>Another "odd" request (mentioned in a previous post) is that I match the
>system menu bar color of other applications in their work suite. Yes,
>Control Panel is the "appropriate" way to handle this - but as my
>customer has pointed out - recent releases of MS Office say to hell with
>this standard and use their own "more esthetic" color schemes.

Now you've hit on one of my pet peeves with MS. The bastards publish
UI standards (and they have smart people on staff who even study the
issue) and then they promptly break their own supposed standards. It
makes it nearly impossible to reign in development that, IMHO, spends
more time on eye candy than substance.



Regards-
Nancy Folsom
Pixel Dust Industries
Author _Debugging_Visual_FoxPro_Applications_
http://www.hentzenwerke.com/catalogpricelists/debugvfp.htm



 
©2004 Nancy Folsom
<-- Prior Message New Search Next Message -->