Please bear in mind that user manual’s intended audience is regular users, and not programmers - flow charts and pseudo-code is probably not useful for the majority of users, and it increases the maintenance burden of the manual. I’d recommend trying to pick key points (eg from the recent discussion, “the good interval will always be at least one greater than hard”), rather than trying to cover everything the code does - interested parties can read the code for that.
Yep, I agree. I was mainly hoping for something that explained the fully expanded equation showing the “normal” calculation of the intervals (ignoring all the if/else caveats). As an end user I was hoping for some more transparency with regard to that. Anyway, I’ll keep this in mind when making any proposed change.
This topic was automatically closed after 11 days. New replies are no longer allowed.