non-QWERTY keyboard

[taterday]

Has anyone encounter a problem with a non-QWERTY keyboard causing problems with VFP 7.0? If so, how did you solve the problem?

Thank you,

Tater

 

[Mike Gagnon]

And the crystal went out....What problem are you having?

Mike Gagnon

If you want to get the best response to a question, please check out FAQ184-2483 first.
ReFox XI (www.mcrgsoftware.com)

 

[taterday]

click event does not work.

It seems to be disabled. Only the ones with non Qwerty keyboards are having problems.

 

[taterday]

This was the first thing they were to do so there may be more problems to follow.

I use install shield 2008 to build the setup.exe. Are there something I should include in the build to account for these types of keyboards?

 

[Mike Lewis]

When you say "non-QWERTY", do you mean an ordinary keyboard with a non-Enlish layout (such as AZERTY)? Or do you mean some exotic non-standard input device of some kind?

If the former, it's highly unlikely that this would prevent a Clik event from firing. Just think of the thousands of French and German and other developers who are using VFP every day. Is it conceivable that they have to do something different from the British and American and Australian developers to trap a mouse click?

I'd suggest you try to analyse the problem a bit more carefully and look for other things that could cause it to happen.

Mike

__________________________________
Mike Lewis (Edinburgh, Scotland)

Visual FoxPro tips, advice, training, consultancy
Custom software for your business

 

[Mike Gagnon]

taderday

What do you mean "click event"? What key on the keyboard would you use to trigger a click event? "Enter"?

Mike Gagnon

If you want to get the best response to a question, please check out FAQ184-2483 first.
ReFox XI (www.mcrgsoftware.com)

 

[JRB-Bldr]

As others above have inferred, the "Click" or "Double Click" methods/events are triggered by a mouse button clicking on an object - not by some key stroke from the keyboard.

NOTE - a QWERTY (a.k.a. 'English standard') keyboard is so named due to the key button layout on the top-left character row - keys: Q W E R T Y
Typically a non-QWERTY keyboard is nothing more than a standard keyboard which has a different key button layout.

As such it is not different in any other way in what it sends to the computer and, in turn to the VFP application.

If you should have some 'way out' keyboard which is sending totally unique data to the computer (and to the VFP application) for some or all of the key strokes, then I'd suggest getting rid of those keyboards.

You could always write yourself some small diagnostic VFP program to display the keyboard input in its RAW state and compare the input from a regular keyboard and these unique ones.

Good Luck,
JRB-Bldr

 

[taterday]

Mouse click to enter a text field.

I will check on the keyboard type. I was told it was ...
I assumed it was a Dvorak keyboard.

Thank you for helping me get my thoughts together.

Tater