With layer set as:

Then, even 99.98% CPU will not light up F12
CPU% measurement is done using ProcessHacker (https://github.com/processhacker/processhacker/)
I used to have Maximum Value: 100 before I set it to 95 (when this picture was taken)
Expected behavior:
If gradient is done by # of keys, then CPU >$((MaxCPU - MaxCPU/keys))% would light up F12 (i.e. 92.307% in my Max CPU 100% case)
If gradient is done by "actual keyboard distance", then CPU >$((MaxCPU - MaxCPU/dst_unit))% (idk how/if you "somehow" measure that)
Actual behavior:
Only CPU 100% would trigger that (and could be not the case, I tried 99,5% and barely got it).
How often does this problem occur?
This problem occurs... (Fill in here) Constantly
Please describe the steps to reproduce this issue:
The issue can be reproduced by doing following steps:
What is the version of Aurora you are experiencing this issue with?
My version is... 0.6.4b-b604
Does the previous version of Aurora have this issue?
The previous version, (Fill in the version here), did/did not have this issue. Haven't tried / I guess yes
Please include any logs, screenshots, or files that are related to this issue:
With layer set as:

Then, even 99.98% CPU will not light up F12
CPU%measurement is done using ProcessHacker (https://github.com/processhacker/processhacker/)I used to have
Maximum Value: 100before I set it to95(when this picture was taken)Expected behavior:
If gradient is done by # of keys, then
CPU >$((MaxCPU - MaxCPU/keys))%would light upF12(i.e.92.307%in myMax CPU 100%case)If gradient is done by "actual keyboard distance", then
CPU >$((MaxCPU - MaxCPU/dst_unit))%(idk how/if you "somehow" measure that)Actual behavior:
Only
CPU 100%would trigger that (and could be not the case, I tried 99,5% and barely got it).How often does this problem occur?
This problem occurs... (Fill in here)ConstantlyPlease describe the steps to reproduce this issue:
The issue can be reproduced by doing following steps:
What is the version of Aurora you are experiencing this issue with?
My version is...
0.6.4b-b604Does the previous version of Aurora have this issue?
The previous version, (Fill in the version here), did/did not have this issue.Haven't tried / I guess yesPlease include any logs, screenshots, or files that are related to this issue: