-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enhancement Request: Allow for easier opening of COMx (x>=10) on Windows #22
Comments
@swabianeagle good catch, I would accept a pull request from you with this change, if you'd be so kind! |
Hi Adrian, sorry for my ignorance as I don't know git very well. What exactly do I have to Armin
|
First you'll want to fork this repo, https://help.github.com/articles/fork-a-repo/, and make the appropriate changes in your fork of |
Can you please tag a new release with this fix? It's a fairly serious problem on windows systems. Also, keeping the issue open is sure to cause some confusion, given that the issue is fixed in master (but not in the latest release). |
Ulp! You are right, let me see if we can fix that today. |
I just released version 0.2.3 please make sure this corrects your issue, and reopen if not. Thanks! |
I'm using rubyserial 0.2.1.
Currently, when using rubyserial on Windows I get the following results when opening a serial port:
Arguably it is my mistake that opening COM17 fails the first time, but it seems asymmetric to me that it works with COM8.
I added the following line to windows.rb and this seems to work:
added this to Serial#initialize (windows.rb, line 5)
address = "\\\\.\\#{address}" # needed for com-ports >= COM10
Now the behavior is symmetric:
Adding the prefix multiple times doesn't seem to matter (I've tried it), so it should be safe to blindly add the prefix by default as I did.
Maybe this could be added in the next release.
The text was updated successfully, but these errors were encountered: