kiibohd/configurator

Custom Layout upload failure

Opened this issue · 7 comments

Upload custom layout for Infinity Ergodox. After flashing the new firmware, layout appears to be bundled default. Double checked downloaded firmware JSON, confirms the custom layout was not uploaded for compilation. Instead, original default layout was compiled and downloaded for flash.

+1 same issue

A little different issue, but the title is fitting. On Kira.

I've found out that if you clear any of the preassigned commands in layer 1 or 2, it gives the Compilation Failed error.
If you add command to any unassigned key on those two layers (1 and 2), it spits out the same error.

Here is the default layout, which compiles no problem (I can change base layer without issues):
Screenshot 2019-04-15 at 16 04 59

And here I cleared "M" key on layer 1 (got rid of "Menu"):
Screenshot 2019-04-15 at 16 02 23

Here I reset to default layout and added the "Play" function to "N" key on layer 1:
Screenshot 2019-04-15 at 16 03 51

Additionally, I can't view logs when this error occurs (the Internet connection is stable.

The issue persists on both Windows and MacOS. This is really sad, because I'd really like to customise the default layout (layers especially).

Using a Whitefox on Mac, I find the following:

  • If I try to make more than one change at a time, it always fails to compile. (For example, if I load a working map, then make more than one change and try to compile, it will fail.)

  • If I try to clear an assignment on Layer 1, it fails to compile. I can reassign a key on layer 1, but not clear it.

  • Whenever it fails to compile, the "Show log" button on the "Compilation failed" banner does nothing.

I'm having the same issue as well. White fox keyboard on arch linux, tried both the appimage and the AUR client. Sometimes compliation works, sometimes it doesn't.

@mchaput I'm trying to flash my old infinity 60 and had to download this and your comment helped me understand wtf was going wrong. It takes like 10 seconds to compile a change and I can only change 1 button at a time (currently trying on layer 1) to get it to compile. I'm trying to change my arrow keys from WASD to ESDF, which it already is on my board, but I'm trying to change something else and get the layout to my current layout and then update my desired changes.

If I remove UP from W and LEFT from A, it freaks out. Meaning the same issue mchaput said above: removing an assignment on a layer breaks compilation but reassigning it doesn't.

How is this still a bug? If this happens to other keyboards, how do people even make their own function layers if this prevents any compilation for anything other than a default layout? PLEASE get this working as I don't have the tic mark from my original flashing and I can't flash my current layout back onto my board with this in order to add the tic mark under my ESC key.

Whenever it fails to compile, the "show log" button on the compilation failed banner does nothing when clicked.

This on a Win 10 machine.

After playing with it, it looks like I can add something to layer 1 where there wasn't a key bind previously and it compiles fine, but if that same key bind is removed, it freaks out. It sounds like something that gets added into the JSON isn't being removed when removing a key bind, like a colon or comma or something.

Sounds like a simple enough bug to fix.

Oh great, even after compiling my janky layout, it still decided to ignore some of my key binds. My caps lock I have assigned to fn1 and it decided to ignore that and leave it caps lock. I put caps lock on layer 1 and that key bind is correct. So it ignored my base layer modification but applied the layer 1 change. Mine is also the LED version of the keyboard and then flashing made all the LEDs shut off and not usable at all, which is really weird...

Oh, and somehow my bottom left three buttons changed even though the layout showed them to be BY DEFAULT LCTRL, LGUI, and LALT. It's somehow now flipped LGUI and LALT. How is this configurator so screwed up???

HOW TO FIX: I went to this url (https://configurator.input.club/lts/?layout=MD1.1-Alphabet) and made my own layout (which the layout doesn't have a standalone tic keybind, which is strange, and what I needed, so I had to leave it under ESC) and downloaded it. I extracted the files within and used the configurator to flash an image and then changed the flash .bin to the one I downloaded from the online configurator and everything worked again. I got my LEDs back, my LGUI and LALT are back where they should be.