kiibohd / kll-spec Goto Github PK

Just what it says - visiting the url (https://www.overleaf.com/read/zzqbdwqjfwwf), the latex source is visible on the left pane, but the right pane reports a compile error.

There is no preview for the latest version of this project. The authors of the project have to fix any compile errors before the preview will be available here.

Same for the 0.4 link. However, 0.5c seems to compile fine.

Hey there!

Maybe it's just my poor implementation of KLL, but given by the current draft (0.5c) that an end frame can be used to trigger a result, and an animation can be dynamically controlled using triggers, I would imagine that the following syntax would work as expected to begin playing a different animation:

A[animation1]: A[animation2];

and the end frame of animation1 would trigger animation2.

I'm attempting to create a KLL file to hold my startup animation, and as far as I can tell both animations are properly defined, however here is how I have chosen to define them:

A[waxon] <= start, pfunc:interp, loops:3, replace:basic;
A[fadein] <= pfunc:interp;

I've attempted to set up the trigger : result pair as follows:

A[waxon]: A[fadein];

While the first animation (A[waxon]) plays properly upon the keyboard powering on, it does not trigger the playing of A[fadein], following the syntax proposed in the the latest KLL draft. Am I just daft?

Thanks for the help!

I'm trying to create a sequence that quickly renders Unicode characters. Since the KLL/USB spec doesn't allow Unicode, I've set up sequences for the ones I use most often.

For instance I've assigned Layer 3 > Key C to the sequence 0169. When I hold fn3+Alt and hit C it gives me ©.

#Configurator code:
U"C" : U"P0" , U"P1" , U"P6" , U"P9";  # Copyright.

However, certain alt codes require repeated characters, which do not seem to register. The horizontal ellipsis, for instance:

#Configurator code:
U"X" : U"P0" , U"P1" , U"P3" , U"P3";  # Horizontal Ellipsis
U"X" : U"P0" , U"P1" , U"P3" , U[91];  # Tried faking it by using a different format key code.

When this sequence runs, it should output 0133. Instead, it outputs 013.

These alt codes specifically require numpad keys, so a normal number string doesn't work.

#Configurator code:
U"X" : '0133';

I tested it with sequences that contained non-sequentially-repeated characters and it ran just fine.

U"A" : U"A", U"B", U"A"; output "aba" as expected.

Spec describes syntax for specifying Consumer Control Code results having "CON" prefix. This is the case for 0.3d and 0.5c versions.

Examples in KLL repo use "CONS". KLL compiler errors out on "CON" with message like this:

should have reached <EOF>: 28,12-28,32: String '"VolumeUp"

I don't know if this is the right place for this issue.
Anyway.
It seems that Macro in current KLL spec treat the modifier key as the plain keys .

1. If I pressed one modifier key, let's say RShift, then trigger a macro with a LShift in it's result.
2. Do not release the RShift key.
3. at the end of macro it will send a LShift release event to host, which cause the "shift" flag changed on host. But the 'RShift' is still pressed.

The ideal way should be before macro execute, check the current modifier key status, if it's result contains a modifier key and that key has already active, than ignore the modifier key in result. let's user to release that modifier key manually.
I think this way is better.