|
About two weeks ago I asked your advice on some hardware, mainly two new monitors and a docking station.
You guys gave me some very good tips and recommendations and after taking everything into consideration... I did the complete opposite 
So I got two brand new Dell UtraSharp 25" monitors[^] and connected them with the new Dell D6000 Universal Dock[^].
My old keyboard had a "compatible with Win95" label and PS/2 port and my originally white mouse was a dirty yellowish color, so I decided to get a pretty standard Microsoft wired keyboard and mouse[^] as well.
Everything was plug n play and works like a charm 
Funny thing with the monitors, they're 2560 x 1440 and Windows recommends changing font sizes to 125%.
I agree that 100% is a bit small, but at 125% some text got blurry.
The solution is to choose a custom scale and set it at... 125%! 
Works like a charm, everything's crispy clear
Now to get twice as much work done!
|
|
|
|
|
Sander Rossel wrote: Now to get twice as much work done!
I'll have to try that at work. Hey manager, if you get me two decent monitors, I can get twice the work done!
Right now we have two crappy monitors, one is a 1280x768 dinosaur, the other a small 1920x1080And by "small", I mean it's physically a small monitor, not the nice big 23" monitors I have at home.
I should stop now, otherwise I'll go on ranting about the archaic i5, 8MB, 5400 RPM disk, crap as well. I have two laptops with better specs!!!
|
|
|
|
|
Marc Clifton wrote: I have two laptops with better specs!!!
I have a calculator with better specs!
I'm sorry, this is no laughing matter... To you
|
|
|
|
|
Marc Clifton wrote: 8MB
Wh... what? I can't think of a single thing in a computer that's only 8MB these days (or even recent-ish past days) 
|
|
|
|
|
Marc Clifton wrote: not the nice big 23" monitors I have at home.
Not to throw oil on that fire, but it's been a while I've considered 23" to be anywhere near "big". 
My smallest monitors start at 24", and that one looks bigger than it actually is because it's running in portrait mode (which is great for web pages and source code)
|
|
|
|
|
|
Well done, I have a couple of UltraSharp monitors too, apart from a minor issue with not automatically recognizing the (display)port in use, I'm very pleased with them !
|
|
|
|
|
Those Ultrasharps are very nice. I bought one last year, and I was stunned how clear it was.
One note: if you notice and update freezes or twitchiness, you might need a firmware update. Dell denied there was a problem at first, they have since repented.
Charlie Gilley
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
I've used that tactic
Customer calls: "Sander, there's a bug in the software."
Me: "Really? I can't imagine our software has any defects..." while quickly doing an update.
Customer: "Yeah really, if I do... Huh, it works now, but it didn't a minute ago!"
Me: "Seems like you've really lost it this time..."
Customer: "Did you just do an update!?"
Me: "You can't prove that "
|
|
|
|
|
That's the same keyboard I ended up with - it's not too bad, is it? Feel is good, and I'm slowly getting used to where the keys are...
I prefer my Logi trackman to those mice though.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
It's layout is closest to the old keyboard I had.
For some reason I do need a little getting used to though.
Probably because I'm now used to my laptop keyboard 
|
|
|
|
|
Those are a good resolution. I like having 1440 lines. I have 1200 at work and it's pretty good but I have 1440 at home. I would probably have gone for the 27s at that resolution just to get the text bigger, although they are twice the price. I would also have looked for some that are cheaper than Dells. 
|
|
|
|
|
Enjoy!
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
Sander Rossel wrote: So I got two brand new Dell UtraSharp 25" monitors[^]...
Just looked them up on Dell Australia, faarrrkkkk me sideways with an elephant, AUD$649.00, profiteering anyone?
Dell UltraSharp 25 Monitor: U2518D | Dell Australia[^].
Michael Martin
Australia
"I controlled my laughter and simple said "No,I am very busy,so I can't write any code for you". The moment they heard this all the smiling face turned into a sad looking face and one of them farted. So I had to leave the place as soon as possible."
- Mr.Prakash One Fine Saturday. 24/04/2004
|
|
|
|
|
Dell regular price are always to high so they can have big sale as the 200 rebate currently in the US.
I don't remember the last sale price I saw but is has probably close to AUD$450.00. Still higher than the US price even with taxes excluded but a good price for that monitor. I have the previous model (U2515D) at home and it great. Thinking about getting one for work as I miss having Visual Studio on a QHD resolution.
Vince
Remember the dead, fight for the living
|
|
|
|
|
Ever since updating to the latest version, when I enter debug on a breakpoint, there's a 15 second "mouse is lagging" where the whole UI, mouse, keyboard, etc., stutters. It's really annoying!
[edit]Sigh. Seems to the keyboard/mouse activity monitoring that I added, that sets a windows hook. Removed that, and no issues. This is what I'm doing:
Detecting mouse and keyboard input with .NET
So, beware of SetWindowsHookEx when debugging!
[/edit]
modified 23-May-18 13:59pm.
|
|
|
|
|
just did most recent VS 2017 update - no issues. however, the windows 10 update took about an hour, big one. Might want to make sure that is done too (if you have windows 10).
are your mouse and keyboard wireless? If so, reboot and try again?
|
|
|
|
|
This is happening on two separate dev boxes. Both W10, latest version of VS2017. Both are laptops, but on one, wired keyboard and wireless mouse, the other one is just the built in keyboard and touchpad.
So, definitely not specific to the machine. It's definitely VS, as the stuttering goes away after a few seconds.
|
|
|
|
|
See the edit to the original post. You got me thinking and I realized there is a common thing going on in the code I'm debugging on both machines.
|
|
|
|
|
Marc Clifton wrote: So, beware of SetWindowsHookEx when debugging!
Reminds me of when I was debugging WM_PAINT handlers in the 90s. 
/ravi
|
|
|
|
|
|
Seems like it.
/ravi
|
|
|
|
|
Strange coincidence...I was playing with low level hooks yesterday. I had an idea for a small application. I thought it might be fun to write an article about it.
Then, I ran into this same problem. I starting thinking about readers running into the problem. I preemptively sensed the blame pursuing me backwards through time.
I decided to pursue a different project
|
|
|
|
|
I had the same problem with VS2015. Thinking about this, it's tough problem for MS developers. Program registers global mouse hook, so callback function is called on every mouse event. When the program breaks in the debugger and mouse moves, our callback is called, and everything is stuck.
I think that Windows finally detects problematic function in the hook chain and kicks it off, but this is only my guess.
|
|
|
|
|
huh, it's been a long time but I don't recall having that issue 12 or 13 years ago in VS2003 when hooking the mouse and keyboard.
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
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
