You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current state of timeouts in this library is confusing. There are keywords for open-serial (inherited from LW) for very fine-grained setting of timeouts (in seconds). But those are completely ignored in favor of per operation timeouts, specified in milliseconds. We should probably choose one and get rid of the other. I kind of like LW's API better here, but it would need to be extended with some functions to adjust the timeout after the serial port is opened.
Additionally, the LW API lets you control per operation if an error is signaled or some default value is returned on timeout. I think this particular behavior is nice.
The text was updated successfully, but these errors were encountered:
The current state of timeouts in this library is confusing. There are keywords for
open-serial
(inherited from LW) for very fine-grained setting of timeouts (in seconds). But those are completely ignored in favor of per operation timeouts, specified in milliseconds. We should probably choose one and get rid of the other. I kind of like LW's API better here, but it would need to be extended with some functions to adjust the timeout after the serial port is opened.Additionally, the LW API lets you control per operation if an error is signaled or some default value is returned on timeout. I think this particular behavior is nice.
The text was updated successfully, but these errors were encountered: