Exec|call|fork command not working?

General
1

After updating to the latest firmware, I have noticed that this command does not work anymore.

COMMAND = {exec|call|fork} MACRONAME

I use this command in my $onInit macro and it does not trigger upon boot.

2

Thanks for report!

Will definitely look into it, but I am afraid it will have to wait some time.

1 Like
3

@nacho Please open a firmware issue if this persists.

1 Like
4

Not necessary. It will get lost anyways.

1 Like
5

I have tested this with a 12.x dev branch and I can’t reproduce it, so please test when 12.x firmware finally comes out and then create a firmware ticket if it still doesn’t work

1 Like
6

@nacho I updated the firmware on my UHK60 to 11.2 about a week ago. I did not change anything in my macros and they still work fine. I do use some fork and call commands.

Are you absolutely confident the commands don’t work anymore? Can you put some setLedTxt around different code paths and see what really gets executed?

1 Like
7

I have updated to 11.2 today and it still does not trigger upon boot for some reason. Below is my $onInit

call hrmauto
set keystrokeDelay 10
set secondaryRole.defaultStrategy advanced
set secondaryRole.advanced.timeout 250 // default 350
set secondaryRole.advanced.timeoutAction secondary
set secondaryRole.advanced.triggerByRelease 1
set secondaryRole.advanced.safetyMargin +10 // default +50

I renamed the macro to hrmauto because I thought maybe the - was causing the error, but that didn’t fix it.
I originally had hrmauto at the end, and tried moving it to the beginning, but that didn’t fix it either.
The LEDs trigger fine like normally so I’m not sure why it’s not triggering upon boot.

8

How can you tell that “it doesn’t trigger”? What should hrmauto do that it does not? Can you throw in some setLedTxt 999 'YES' at the start of hrmauto and check whether the display shows YES for a moment when the keyboard starts?

2 Likes
9

OK, thanks. this seemed to resolve the issue. By adding the setLedTxt 999 'YES' to the start of the hrmauto script made the macro perform as expected upon $onInit for some reason. I’ll keep it this way for now since it’s working and report back if I encounter any other issues. This is my current hrmauto macro:

setLedTxt 999 'YES'
setVar hrm_active 1
setVar hrm_timer_active 0
setVar hrm_tick 0
setVar hrm_tick_delay 10
setVar hrm_tick_active 20 // default 30
setVar hrm_space 0
setVar hrm_reduced_safety 125 // default 80
setVar safetyMargin $secondaryRole.advanced.safetyMargin
overlayLayer base HRM mod
setLedTxt 666 '-+-'
if ($hrm_timer_active == 0) fork hrmtimer