On full-size, TKL and 1800 layouts, finding the cursor keys with just your fingers is easy due to the gap around them. But what about 90%/95% boards like the Kira or the Vortex Tab90/Tab90M where there’s no gap around the arrow keys nor between the main and the number block?
On my own Tab90M I replaced the grey cursor keys with yellow ones (both sets came with the keyboard), but without looking I often hit the wrong key. Granted, using a non-sculpted VSA profile (similar to DSA) for such a huge amount of key without gaps isn’t really helping either. I also had issues finding the Enter key easily and not hitting PageDown (right of it) instead.
So I recently exchange the stock VSA Dolch key cap set with the Git kit from GMK Oblivion. Colorwise not a big change as both are dolch-ish. But a big change in the profile from non-sculpted to sculpted.
On the Tab90M, there’s a 65%/75% style column with Delete/Home/PageUp/PageDown/End/Right keys between the main and the number block. But despite all these keys are available in the proper row-profile (R1/R1/R2/R3/R4/R4) in the kit (or at least those kits I purchased), I decided it’s better to have all these key caps except the “Arrow Right” key cap in R1 profile to build up a perceptible “wall” between the main block and the number pad. And on the bottom left of it is the cursor block:
I’m quite convinced that this is a help when navigating with the fingers on that huge keyboard, but then again I still occasionally hit the Right Control (labelled “Pull” in the picture) instead of the “Arrow Left” key. (Maybe caused by being used to the way smaller MiniVan with only one key between the cursor cross and the spacebar(s).)
Anyone else tried to use such haptic walls on huge keyboards without gaps? Any experience with it?
Or are there key cap sets where the Arrow Down key cap either has a bar, dot or is a deep dish key?
Any other solutions to this? Artisans as Enter and cursors keys?
ISO Enter will help you or when in doubt use the numpad enter.
For the arrowkey, use your wall to find the middle of arrows.
Sculpted caps would help you if u can find matching ones.
If it’s possible to open the switches on your keyboard, put a heavy spring in the right control switch.
Funny coincidence seeing this topic posted. My daughter just received a 75% for Easter, and while working on her computer, I keep mismashing keys when I think i’m hitting return. Its frustrating and I didnt know what the hell was going on for the first couple of fat finger moments. I always use 60%, TKL, and full size boards so this is a totally new experience for me and I didnt realize how much I depended on the gap to the right of the return key to inform my fingers where there were.
I have also given some thought to this, and for me personally I believe .25u blockers or gaps (at least) are the way forward for logical groupings. A blocker, like on @yasintahir’s YAS-62, allows the finger to find the right (or left) arrow easily, much as a homing bump or dish lets one locate F or J.
Some layouts have a “cutout” for the nav cluster, with gaps between the arrow cluster and the bottom row/right shift and the numpad, adjusting the numpad zero to single-width and offsetting the arrows 0.25u, and sometimes downwards as well). The one I linked (image below) is my own stab at that.
Another way to let your fingers “do the walking” and find the arrow keys is to put them at the edge, but without filling in the gaps above the right (and optionally the left) arrow, instead putting blockers there. An example of that is the long-awaited and somewhat maligned Matias 60% board:
Yep, the YAS62 more and more becomes my favourite HHKB-layout derivative. Might pass the Tokyo66 at some point, which still has the above mentioned 65% issue wrt. the Enter key for me.
Want!
Urgs! I really dislike sub-1u keys. And more-than-1u-height bottom row keys! But yeah, that would help, too.
I really like the idea of a different material and hence a haptic difference! Before I just considered these steel keys something gamers want for their gamer keyboard to look more martial. Now I consider these something to buy to have an actual use.
Actually, they even look like being deep dish. Might be just the shiny surface, though.
I remember seeing a post somewhere on deskthority or geekhack I think a long time ago where someone was using a teeny tiny dab of superglue and a tiny ball bearing to almost make a homing key on keys they wanted to be able to find by touch, maybe something like that could work on one of the arrow keys?
Though they’re a different profile (and not deep dish or similar to the black TEX ADA caps, but rather OEM profile), they serve their purpose well; both the change in surface material (they are smooth and cold to the touch) and profile promote @XTaran’s idea of a “haptic wall”.
No you’re not seeing double; the first Slimer had a problem where the hands were too low and pressed adjacent keys, so the maker was generous enough to fix the model, reprint it and paint it, and send it free of charge.
Well, Slimer’s gonna have his fans, certainly. Cakey boy
To circle back to the original topic, I like to use a dot of UV Epoxy or figure something else out to make the down arrow into a homing key if there’s no gap or blocker. I’m fond of having the arrows in the extreme lower-right corner if the layout supports it, but I guess that’s not helpful when this is a specific issue for 96% boards and their near cousins. Enter, I’m less concerned about. It should always be large enough and consistently placed, so I don’t think a physical barrier is necessary for proper touch typing, and even just for dancing around or navigation/selection, it’ll always be large and just above “Up” on this type of layout.
Well, yes and no. Noticed your reply via e-mail notification.
Things slowed down with regards to keyboards for me—except maybe my typing speed. I’m kinda happy with the keyboards I use as daily drivers: a Rama U80 with Kailh Box Jades and MT3 profile keycaps at home (albeit the Rama drama—still waiting for my third U80 ) and a black Tex Shura with Cherry MX Silent Red switches (see below) at work, which replaced an aging Tex Yoda II.
Also the pandemic made me skip most meetups (a local indoor one last year and before that just outdoor ones at hacker camps) and the amount of keyboards I built in the past feels also rather low albeit it actually weren’t that few:
A Cyberpunk 2077/Araska themed Kbdfans D45 which arrived last October, but I only found appropriate keycaps a few months ago:
Bought a Kiser Monorail (V4N4G0N compatible) in March this year second hand on the Fediverse. Was totally happy about the offer as I missed the V4N4G0N groupbuy back then. It just cried for GMK Laser to get a cyberdeck-ish appearance:
(Figured I shouldn’t talk about new keyboards without posting pictures, even if it might be off-topic in this thread. But at least two of the pictures are kinda on-topic as the keyboards have haptically separated cursor blocks. )
And there’s currently only one keyboard I’m waiting for: The PolyKbd with tiny screens in each key. And I still have at least half a dozen unbuilt kits at home, including e.g. a Zlant XL, i.e. a 5-row Zlant.
For me the n+1 rule feels currently more present with bicycles, albeit nothing like all the shiny road bikes seen in the Fun Between your Legs! (Cycling Thread) thread: I recently bought a Skatebike (think unicycle with a skateboard truck in front) of unknown make and a Strida Mk1 folding bicycle, both at least 30 years old. Might revive that thread with posting some pictures of them there.
Indeed, love that Ghostbusters theme despite not all keycaps fit perfectly. (I think the left Control is too narrow.) Those industrial style keycaps (spacebar and cursor keys) work very well with the Ghostbuster artisan.
I really enjoy these necro threads from before my time in this hobby and on this site.
I run into similar issues with 65% layouts with a single column to the right of the enter key. I think my favorite layout is this one, with mod tap on the right shift to double as the question mark key on tap and shift on hold (the one marked “?” here is actually “delete”):