V3 / CODE V3 Comprehensive User Guide (Firmware 1.20+)




  • Avatar
    Mike W.

    I just read the whole manual.  Just to confirm a few points, could you please answer/confirm the following?

    1. If a remapping is done (say, Caps Lock to Ctrl), that will apply only to that particular layer (right?)—but

    1b. if a special key is moved (say, moving the Pgm key functionality to where Caps Lock is), that will apply to all layers.  Right?

    2. If some remapping and/or macros are created for layer 1 (with switch 6 on and switch 5 off), then both switches 5 and 6 are set to off thereby disabling virtual layers functionality—any remappings AND any macros entered on layer 1 will still be available, right?  (I recognize there may be a different answer for remappings vs. for macros.)

    3. Same question as 2 but for the switch-5-on-switch-6-on case of the "basic setup."  Does "basic setup" mean remappings don't apply?  Or is it possible to program in some remappings (like Caps Lock to Ctrl) and then have them available in "basic mode"?  What about macros?

    4. Am I understanding right that accidentally hitting the ADJACENT keys for Pgm and Fn at the same time is enough to enter programming mode?  (If I have switch 5 off and switch 6 on?)

    4b. If I move the Pgm key to e.g. "PrtSc" is there any way to access the normal "PrtSc" functionality?  (It seems not from my reading of the manual.)

    4c. Assuming the answer to 4b is "no," this seems like quite a flaw.  I would like to be able to program periodically without messing with DIP switches, but I definitely don't want to *accidentally* enter programming mode.  Is there any suggested simple workaround, or have I misunderstood something?

    Comment actions Permalink
  • Avatar

    Mike W. Hello 👾 ! 

    1. Yes, remaps only apply to that specific layer

    1b. Yes, the function key movements will apply to all layers 

    2. Yes, since layer 1 is default your remaps will still be applied, just remember when you turn these off, it also turns off the Fn key, so any macros you set to the Fn key will not be able to be triggered. 

    3. Basic setup just gives you the Fn key for media controls and backlight functions (no layer swap, no programming). You can't program anything with the basic setup because the PGM key is disabled.

    4. Yes, if you have your PGM key enabled it is possible to accidentally enter programming mode. 

    4b. No, if you move a function key (such as PGM in your example) it will obfuscate the key input below it. Example: If you move your PGM key to Scroll Lock you will no longer be able to access Scroll Lock through the keyboard (you can still use the onscreen keyboard, or other methods to press keys beyond your keyboard input). 

    4c. If you have a better suggestion to how you want this set up, please let me know. Unfortunately we cannot make a state where you have the ability to program your keyboard, but then also not have you potentially accidentally enter programming mode, the way we have set that up is on the dipswitch. 

    Right now it's pretty flexible with the dipswitches, the ability to move function keys, etc. You will have to weigh how often you're making/messing with macros with how often you are accidentally hitting keys. Depending on that ratio one may be more suitable for you. If you're making a lot or complex macros my recommendation is to leave the PGM key off with the dipswitch until you are ready to make changes/additions to your macros. 

    If you're prone to accidentally hitting keys and still want to be able to program on the fly, my suggestion is to move your PGM far away from your Fn key. For a 104-key there are redundant keys on the numpad, pause is also a good choice that is not used by a lot of programs, scroll lock is also a good choice, a lot of F row keys, even the num lock key (unless you toggle that on/off a lot). 

    Our firmware can do a lot and is quite extensive in terms of programming options, but if you are an extensive power user requiring more than it can provide I would suggest looking into a software solution. Unless you are moving from computer to computer or absolutely need the macros stored on the keyboard, the free software tools available are going to make writing and managing complex macros much easier, without limitation. Adding to that functions and abilities that a firmware setup could never allot (such as mouse control). Check out AutoHotKey on Windows and Karabiner if you're on a Mac. 

    Hopefully I have answered your questions successfully and the suggestions I have provided are helpful. Thank you. 

    Comment actions Permalink
  • Avatar
    Mike W.

    Definitely helpful, and thanks for the point about question 2.

    3. On question 3, I think my question was misunderstood.  I wasn't talking about the default state with both DIP switches (5 and 6) off but with media controls accessible.  I was talking about:

    > SW5 on, SW6 on – All special functions are disabled - Onboard media functions and lighting controls are disabled, virtual layers are disabled and programming is disabled. This is as “basic” of a keyboard setup as you can get.

    And, I know I can't program in the "basic" mode.  The intent of question 3 was: if I do some remappings in programming mode and *then* change the DIP switches to enter basic mode (with even the media controls disabled)—will the remappings I programmed earlier still apply to keys pressed in basic mode?  Just as a concrete example of this question, is it possible to have media controls disabled (switches 5 and 6 both on) but still have the Caps Lock key mapped to send "Esc"?

    4c. The "pause" key for Pgm would seem to be an obvious choice, except that it's already used for "mute" in the media controls (and even has its own label as such, on the CODE keyboard).  So if I used Pause for Pgm, then "Fn + Pause" would activate programming mode instead of mute.  (Undesirable.)

    Next choice would be ScrLk, which I think I will use.  However it seems from the above manual that that's already the key (Pgm + ScrLk) for reprogramming indicator lights, and it's not clear that there's any way to change that.

    I probably won't reprogram indicator lights very often, but still it would be nice to move Pgm to the ScrLk key, and be *able* to have Pgm + right Ctrl activate indicator light reprogramming.  In this ideal setup, I won't be able to access the normal ScrLk key functionality (I don't care), BUT the right Ctrl key will still work as normal (I use it a lot for e.g. Ctrl + arrows to switch "spaces" on a Mac), plus I'll be able to program indicator lights if I want, AND Fn+Pgm will be a lot harder to accidentally activate.  (Two adjacent keys are easy to accidentally press any number of ways.)

    Second best setup would be to move Pgm to ScrLk and have indicator programming inaccessible, which I'll do if there's no way to move the Pgm+ScrLk functionality for indicator light programming.  (That's a question by the way.)  :)

    Edit: Sorry for such a long comment!  It comes from trying not to be ambiguous.  :D

    Comment actions Permalink
  • Avatar

    Mike W.

    Ok no problem, 

    3. Yes! Your remappings/macros will still remain even if the Fn and PGM keys are turned off, even if the layer keys and media keys are turned off as well. 

    4. I just gave you some examples of something I would do under the circumstances of having all the caveats that you were detailing. Under normal circumstances I would either be programming often enough to leave the PGM key enabled, or I wouldn't be and then turn it off with the dipswitch to avoid accidentally programming. We wanted to leave the programming toggle on the dipswitch because even with a different location it's still possible to accidentally enter into it, the only way to avoid this is to put it on the dipswitch. 

    You could swap PGM and Scroll Lock if you'd like, that may be a solution for you. If you move PGM to scroll lock position only then you will no longer be able to press scroll lock. You'll have to move scroll lock to a different location before moving the PGM key if you want both scroll lock and PGM functions at the same time. 

    It seems like you want to have everything accessible, but then also not have PGM and Fn next to one another. I would remap the PGM key further away and swap that key with the previous PGM location. The only other way to have what you want and not move anything but also make it so you can't accidentally program anything is to use the dipswitch.

    I hope that answers your questions. Thank you. 

    Comment actions Permalink

Please sign in to leave a comment.