Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Loop for schedule
#15
1. Ok, if then guess it's a continous loop, was afraid to try that because of the potentiel bootleneck it
could create in QM, and being too much ram/cpu consumer and interfere with other function. Good to know.

2. I once used init2 to launch at QM start. bad deal?

3. Can mNow be different for individual schedules, or the same for all? test some schedule on second basis, others minute, others hours?


Messages In This Thread

Forum Jump:


Users browsing this thread: 3 Guest(s)