H. G. Parra
H. G. Parra
I'm actually surprised it doesn't have it already. Will check.
Support added for Windows in 1.0.4. Still need POSIX support? See #16
Please see https://github.com/hparra/ruby-serialport/discussions/77
I'm not entirely sure. It seems the problem is just an unexpected default setting. In that case I'm reluctant to commit the line change because it could break existing systems...
Please see https://github.com/hparra/ruby-serialport/discussions/77
flipback: Very strange. Are you just running through a loop? Can someone confirm on another POSIX system, e.g. Mac OS X, and Windows? HGP
Could you send me a functional test to duplicate this? Just a small file where I pass in the port address should be fine.
I think I see what's happening here. Poor design. Please confirm. The documentation specifies that you can pass a millisecond value, but the truth is the underlying structure (POSIX anyway)...
I'm interested in the Windows behavior as well. If anyone can check I would appreciate it, but in looking at the code the millisecond value is passed straight to Windows,...
Yes, the magic number with internal arithmetic was 50 - used to round up to the nearest whole decisecond, so 150-249 ms became 200ms. I'm not sure how I feel...