settimer, timer1, 1000
gosub, timer1
timer1:
if a_raider_is_detected()
{ fire_a_warning_shot()
notify_the_user()
settimer, timer1, off
settimer, timer2, 1000
}return
timer2:
if not a_raider_is_detected()
{ settimer, timer1, on
settimer, timer2, off
}return
while internet_browser.active, 10000
when (flash_player.active and site="YouTube"), 2000
{ adjust_settings_macro()
cooldown when not (flash_player.active and site="YouTube")
}
settimer, timer0, 10000
gosub, timer0
timer0:
if internet_browser.active()
{ settimer, timer1, 2000 ; on
gosub, timer1
settimer, timer0, off
settimer, timer00, 10000
}return
timer00:
if not internet_browser.active()
{ settimer, timer1, off ; off
settimer, timer0, on
settimer, timer00, off
}return
timer1:
if (flash_player.active and site="YouTube")
{ adjust_settings_macro() ; actions
settimer, timer1, off
settimer, timer2, 2000
}return
timer2:
if not (flash_player.active and site="YouTube")
{ settimer, timer1, on
settimer, timer2, off
}return
.
Glad to share
Is it to be implemented?
perhaps Cooldown should be simpler, like making it function without a need for parameters? edit: on second thought, I think cooldown should be implicit.
It could be implemented.
I also think that a syntax that handles events (or can be used to create value polling more easily).
Nonetheless the design you provided is probably very clunky and limited.
The second parameter seems very strange and we might be better off putting it into a function which could provide a simple polling mechanism.
There are also a lot of things that are not clear from this example.