shift kills caps lock after shift-modified key is typed out

[d3aWrVVmn]

using EPKL v1.4.1

for example:
expected: CAPS "LOCK"
actual: CAPS "lock"

if no shift-modified key is typed out, i.e. i'm only pressing shift without typing anything, the caps lock stays on
i don't know if this is expected behaviour. if it is, i'm sorry; can it be disabled? i'm also sorry for using the issues page for tech support

[DreymaR]

The issues page is the right place for this, don't worry! Also, sorry for the late reply but I've been on vacation.

I cannot reproduce your problem.

Activating CapsLock (using Extend+Esc), then hitting Shift for the quotes, I get:
CAPS "LOCK"
exactly as it ought to be.

I reproduced this using both an eD (state mapped) and eD2VK (VK) layout.

If you keep the Shift key repressed while typing "lock, it will come out in minuscles, as expected.

[d3aWrVVmn]

ah, that so...
i tested the previous versions, and v1.3.1 the caps lock stays on. v1.4.0 has shift killing the caps lock just like v1.4.1
also, i forgot, i'm sorry: i'm running windows 10 19044.3208

[DreymaR]

If you suspend EPKL and try it, it should be the same behavior: Caps+Shift decapitalizes letters again.

It also depends on your mappings if you use a state mapped layout such as the eD ones. The CapsBehavior or "CStat" number governs how each key behaves when using CapsLock; it's a bit map of the states that display this behavior.

[d3aWrVVmn]

ah yeah! i'm sorry again: i was using colemak(vk) (the default one). switching to colemak(ed) does stop shift from killing the capslock