Strange issues with macros
During an attempt to recreate programmer Dvorak layout on V3 with version 2.8 firmware I've run into some strange issues. I've remapped Fn to right shift to get the closest possible to a normal typing experience, and I am attempting to do this all in layer 1 to minimize frustration and mode-switching. I am working with the Dvorak dipswitch on because without it I don't think I would have nearly enough macros in one layer.
The keys that are 1, 2, and 3 in QWERTY/normal Dvorak seem to be unavailable for macros. The keyboard does not respond at all when I hit them while in programming mode, either for a "raw" macro or an Fn + key macro.
Meanwhile, on the other side of the number row, the 8 and 9 keys from normal Dvorak share a non-Fn macro. Whether I assign ), +, or anything else to them, and regardless of which one I assign it to, they both receive the same macro. Simultaneously, the 9 key seems to "send" its Fn macro to the 0 key. When I assign Fn + 4 to the 9 key (as it is on Programmer), it instead assigns Fn + 4 to the 0 key. I can instead assign an Fn macro to the 0 key directly and doing it that way works as one would expect.
Interestingly, these issues are quite different than they were on version 2.4 firmware. They have both changed type and key location. I do think these are relatively livable issues, but for now, I am going to factory reset the keyboard and use normal Dvorak while ignoring the keycaps I bought. It would be nice if these issues could be addressed in the next firmware patch, or if anyone has suggestions.
-
I'm having very similar issues on 2.8, almost to the point that macros are unusable. I can assign a macro to one key combo, then assign another macro to a different key combo, and for some reason both combos now perform the later combo. I've had this with up to four different macros, where they're all linked together or something. Oddly enough, after a factory reset, it will work normally again, for the most part. I'm also seeing an issue where I define a macro for a key or key combination, it appears to program in correctly (the LEDs flash appropriately after I hit PGM to save at the end), but then it just doesn't do anything.
It seems like I have better luck if I can create my macros one by one without modifying anything - once I try to make a modification to anything, everything just goes to hell. I've even had (twice) a situation where the keyboard appeared to "crash" - it was stuck in programming mode (Fn + PGM), but nothing I could do would get it out of it. Fn+PGM did nothing, either PGM or Fn by themselves did nothing, Fn+layer key did nothing, etc.
Unless I have some kind of hardware problem that doesn't present itself when just using the keyboard without macros or something, I'd say that this firmware is embarrassingly poor. Maybe I'm just missing something, but I spent several hours today just trying to define a half dozen simple macros to enter like 20-character strings of text. I kept having to start over, or to factory reset the board, because it would start having issues, and then they would just get worse and worse.
Please sign in to leave a comment.
Comments
1 comment