![]() I'm not getting rid of that and it will get more use, but trying to enter long sequences of numbers on a 40% is a bit of a pain. I have moved up in the world from the 40% I was daily driving with before. I'm typing this comment on a carbon black Q2 and so far I'm quite enjoying it. I have had trouble finding a keycap set I like for the 75%, but each time, i may have given up too easily. Another friend needs the number pad and will only look at full size boards. I have a friend who swears by 65%, they don't need any of those things. For me, I like the 75% boards, I want my function row, number row, and arrow keys. Note that size is *really* a personal preference. (My wife dislikes noise, and I've come to prefer the feel of them.) In some of the reviews, they talk about the stabilizers, but these reviews seem a little old, as the stabilizers in the one I got aren't rattling at all. It has a knob which I ignore, and I chose silent red Gateron switches. It's a 75% which is my perfect size, but I don't really like the keycaps I got for it, Aura pudding back. I really like the (possibly overpriced) Glorious Pro. The only thing i'd say is wait a week before deciding, because something more suited to your taste always comes along. There are several keyboard channels on youtube, I suspect how good they are depends upon one's personal taste. They also have a youtube channel, which is sometimes helpful. has a lot of good articles on keyboards. I haven't yet seen any proprietary keyboard software that was anything but wretched. I've never used that software, so maybe I'm opining from a position of ignorance here, but I find it hard to imagine it being anything other than wretched. But if you're used to prim and proper peripheral software (such as Razer Synapse). It displays what the key is programmed to (of course), but somehow it doesn't display "on-screen legends" which are somehow something different that you would like to see? And it's also somehow a problem that you have to "look down" at the keyboard in front of you that you are actually programming? I really don't know what you're asking for here, or how you think it ought to work differently.Īnd then. Instead, VIA displays what the key is programmed to, so I often had to look down to figure out which key I was programming. There are no on-screen legends for the function layers. (Also, this sentence no verb!) I think it's complicated by the strange way this board supports Mac and Windows, where most people would simply use VIA to set their board up for one or the other, as desired. I've been trying to parse this, and it's kinda dense. I mean, I've read that paragraph a few times now.įor instance, when changing from from layer 0 or 1 in the app (the default Mac and Windows key mappings) to layers 2, 3, or 4, which are for use when pressing Fn1 (Mac), Fn1 (Windows), and Fn2 (Windows), respectively. I don't understand the complaint about VIA's operation. Still, it be a simple matter of the keyboard producer getting their product into the VIA database. A better solution would be to store that data on the keyboard itself, which is how VIAL works, and I hope that this will grow in popularity. If it's not found in the database, for example if the keyboard is too new, then you have to load it manually. As I understand, VIA normally looks up the keyboard online and downloads that file from a database. I have several VIA-compatible keyboards, and one of them does make me jump through that hoop, and it's irritating. I understand that it's a nuisance having to manually load the JSON layout file. In fact, compatibility with VIA (or VIAL) has become table stakes for me now. It's free, it's multi-platform, it's powerful, versatile, and it's pretty much foolproof to operate. Why you raggin on VIA? VIA is the holy grail of keyboard remapping applications.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |