yurikhan / teck Goto Github PK

Hope can have the shifted keys in the layout designer, like ( ) &, so we can press one key to send the parentheses to the system.

Adding/Changing a non-alphanumeric character results in an empty key displayed.

Steps to reproduce:

1. Select "1!"
2. Replace "1!" with "1_"
3. Press Enter

Expected behavior:
Key displays "1_".

Current behavior:
Key is blank/unlabeled

Hex file seems to be broken too.

The firmware contains code that looks like a macro engine, which seems to be able to play back any sequence of HID reports with specified delays in between.

Ability to configure the macros and bindings would nicely solve any feature requests that are not implementable in a way that works everywhere and for everyone.

I would like to load my current layout into the configurator to modify, rather than reproduce the layout from the defaults. I have the hex file, based on TrulyErgonomic's v4 firmare. Can I do this by adding the hex file to the repository, then selecting it from the configurator? The layout is for TEK 209 and has essentially the defaults for the main layer and Dvorak for the secondary.

Hi,
I'm using the firmware as generated by the version on the TrulyErgonomic site on a couple of 209 keyboards. I (and others) have found that the Vol+/Vol- keys behave erratically. The operating system apparently keeps receiving the keycode, so the volume maxes out or goes to zero. I haven't yet verified if this is the case on Windows. It happens erratically too, sometimes it will work, other times it goes to the end immediately, and it also will do it strangely sometimes.

Dan

Would be awesome to map alt codes directly. And/or Unicodes.

In my personalised layout¹ i moved the media keys (prev / play / next) one key to the left and added a stop key on f9, all on the Fn layer.

While all other changes to the layout work after flashing, Fn + F6/7/8/9 still send the standard key codes.

¹ http://yurivkhan.github.io/teck/#KTo7PD0+P0BBQkNERUhG394pNR4fICEi4yMkJSYnLS4rNBQaCBUXihwYDBITLzA5BBYHCQoqCw0ODzMy4B0bBhkFKBEQNjc45OPiSktOTeFkLFBSUU/m5yk6Ozw9Pj9AQUJDREVIRt/eKTUeHyAhIuMjJCUmJy0uKwYTFwkOD0wFBBYKGR0wOQcLMxIMKhg4HAgbMuE0FA4aESgNEDY3LeXg4kpLTk0sZCxQUlFP5uQBAAwAsgEADAIjAQAMAYoBAAwCIQEADAGUAQAMAZIBAAwAtgEADADNAQAMALUBAAwAtwEADADiAQAMAOoBAAwA6QEADAC4AAAAAAAAAAAAAEcAAAAAAAAAAAAAAAAAAEkAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAApOjs8PT4/QEFCQ0RFTDnf3mQ1Hh8gISLjIyQlJictLjE4FBoIFReKHBgMEhMvMOEEFgcJCisLDQ4PM+XjHRsGGQUqERA2NzTn4OJKS05NZSgsUFJRT+bkAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABnVFVWAAAAAAAAAAAAAABfYGFXAAAAAAAAAAAAAFxdXmIAAAAAAAAAAABZWltjAAAAAAAAAABYAAAAAAAAAJMBAAwCIwEADAGKAQAMAiEBAAwBlAEADAGSAQAMAYMBAAwAtgEADADNAQAMALUBAAwA4gEADADqAQAMAOkBAAwAuEkARgAAAAAAAK1HrgAAAAAAAAAAAAAAAACLAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

It is reported that some users experience excess key bounce, i.e. pressing a key once produces more than one character.

The problem only affects some users, some keyboards and some keys.

If you are affected, please leave a comment here.

Additionally, I need at least one testing volunteer who is:

• able to reproduce the problem reliably, and
• comfortable with flashing experimental firmware and rolling back to a previous version.