What I would find really intriguing is a layout where the home rows are the curves awft nuyo, a sort of workman/Jason style taken to the extreme, if you will. Assuming that those buttons really are more natural than my current method of sort of hovering between the two rows, I could see that being an awesome experiment, among other things.
Out of curiosity: How does the apostrophe key feel up there? And the slash/question in the middle? Acceptable solutions, or annoying?
Apostrophe is barely noticeable anymore (though I suspect it may still have a speed penalty). The slash/question mark are quite nice to press, possibly even better than the original position! Sadly, the same can not be said for !,\, but those are rare and I almost never hit those keys. So all-in-all, acceptable.
The other update is that I've started using amphetype to "read" (though I'll probably skip chapters where it gets too tedious, this at least ensures that my practice accomplishes something). Unfortunately, I immediately came upon the python altgr bug: none of the "command"-like altgrs (backspace, enter, and the like) work. I managed to hack in the altgr backspace (as without that I would probably have given up), by adding the following line to Quizzer.py's keyPressEvent function:
elif e.key() == Qt.Key_Backspace and int(e.modifiers()) == 1073741824: #Altgr backspace
e = QKeyEvent(QEvent.KeyPress, e.key(), Qt.KeyboardModifiers(0),e.text(),e.isAutoRepeat(),e.count())
Essentially, the altgr backspace is already triggered (Qt.Key_Backspace with modifier 1073741824); it's just that qt decided not to do anything with that modifier for some reason. So I created a new QKeyEvent that strips it of the modifier, making it just like normal backspace. You would probably have to do something similar with the other "command" keypresses.
The bad news, though, is that ctrl+[altgr backspace] doesn't work; it doesn't even seem to trigger a keyPressEvent at all. So that's pretty rubbish.
Last edited by lalop (03-Jul-2013 23:41:40)