Nope. Numbers need to be unshifted. Can't type line numbers as a stream-of-consciousness type thing when coding if you have to keep banging the function key before you type each line of code.
Honestly, I can't see why we don't just use the same layout as the original Pandora. We all know that one by now.
D.
Ahh - a coder then. You have a choice of two of three sets to have behind the Fn layer.
1. Numbers, which can be all in a neat and easily to find line.
2. F1-F12, which nobody has argued should be 'forward' or 'top' layer.
3. The symbol keys. `~ [{ ]} \| ,< .> /?
On the Pandora the F1-F12 and the majority of the symbol keys were on the Fn/Meta layer. The symbol key pairs were also broken - which caused a compatibility issue with certain types of software (Example DosBox) that count on shift+[ to result in {. Now we know - and can build a better layout to avoid that issue entirely.
In your coding, which do you use more? Numbers or symbols? All of those times you had to go into the Fn/Meta layer on the Pandora and sift through the randomly arranged symbols on the Fn/Meta/Blue layer of the keys to find the right symbol... The symbols don't have a strict order that makes them easy to find on the Fn/Meta layer. Numbers do.
Symbols are used more often than Numbers. Numbers are easier to find on the Fn/Meta layer than symbols are. By having symbols on dedicated keys, it opens them up as dead keys for easy diacritics, which keeps them from having to be blatantly mapped over the top of other keys. This leads to broader language support including the most common letters of the German alphabet being where they're supposed to be for the Germans - who are building this for the rest of us - and to do so without compromising English.
Modern coding relies more on symbols <>[]{};'"`~ than it does on numbers. If you're hand writing line numbers in coding though... Are you coding in Basic? Fortran?
If not, then the symbols being top side are actually more important than numbers.
Now, all that said, the numbers are very easy to get to. Note that Fn is duplicated on both the keyboard AND a shoulder button. It works just like a shift key. Hold it down with one digit and select the symbols with another. Writing a long line of numbers? That's easy too - hit both Fn keys at the same time then the numbers and F1-F12 are all 'top side' and can be typed without touching Fn. Need a symbol or letter in the middle of your numbers? Easy. When Fn-locked, press either Fn button to temporarily un-Fn the keyboard. This works just like using shift on a Caps-lock activated keyboard.
Speaking of which, shift+shift = shiftlock. Slightly different from capslock in that it shifts the entire keyboard and holds it there. This is activated by pressing shift+shift.
This design is insanely flexible and should be very efficient, but you would have to get past the knee jerk response over the numbers row being on the Fn layer. They weren't put there on a whim. Yes, it is a slight trade off, but the benefits that are gained are pretty darn cool if I say so myself.
http://www.keyboard-layout-editor.com/#/layouts/ee8d3bc8b446f99c027105d3810f8d07
Picture yourself actually using it. Consider the coding efficiency gains of having the symbols on top.
Then there is gaming.
FPS/MORPG? Lock the Fn layer top and have contiguous numbers AND F1-F12 'locked' to the active/top layer of the keyboard.
But I'm not German... what do I do with those other 3 keys?
You don't -have- to do -anything- with them. BUT - if you're so inclined, there is nothing that says you cannot map them to OS or application macros and functions and/or use them as another 3 game pad buttons. Wait - what? 3 more game pad buttons on the right?
http://www.keyboard-layout-editor.com/#/layouts/ee8d3bc8b446f99c027105d3810f8d07
⌦C ⇞Y
⇤A ⇥B
⌫Z ⇟X
Ü
Ö Ä
Note - that makes 9 buttons easily available for the right game pad area, all aligned for easy use.
This can work, it has piles of bonuses and benefits.