|
I haven't used serial communications in .net very much, but have written a serial port wrapper suitable for use with my CommScript[^] class.
|
|
|
|
|
Only had a quick look, seems interesting!
|
|
|
|
|
Thanks.
It looks like I began writing an article on my SerialCommunicator back in 2010, but I never finished it. 
|
|
|
|
|
I love LiqPad and use it all the time.
Powershell is the tool to use in most "scripting" scenarios, IMHO.
|
|
|
|
|
Never heard of it, but knowing my management, someone will read a blog about it and announce that it's the next great thing and everyone has to use it.
I'll continue to roll my own as needed, thanks.
modified 27-May-21 17:19pm.
|
|
|
|
|
As far as I can tell it's HTML with a few add ons <<quake>> 
|
|
|
|
|
|
Do I need to actually fill this in? Didn't think so!
But if I need one, here's my continual pet peeve: why does VS randomly change the "Find" (Ctrl+F) or "Find All" (Ctrl+Shift+F) document selection from "current document / entire solution" (respectively for the pressed keyboard shortcut) to "all open documents", "entire solution", or whatever else it thinks is the option of the day based on various planetary conjunctions?
|
|
|
|
|
I use that often but have never had it happen. Currently on VS2017. I wonder what explains it.
|
|
|
|
|
I've never noticed that and I use it all the time.
You have a prankster in your office. 
|
|
|
|
|
I can reproduce it by scrolling the mouse wheel while positioned over the "Look in:" drop-down menu. Are you using some kind of bizarre input device that allows you to inadvertently do this? 
|
|
|
|
|
Cool! I can do this with my laptop's mousepad, really useful! Never had it happen inadvertently (Ctrl-F seems to remember the previous scope) but this means I can change the scope really easily. Thank you Marc and Greg!
|
|
|
|
|
Glad you liked it! I didn't know whether to consider it design intent or a bug.
|
|
|
|
|
I don't think there is a difference between the two in Microsoft land.
|
|
|
|
|
True story! 
It's also what I tell my boss on lazy days!
|
|
|
|
|
Oh wow, this happens when hover the mouse over any of the dropdowns in the dialog!
|
|
|
|
|
not just dropdowns in VS. WIndows default behavior is for the wheel to scroll whatever the cursor is over regardless of if it has focus or not.
99% of the time I like doing that. The last 1% I start swearing when after a scroll I try to do something else and discover that focus wasn't where I thought it was.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
|
|
|
|
|
Greg Utas wrote: I can reproduce it by scrolling the mouse wheel while positioned over the "Look in:" drop-down menu.
You know, that might very well be the problem!
Greg Utas wrote: Are you using some kind of bizarre input device that allows you to inadvertently do this?
Maybe using my cat as a mouse assistant has it's drawbacks. 
|
|
|
|
|
Greg Utas wrote: scrolling the mouse wheel while positioned over the "Look in:" drop-down menu
It does that on all dropdowns. That's been a feature forever.
|
|
|
|
|
|
All great companies started out with a scribble on a napkin. 
|
|
|
|
|
|
Six hours of debugging can save you five minutes of reading documentation.
"If we don't change direction, we'll end up where we're going"
|
|
|
|
|
Who has time to read?
I’ve given up trying to be calm. However, I am open to feeling slightly less agitated.
|
|
|
|
|
That's because they're too busy debugging!
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
