QWERTY keyboard image

[Denkster]

Add this to the manual

keys1.png (200.34 KiB) Viewed 1529 times

(I stole this image from other thread
Re: 505RC - QWERTY note input is lost after closing KB window)

Eveline

[q]

Polarbreeze had the idea of overlying the QWERTY keys atop a piano keyboard. The image is worth a thousand words and explains QWERTY in a split second.

I refined his image somewhat ... and I'm perfectly amenable making alterations. Suggestions?

I'm tempted to move the rows of letters keys closer together, more like Polarbreeze's original image, and thus more like a true computer keyboard. I kept them slightly separated to leave the lower portion of the black keys visible, but I could try transparency instead. And I could add bevels to the keys to make them more realistic.



Another thought is to center the letters and make them larger. Though that presentation would differ from how we find them on a computer keyboard, it may improve readability. Particularly in print.

q

[anaigeon]

IMHO taking in account different keyboard layouts shoulld get higher priority than picture aesthetics.

[q]

IMHO taking in account different keyboard layouts should get higher priority than picture aesthetics.

If you mean, include images for other types of keyboards, yes, of course.


http://en.wikipedia.org/wiki/AZERTY


http://en.wikipedia.org/wiki/Keyboard_layout
q

[anaigeon]

Yes, thanks, that would be fine!

[Andre]

"taking in account different keyboard layouts "

is quite more than providing an image showing a non-QWERTY keyboard.

Using the "QWERTY keyboard" function on an AZERTY keyboard (France, Belgium and their former african colonies) currently requires us to search for the

low C : on the A key which is where the US keyboard has Q
C# : on the W key Z
toggle: on the Q key A

and on a QWERTZ keyboard (Germany, Luxembourg, Switzerland, Austria, once some East-Europe countries)

searching for G# : on the Y key where the US keyboard has Z)


So obviously losing the "mapping" with the piano keyboard.

Of course, supporting our "real keyboards" could require some means to "select" the right keyboard.

[polarbreeze]

Of course, supporting our "real keyboards" would require some means to "select" the right keyboard.

The operating system always knows that doesn't it?

[anaigeon]

Of course, supporting our "real keyboards" would require some means to "select" the right keyboard.

The operating system always knows that doesn't it?

I think so, too. It's only a matter to mention scan code rather than the letter.

[Andre]

What I essentially meant, is that something has to be done in the code, not just in the documentation.

For sure the operating system knows the keyboard layout. But I'm not sure if this is readily available to the application program.
Using the scan code (physical position) is of course an option, if available to the application.

The choice of the solution is to the developper. What I meant to say about a "selection" is that, as a user, I would not object on this (this option being remembered, of course) - so I have changed "would" into "could".