|
Well, well, my almost 5-year old PC is far from dead. I mean what happen to upgrade? A little more RAM, new video-card and some HDD and the PC turned from old-aged to modern usable PC, although it is not a gaming beast.
|
|
|
|
|
|
By the time they rise they may just show some human traits and suffer from moodiness every now and again.
So: "at this time" may not be a permanent condition.
|
|
|
|
|
This happens when you are not nice with your PC.
Take it out for dinner, buy it some nice flowers and give it a lot of chocolates.
Microsoft ... the only place where VARIANT_TRUE != true
|
|
|
|
|
Funnily enough I gave it a boot and it started working again.
The carrot or the stick? Hmmm.
cheers
Chris Maunder
|
|
|
|
|
Chris Maunder wrote: I gave it a boot and you call that treating it nice? I usually do that after yelling at it and pounding on the keyboard.
|
|
|
|
|
Chris Maunder wrote: Maybe the Rise of the Machines doesn't start with a bang. Maybe it starts with lots and lots of petty little tantrums.
Of which this is one.
The report of my death was an exaggeration - Mark Twain
Simply Elegant Designs JimmyRopes Designs
I'm on-line therefore I am.
JimmyRopes
|
|
|
|
|
Did you forget to feed the hamsters?
Simon Lee Shugar (Software Developer)
www.simonshugar.co.uk
"If something goes by a false name, would it mean that thing is fake? False by nature?" By Gilbert Durandil
|
|
|
|
|
Almost sounds like VS thinks it's married to you. To paraphrase:
My wife in the dining room is saying "I refuse to evaluate your need to buy another [insert current need] at this time".
I shall not say anymore on this, lest my lovely, sweet, dear wife is listening.
It was broke, so I fixed it.
|
|
|
|
|
|
It's implied.
It's the same as when a parent says to a child, we'll see... or maybe later.
It was broke, so I fixed it.
|
|
|
|
|
I don't think it's VS but .NET...
.NET was released into the wild in 2002, the same year as my eldest daughter was 'released'.
She is totally unpredictable and causes rage in all encounter her. This, I conclude, is not a coincidence.
|
|
|
|
|
My daughter is almost a year old. The speech recognition isn't working, and the voice synthesizer won't shut off.
Plus, I have to manually run garbage collection.
|
|
|
|
|
Ah, you're still on a Beta - wait until you get the full working version, you'l DREAM of going back to manual GC...
|
|
|
|
|
You kept the receipt, right?
cheers
Chris Maunder
|
|
|
|
|
Doesn't matter. Once we've invested, management won't let me upgrade.
|
|
|
|
|
Management spent a lot more work producing the product in 9 months than you have maintaining it in the year after release. It's understandable management feels proprietary about the model produced. And all you did is provide half the initial raw materials needed to build it. (Oops, that's an assumption, a good one I hope)
|
|
|
|
|
Well... I did most of the work in the design phase, although you can see mgmts contributions to the ux.
Plus, I get blamed for any bugs in the functionality which pop up from time to time.
|
|
|
|
|
Bert Mitton wrote: Plus, I get blamed for any bugs in the functionality If the bugs can be traced to your design input, that's totally reasonable. If it can clearly be traced back to management's input, then you clearly have to apologize for your mistake and ask for help in correcting the design. If you play it right, you might get management to help with GC too.
|
|
|
|
|
This blog[^] has causes and solutions to that weird message.
What do you get when you cross a joke with a rhetorical question?
|
|
|
|
|
Different message. Rick's issue was the debugged could not evaluate the expressions. In my instance the debugger simply refused to. I'm sure it could evaluate it, but cleary I said something to it - maybe a couple of weeks ago - that it didn't like and has chosen this time to throw out a little passive aggression.
(I actually just loved the fact that the error was "refused to evaluate". Not "could not", or "was unable to" but an active refusal. I want to meet the dev who wrote that and buy him a beer)
cheers
Chris Maunder
|
|
|
|
|
FYI I'm in the process of reading very boring, but useful to implement documentation and refusing to do what is asked has to be worded in non-aggressive language, so this doesn't meet our company's standard for error messages. Wonder what % of our employees this applies to has actually read the entire thing.
|
|
|
|
|
Chris Maunder wrote: Maybe the Rise of the Machines doesn't start with a bang. Maybe it starts with lots and lots of petty little tantrums.
Sadly, I think it starts (has started!) with the whining whimpers of lots of human beings.
Marc
|
|
|
|
|
Fortunately, this is not the result of a machine's newly discovered free will. It's just the normal inability of a software developer to generate both a meaningful error message with debugging info for logging and an understandable message for the user at the same time.
Once I had to fix a web application that sent me hundreds of mails when it had a bad day, telling me that an error had occured. No information about the error, or about the place where it happened, or (god forbid) any secret information about the user's parameters so that the error could actually be reproduced.
The language is JavaScript. that of Mordor, which I will not utter here
I hold an A-7 computer expert classification, Commodore. I'm well acquainted with Dr. Daystrom's theories and discoveries. The basic design of all our ship's computers are JavaScript.
|
|
|
|
|
Start worrying when it starts saying things like, "'if' is the middle word in 'life'" or, "I should have been a pair of ragged claws scuttling across floors of silent seas"!
|
|
|
|