Why are you wasting space by having the same character with different case on the fn map?
Also, having symbols on the dpad and facebuttons is a *really* terrible idea. Since a shoulder button is mapped to shift, imagine the chaos when trying to play a game...
The characters on the fn map are intended to 'fill out' the international keyboard a bit. There is no fn-shift on this definition as that combination is reserved for shift/caps-lock. Which, is, as I see now, a flaw in the design. I need to figure out something else to use as a fn-lock and shift-lock meta-key.
Note - in the versions I posted up the shoulder buttons are not defined. That was intentional. Those should be software mapped by the program that is running. That way they can be used as volume & track selection in audio players, etc... I have purposely NOT mapped shift or ctrl or any other meta-key to the shoulder buttons.
A quick note on shoulder buttons - please don't make them the physical corners of the device. That was a bad solution on the Pandora, lets not repeat that. Make them real buttons on a simple 2-contact set vertical circuit board for each side. No more flapping case corners, no more stuck shoulder buttons. Use real buttons like the game pad. Let them come through holes in the solid back of the case. Actual, real, buttons.
Indeed. Fn-Shift-<key> is also a valid combination. As is Fn-Alt and Fn-Ctrl if you really really need them.
No, it isn't. At least not on the keyboards I presented above. Fn-Shift doesn't exist per say.
Fn-SLK is intended as shift/caps lock.
Sft-FLK similarly will lock the keyboard in function mode.
So, no, you can't do fn-shift-key. You can do any combination of alt, ctrl, shift on any button on the set though. Hmmm... What it needs is another way to do fn-lock and shift-lock.
Notice that alt, ctrl and shift are closely nested in a triangle. That is intentional so that you can thumb-mash any combination of them.
A numeric keypad between the nubs is a really interesting idea!
I wonder if it is possible to fit those two extra horizontal keys between the nubs without making the device wider.
Consider the 16:9 screen dimensions on a 5" screen.
Most 16:9 screens that I have seen require relatively thick bezels on the short ends - add 5-10mm to each side for that. Maybe even more on one side than the other depending on the screen requirements.
No matter how many polls, votes or conversations we have around dimensions, the screen and it's required bezel widths will dictate the minimum width and depth.
My best estimation is that the Pyra is going to be roughly 150-155mm wide compared to the Pandora's 140mm.
Nothing says that the 10 keys between the nubs have to be the same size as the rest of the keys.
Nothing says that the keys (any) have to be the same XY dimensions on the Pyra as they were on the Pandora.
Solving the fn-shift metakey issue...
How does everyone feel about using something like:
sft+alt+ctrl = sftlock <- may have some issues as this is a possible combination on a DOS keyboard.
fn+alt+ctrl+sft = sftlock <- possible combination using button-mashing IF the keyboard can do a 4 button press.
fn+alt+ctrl = fnlock
fn+sft+alt = mode 4 keyboard map?
fn+alt+ctrl = mode 5 keyboard map?
fn+pyr = back to default map -now-?
What kinds of and how many meta-fn-shift-key combinations do we need?
