The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
Could be one of your screens momentarily disconnected. Windows then tries to "adjust" as best as it can.
It does mess up from time to time.
On my work laptop I currently have 7 screens according to windows (In reality I only have 3 if I count the laptop screen itself)...
And disconnecting them seems to only confuse windows into thinking they are still there. It's annoying as hell, cause everything then opens on my second screen that isn't there...
At home I'v never had any problems with it though and there I have 4 screens, if I disconnect one windows instantly goes to another configuration, connect it again and it goes back to the original configuration.
I guess it depends on window's mood while installing it?
Same here. A new NVidea driver installed yesterday or the day before. While the driver installed both monitors flashed, but all was well after the installation. I have found that the monitors flash quite often when a new video driver is being installed. I consider this "normal" and it has little to do with Windows.
Quite often, but I use Windows Surface Pro 3, both at work and home. When docking station (for some Microsoft knows what reason) lost connection with the device, all open windows get scrambled between two monitors.
There is only one Vera Farmiga and Salma Hayek is her prophet!
Advertise here – minimum three posts per day are guaranteed.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare
A date is represented as either a floating point value or "datetime". So far so good.
I set the date to 0, and the resulting datetime representation was null. Hmmmm.
I set it to 1, and the datetime was 31 Dec 1899. Well, okay... I guess.
The real adventure starts when you try to find the absolute max datetime that can be represented. There is no documentation that I could find that says what this value is, and I think I know why.
That value is 313740917827896, or 31 Dec 4294967295.
If you add 1 to the numeric value, the represented datetime becomes 01 Jan 0000.
If you continue adding, you can go all the way to 313740918558381, which gives you a datetime of 31 Dec 1999.
If you add 1 to that value, it finally overflows into something that evidently cannot be interpreted as a date.
If you really want a laugh, I changed that absolute max value to a negative number, and I got a datetime of 4294967292 Jan 1900. Yes, that first number is the DAY. Curiously, it's almost the same value as the max possible year (before it wraps around).
I don't know whether to laugh or cry...
".45 ACP - because shooting twice is just silly" - JSOP, 2010 - You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 - When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
No it's not, why start with a number that only changes once in a millenium?
The least you could do is stick that somewhere in the middle!
Start with the day, however, and you'll probably never have to read past the first two digits
I don't understand why you're so in love with numbers. Nothing beats localized text so better to use "dddd d MMMM yy". It's just so readable and drops the unnecessary century. We're all at the same millennia here, right?
Last Visit: 31-Dec-99 18:00 Last Update: 18-Aug-17 1:51