FKey 182

John · Post by **John** » Mon Jun 29, 2009 9:26 am

I'm getting occosional strange results working with an AEX grid and an AEX text box where occosionally clicking the textbox will return an FKey value of 182.

It's seems strange to me.

Does anyone know anything about FKey 182? I don't think I've ever encountered this particular FKey value before. there is nothing about it on our FKey page.

Post by **gordon** » Tue Jun 30, 2009 9:16 am

Can you reproduce this?

Can you provide an example?

John · Post by **John** » Tue Jun 30, 2009 2:24 pm

i can reproduce it. i can write an example, but not for a few weeks, I'll try to remember to do so. I documented the behavior as best as i could on the fkey page of the br!wiki.

Post by **Susan Smith** » Tue Jun 30, 2009 2:37 pm

Hi John,

Pardon my ignorance, but what is an AEX Grid and AEX Text box? I haven't heard the term "AEX" before.

-- Susan

John · Post by **John** » Wed Jul 01, 2009 6:46 am

Okay, so I kinda sorta just made up the terms.

What I meant was a grid that utilizes the A, E, and X attributes.
(see also http://brwiki.ads.net/index.php?title=Definitions )

and a textbox that does also (i.e.)

10 in f '10,10,C 1,AEX': quick_sample$

with A, E, and X all in use any time you arrow off of a field or click a fkey is set and control is returned to the program.

-John

Post by **gordon** » Wed Jul 01, 2009 11:35 am

I just tried it with 4.20d and it produced the proper FKEY values.

Right arrow produced 116 and down arrow produced 104.

Documenting erroneous results on the wiki is counterproductive. Please remove such documentation.

After this, please report such anomalies and if they don't conform to the documentation regard them as an error. For quicker resolution please provide an example.

John · Post by **John** » Wed Jul 01, 2009 1:25 pm

Sorry - I didn't know it was an error - I figured it was a feature I just didn't understand.

I don't really need a resolution - I just need documented behavior so I know how to write my code.

Personally I like the behavior being documented (erroneous or not) because next time I write a AEX grid and AEX textbox combination I need to remember about fkey 182. At least with the version of BR! that I'm using (4.18g).

I would perfer to note that this behavior was only with versions of BR! prior to such and such rather than pretend that the behavior never existed. Isn't that the purpose of documentation? To document the behavior, not document what we'd like the behavior to be?

I don't have time to write a stand alone test and instructions for you now, but I will in a few weeks when I'm not under so many deadlines.

-john

Gabriel · Post by **Gabriel** » Wed Jul 01, 2009 1:27 pm

John,

Its possible that your strange results are coming from some other piece of your code, such as Substitute Keyboard Statements, or some Fkey (hottext) value being placed in your controls. We can't really tell until we can see a simple example of your code demonstrating the error.

Gabriel

John · Post by **John** » Wed Jul 01, 2009 1:39 pm

I will do as you ask me to.

Post by **gordon** » Wed Jul 01, 2009 9:39 pm

The purpose of the documentation is definitely NOT to document erroneous attributes of any release as though they were features, but to say that such and such is a known error.

If the product doesn't match the documentation then we should fix the product. Certainly not document some goofy attribute that's going away in the next release.

Since I tested 4.20 on this without failure, it will be necessary to provide a sample before we can fix it.

Meanwhile please remove the documentation fron the wiki that describes this result.