|
|
|
|
|
|
by jauntywundrkind
855 days ago
|
|
|
> I am a heavy user of a proprietary one-handed keyboard system. Recent maintenance issues and the lack of user serviceability have turned my attention to creating a more reliable solution. Oh no! That's so sad to hear. I was overjoyed when the new BT model came out; I was finally going to get to do the thing & get good at this. A couple years latter I actually made an effort to really learn it & get a little competent. For whatever reason (allegedly more coder friendly) I almost immediately adopted TabSpace layout & printed up a half dozen key map graphics so one would always be at hand. It was a fun time but I never committed hard enough. I'm also just shocked how effective & capable I am at writing on a touchscreen. I'd tried some more code-oriented keyboards for coding, and this was a while ago but they lacked most of the intelligence/helpfulness of a mainstream touch-keyboard & weren't something I could hard adopt. In the meantime, the mainstream touch-keyboards forever annoy me; I really wish long presses could offer a lot more options but we seem forever consigned to be flipping between screens to get a special character or two. I'm super excited to hear of Twiddler / one handed users in the wild. That's crazy awesome that you build your own! That it only takes 8 keys is a feat! |
|
|
TBH, the the Twiddler layout is probably superior (though not by much). I went with eight traditional keys because it could be hand wired. The Twiddler approach is basically limited to soldering directly to a board, with all the issues therein. After about six months or so I would get debris caught under one switch or another and the Twiddler is basically welded shut. :/
Speaking of design issues (and talking about the BT). I highly recommend using a Nice! or other wireless/BT microcontroller. Not only is it more convenient but cable strain is a real issue on most microcontrollers. If the Handler has a design flaw, that's the biggie.