deskthority

And here i was thinking i wouldnt order any more caps...

It should save event if you haven't assigned all keys, in theory I'm off to bed now but if you still have problems i can check tomorrow.

The first problem will need some testing, haven't tried on Linux yet but i plan to do so soon
I have pushed a fix for the other problem to github just now, i think it should work!

Yep!
And it can currently only display rectangular shapes, so an ISO enter key will not be possible...

You can, in theory, increase the resolution by making the layout array bigger. But there is also a limit in screen resolution so unless you have a very big terminal window you probably won't be able to see the difference anyway...
For the ergodox layout each 1U is represented by 2x2 array entries ...

uberben: Thanks! Let me know if you need any assistance with adding a layout for the Kinesis (has not been done).

Making some progress on action editing, it mostly works now but there are still some UX things to do, and macros are missing.
Here's the current state:

Well spotted, it's merged!

scottc wrote:I found a bug!

Oh my, a bug? Really?
To be honest i'm glad it worked at all outside my own computer

You could also consider parsing the JSON output from keyboard-layout-editor.com as input. That would be nice for quickly prototyping layouts. Maybe you'll see a pull request from me soon... Just thinking aloud here, don't mind me... :D

Cool, will take a look at that site :)

Soarer's uses NVRAM ...

I've been meaning to take a look at Soarers firmware but i haven't had the chance so far, it's something i'd like to add support for. But first i'll make it possible and easy to make use of all the functionality in TMK's action functions :)

I did consider a Cocoa app at first but i really like to ...

I can add a layout for it when i get a chance, or you can do one and send to me :)
Here's how it's done: https://github.com/CJNE/vikeys/blob/master/lib/keyboards.js
Every number represents a key, null means blank space. The "resolution" needed depends on how many different key sizes you
have, and ...

Great, thanks! What keyboard layout would you like to have?

Right now you can't edit actions, that's what i'm working on at the moment.
It will be possible to construct any kind of action, such as macros and all types of layer functionality. If you look at the screenshot you can see the list of actions that were parsed from the .h file, the plan is to make ...

I've been playing with a curses based terminal tool to edit keymap.h files in the tmk firmware and have reached a stage where it's almost useable :).
I wanted to see if anyone else would be interested in such a tool and/or have ideas for functionality?

Consider it an early alpha. I have only ...

Yeah, i'll give "anti-ergo" a try before i decide, it could be the ideal combo for me.

Ah, i thought it was mods as in modification

The mods on my Ergodox are already brown, so maybe all brown is the way to go then...
I have all blue on my other dox and i much prefer the feel on that one but i don't want the click sound.

I haven't tried lubing, not sure i want to go down that path, unless it's sufficient to do it just once?
But as i understand it you usually just lube the sliders and the spring ends?
I think the friction comes from the tactile bump mechanism.

I'm able to get the caps lock to work now, but still can't figure out the LEDs. Those aren't too big of a deal for me though, as I rarely use caps lock or scroll lock. Thanks for the help :)
Glad that you got some of it working at least :) I don't have a phantom so it's hard to debug.
It could be ...

What is ergo clear with linear mods exactly?
I've changed springs to 62g korean from Originative and i don't like them very much to be honest, they feel very "rough"*, it's even more noticeable with the lighter spring.

Is it possible to reduce the friction somehow?

Try to add this to config.h As for the LED brightness, have a look in the Makefile you use and make sure that SLEEP_LED_ENABLE is set to no or commented out (add a # to the beginning of the line)

No, it definitely did trigger the jump to bootloader function, it shut down USB but what happened next i don't know. It was supposed to jump to the bootloader but perhaps the address was not set right?
Assuming it is a Teensy 2.0, try to add:

#define BOOTLOADER_SIZE 512

to config.h, compile and ...

Haven't tried this in Windows so i can't tell if it's normal or not... If nothing helps try to unplug and plug in then hit the hardware program button on the teensy.

Ah, you are missing some includes, add to the list of includes at the top keymap.c and try to compile again.

Excellent news, thanks bchociej!

Great :) Lufa and pjrc are two different USB stacks, they provide the same basic functionality. I think the tmk firmware is moving focus to Lufa nowadays. It shouldn't matter which one you choose.

You need to provide more detail in order to get help with the compile error. It might be that you have ...

The 1 in that code is the layer number to switch to.
FN0 ... FNn are special functions that you can assign to keys and the numbers are just their position in the fn_actions array.


static const uint16_t PROGMEM fn_actions[] = {
ACTION_LAYER_MOMENTARY(1), //This is FN0
ACTION_FUNCTION(TEENSY_KEY ...

Yes there is! If you use the default keymap_ansi.h file for your keymap, change this part:


static const uint16_t PROGMEM fn_actions[] = {
[0] = ACTION_LAYER_MOMENTARY(1)
};

to look like this:

enum function_id {
TEENSY_KEY
};
void action_function(keyrecord_t *event, uint8_t id, uint8_t opt ...

To start things off, here are the things you need to install and instructions for how to build:
https://github.com/tmk/tmk_keyboard/blob/master/doc/build.md

Then read here for phantom specifics:
https://github.com/tmk/tmk_keyboard/tree/master/keyboard/phantom

You should do all edits and ...

CJNE, that tool looks fantastic. I was thinking of writing something similar myself, but probably more on the level of $SOME_MARKUP_LANG --> outputs layout.h. Do I see that it's written in Node? :D

Thanks :)
Yeah it's Node alright, trying to keep up with the trends 8-)
And it would be trivial ...

Sounds like the Poker have more EEPROM than a teensy then :) Don't know much about the Poker controller, is it even possible to flash it with a custom firmware?

I'm not quite sure what you had in mind here, to get all manufacturers to agree on a standard protocol?
That would be nice, but the ...