Great feedback! It's a bit ironic that after spending a few days really paying attention to my num pad usage, I came to the conclusion that, for me, having to put the decimal point on a fn layer would probably end up pissing me off. So, I was thinking that your original layout using the return key from the primary section of the board would be the best compromise. I hear you on the natural position of enter in the bottom right though and since nobody else has offered any input for this layout, we will go with your choice.
I think there might be a bit of confusion about the fn layer/key layout though. I was not intending to put an actual fn key on the pad, just showing the fn layer options since this is a pretty unconventional layout and if Ellipse is kind enough to do the printing of these keys, we might as well go all out with any sub legends. I was thinking that the "Nav" or "Lock" fn would be a toggle layer and you could also have the nav controls on a momentary layer as you mentioned. Are we on the same page here?
Yes we are, same page.
Regarding the decimal point, I think we just put "
↵" & "
." on the key and let everyone program their preference as main / function layer.
I have been using an ergodox exclusively the last week and, ironically, trained my right thumb to look for the return key...
now I'd probably find having the decimal there easier. What the experience brought home to me is; as long as your layout is sensible, it's not a big thing to quickly adjust your muscle memory. (BTW & OT - Who thought the default ergodox layout was a good idea? Mind you; it forced me to not be lazy and work out my own one, so maybe it's a stroke of genius.)
Can you point me to the software you were looking at? I'm happy to make a few versions of firmware that can be downloaded to go with the keycaps, or raw data to cut'n'paste into the json file; assuming that's the format, of course.