Re: Are you as polite and diplomatic as COBOL?...

Kellie Fitton wrote: 
Richard wrote:

and forces the end-user to click on the button

If the button is a default button or has focus then 'enter' can be 

used

without moving the hands off the keyboard. 


Kellie Wrote:
Hi Richard,

I don't think you read the entire thread nor understood what jimmy and
I were talking about, simply because you are mixing apples with
oranges.
again, my point was: I do NOT WANT any PAUSING or HAULTING of programm
flow or execution, while the end-user is entering his data, it has
nothing to do with a button or the enter key, period. Capite??


So, after criticisng something for 'having to click' you now advocate
'having to click'.
"Consistency is the hobgobblin of tiny minds."



Again, you are mixing apples with oranges, I was simply trying to point
out the fact about how to enter DATES and TIMES in a dialogBox, IF the
end-user have the needs to do so in a graphical environment, simply
because jimmy have mentioned how to format a DATE in his reply, it has
nothing to do with the mouse or clicking, period. Capite??

Regards, Kellie.

Kellie,

I really don't want to flog this one to death, but I did not specifically say PAUSE on each error - that is not how I work. Just re-check my two messages. (On PB-OK I use a validation routine to cycle through entry-fields).

As to the Date-Picker - fine, and as illustrated by PECD can also be useful. But I keep on saying don't be adamant there is a one-only solution. I didn't mention with reference to Quickbooks that EVERY dialog that has a date field has a DATE-PICKER ICON - and I *USE* them in Quickbooks.

But in the application I'm most interested in your Date-Picker is a hindrance. The application allows for 10 inspection dates. If the company is picking up a new contract then they could face the possibility of keying-in some six years history - the prime reason I've gone SQL to receive and send data.

As to the dates they could be :-

Feb 77, Feb 78, Apr 79, Mar 80, Jan 81, Feb 82

Although roughly the system works on a 12-month cycle, not always the case and not always a clean 12-months. And it can differ from Item to Item being inspected; the table above might fit 80% of the Items but not all.

So I go with YYMM, (I'm not not interested in the Days) and translate 7702 to display Feb 1977, and in the DB I'm storing yyyymm.

Six dates x 4 characters + Tab between each =  30 (clicks/keystrokes etc.)

Now think in terms of your Date-Picker - what's the count for your (clicks/Keystrokes/forwards and backwards arrows) to achieve the above Date Table ?

-----------------------------------------------------------------------
Now your first message of April 28th concluded :-

"I would greatly appreciate your thoughts and comments".

but turned out to be :-

"I would greatly appreciate your thoughts and comments, and then I will refute what you suggest with counter-arguments".

Quite simply - I wouldn't have commented at all, nor will I be doing so in the future.
------------------------------------------------------------------------


Jimmy
.

Quantcast