|
|
|
Are you sure they all weren't Samsung washers just blowing up on their own?
if (Object.DividedByZero == true) { Universe.Implode(); }
|
|
|
|
|
Pom Pey wrote: The weirdest thing about it all he was breaking into people’s house’s just to ruin their washing machines by putting bricks into them and turning them on. Very strange if you ask me
To a washing machine repairman, that's not weird, that's brilliant.
|
|
|
|
|
kinda like the volunteer firefighters starting brush fires
Director of Transmogrification Services
Shinobi of Query Language
Master of Yoda Conditional
|
|
|
|
|
MadMyche wrote: kinda like the volunteer firefighters starting brush fires
If they're volunteers...what's the payoff?
|
|
|
|
|
Adrenaline.
Also a great excuse to avoiding honey-do lists
Director of Transmogrification Services
Shinobi of Query Language
Master of Yoda Conditional
|
|
|
|
|
"I've never killed a man but I've read many an obituary with a great deal of satisfaction."
|
|
|
|
|
Did he just Vanish in a Flash?
|
|
|
|
|
To those that install the update, I see they added more features [again],
but did they fix any old the older broken ones?
|
|
|
|
|
lopati: roaming wrote: did they fix any old the older broken ones?
Ha ha ha ha ha ...
I do love an optimist!
I'm still waiting for a problem in VS2005 to get fixed: If you create an abstract control, you can't use the designer on concrete derived controls unless you create a concrete intermediary class.
I.e. this gives a designer error:
public abstract class MyBase : UserControl {...}
public class MyDerived: MyBase {...}
But this doesn't:
public abstract class MyBase : UserControl {...}
public class MyConcrete: MyBase {}
public class MyDerived: MyConcrete {...} Which kinda kicks the whole advantage of the abstract base class right into the bin, or forces you to have different code for release and development - which is an anathema.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
OriginalGriff wrote: I'm still waiting for a problem in VS2005 to get fixed
Hmmm, I think you could be waiting for quite a while as support for 2005 ended in 2016.
98.4% of statistics are made up on the spot.
|
|
|
|
|
That's OK - it's still there in 2008, and 2010, and 2013, and 2015, and 2017. So I'm not betting on a fix any time soon...
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Well, we can't complain about a lack of consistency, then.
Experience does rather suggest that a 13 year-old bug is never, ever going to be fixed. It's a teenager now and nobody can talk any sense to it.
98.4% of statistics are made up on the spot.
|
|
|
|
|
That would explain when VS went to the Dark Side: it just hit puberty and painted its UI black.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Do you think it went Emo or Goth?
|
|
|
|
|
Emo - it's forever complaining...
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
OriginalGriff wrote: Date: | Thursday, May 10, 2018 3:29am |
That would explain when VS went to the Dark Side: it just hit puberty and painted its UI black. |
I just figured Microsoft hired the colorblind idiot from Apple who thinks black & white is sufficient for a modern display. Dumping the colors after the 2010 releases of everything was just stupid and reduced usability.
|
|
|
|
|
obermd wrote: ... was just stupid and reduced usability
So, puberty then?
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
|
As much as it's something that millions have wished that it would do over the years, it's really hard to argue that it was ever a bug or even an omission.
Notepad exists as a simple DOS/Windows text-editor and has never tried to claim any grander purpose than that.
Those of us (lets be honest, pretty well all of us) who have at some point used it to work on files from sources other than its native OS, have, in truth, being using the product for something for which it was never intended.
Microsoft could, had they wished, have made a very strong - possible inarguable - case for not doing it but have instead taken a pragmatic line and decided to give us a feature that we've always wanted even though it could be classed as mission creep.
98.4% of statistics are made up on the spot.
|
|
|
|
|
Oh, I'm totally with you. While I'm glad to see it "fixed", as I do sometimes mix Windows and Linux files, I'm just hoping it doesn't start a trend of feature creep and changing known behavior.
But it is nice that they've allowed for a registry entry to revert to the old behavior.
|
|
|
|
|
Yes, the "turn-offability" is a nice touch.
I think Microsoft have actually got something completely right for once!
98.4% of statistics are made up on the spot.
|
|
|
|
|
It's an accident - and if they find out, I'm sure they will correct it!
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
You just wait. They'll find a way to mess something up.
(The voice of experience in dealing with everything MS)
|
|
|
|