Replies: 1 comment 2 replies
-
Hey @allgreed, I haven't tried crontrolling urgency like this before. Where did you get to? Did you write a hook? |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi, I have this bit set up:
and it works splendidly 99.99% of the time, because if something is blocking something with high urgency then it should have at least that urgency!
And then laundry happened. Basically laundry has some calculated urgency which I'm fine with. However there's a dependent task "hang laundry to dry" which needs to be done after laundry and for domain reasons (if I don't take it out of the washing machine it gets ugly) it warrants an urgency boost. However it should only be booster after the laundry is done. I've initially achieved this with just slapping
+next
on the drying task, however with the urgency inheritance it bumps the whole process to the top and that's not exactly what I want.While writing this I've came to the realization that hooks might be the perfect use case for this -> namely add
+next
to the drying task once the laundry is completed, but no sooner. Is there a better way of approaching this issue?Beta Was this translation helpful? Give feedback.
All reactions