In this case, having numbers on the shifted top row might be an improvement (though one still has to press a shift for that, so we’re not much better off…). But as soon as you inline numbers with other stuff, from different layers, they aren’t as convenient anymore. So far, my experience is that a numpad is great if you want to enter a continous sequence of numbers, or perhaps number + some symbols that are accessible on the same layer. Even if I chord AUX with 8 and Shift -, and the sequence becomes uint, AUX+8 AUX+Shift _, t, I still have to time the AUX release properly. For example, typing uint8_t with the layout I have now is… awkward: uint, AUX 8, Shift -, t is not the most convenient thing. There are a few things that are harder with such a setup. ![]() maybe I will revisit unshifted symbols now that I can freely adjust my numpad layer. The awkward colon was annoying and frustrating. The symbols were all messed up in different places, and I ended up with something like this.The big issue I had when using unshifted symbols and numpad on a conventional keyboard was inputting times, which is the majority of my number input. However, I went and installed Programmer Dvorak Keyboard Layout. If I pressed Win-Space I toggled between the two keyboard layouts. So I added 'United States Dvorak' in Windows and it worked fine. Recently I've been learning Dvorak as well. That change made typing symbols impossible with the altered keyboard. 3 Normally I type using a Swedish QWERTY layout. I reordered my number keys based on the cursed row (As normal Dvorak typists call the numbers in the programmer's Dvorak). The symbol + number key association is also different from qwerty. I use a modified Dvorak optimized for programming, with the most important modifications being the placement of l/L, s/S, and /: (the last is particularly important for any programming language that uses lots of semicolons or colons, which is most of them). The symbols take the number's place, and the numbers typed using shift. Programmer's Dvorak reorders the numbers keys differently. As a result, H and U keycaps ended up in different positions in my setup. So I had to leave those untouched in their qwerty place. To my bad luck, the F and J keycaps were a different design than the rest of the keys. I want the correct key in place to look when I need a reference. ![]() But this was one of the reasons my gradual switch from qwerty failed. For touch typing you don't really need to do this, changing the OS settings is enough. So in the attempt, I rearranged the keys on my amazon basics keyboard to match the programmer's Dvorak Layout. I would like to test how far I can actually go without getting one of those. But they are really expensive and I don't easily act on the impulse to buy anything ( Learned it from Gandhi). ![]() The obvious choice would be to buy a custom programmable keyboard. Hereafter I will mention it as just Dvorak. The symbols are not easy to type in the standard layout. Writing code is a major part of my job, so I can't use the standard Dvorak. It was a painful and equally enjoyable experience. An enUS Programmer Dvorak keyboard layout for Android with AltGr support. After trying a gradual switch for 3 months, I went cold turkey this July. I committed to converting myself into a Dvorak typist in 2020.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |