Carsten Haitzler
3051df7fee
if you add a job to do things like defer a calc till later in the loop (or if later in size calc - it'd be the next loop run after rendering) ... then del the previous job and add a new one. why? order of operation. if you add job a... because of event a, then add job b, because of event b ... if for whatever reason, event a happens again and you skip adding job a... job a will run before jbo b, even though the LAST event is later and that 2nd event a may relay on event b state/calculations. so always del then add to ensure then that job a happens ater b if this scenario happens. it just leads to fewer surprises and weird issues. |
||
|---|---|---|
| .. | ||
| bin | ||
| modules | ||
| protocol | ||
| tests | ||
| Makefile.mk | ||