|
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!
|
|
|
|
|
This applies to anything where assembly is required. I've learned to RTFM!
"Go forth into the source" - Neal Morse
"Hope is contagious"
|
|
|
|
|
Judging by QA, most developers can't use a debugger either ... 
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Debuggers are elephanting useless. They cant tell me why my code wont compile!
"If we don't change direction, we'll end up where we're going"
|
|
|
|
|
Admit it, you got that from QA didn't you?
Keep Calm and Carry On
|
|
|
|
|
Who? Me??
"If we don't change direction, we'll end up where we're going"
|
|
|
|
|
Speaking as one that wears all 3 hats, (not at the same time mind you, I would look rather silly), as a developer, the primary focus is to not create bugs when adding new features and certainly now when fixing features. Yes that can be easier said than done, especially as spaghetti code is often at the root cause of many bugs, and debuggers are critical tools needed to help find and fix things. But that is only part of the story, QA and users do unexpected things which developers should for tell and protect against.
As a QA lead it is a challenge to break code other developers create, and sometimes its the role of the customer to find the really obscure issues.
As a documenter the clarity of what gets written is as important as the accuracy of what is written. I say this after inheriting documentation from two predecessors who claimed to write good English and keep the changes made up to date, (yes that was a laugh).
So to summarise, the whole lifecycle can be a real pain, we simply have to do the best we can with the resources to hand, unless anyone has a time machine or working crystal ball.
Bobby Dazzler
|
|
|
|
|
Documentation is for lovers or those with special needs.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
