It is perfectly preferable. Especially since it does not restrict itself to one type of multitasking framework. I like that.tve wrote: ↑Sat Jan 04, 2020 1:32 amyou have been using a model where the driver exports an `ameasure` method that calls async delay functions inside. In my drivers I have instead provided a `start` method that starts the data acquisition and returns the expected time it will take and then a second `read` method that reads the result assuming it's ready and returns an error if it's not. The rationale for my design is that this model lets the caller decide which form of delay function to call. Is that not preferable?
What format and unit is it that your `start` method returns the desired delay? It would be good to coordinate things like that across drivers.