|
Whatever you have taken, don't drive home...
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
This seems to be a common response (basically, "you must be on drugs!").
Which is odd, considering I have *never* taken drugs; as I responded earlier: I don't need them; never did.
|
|
|
|
|
Hi All,
When my Win 8 box goes to screen saver and I go to get it back, I have do the log in with a pass word. I have fiddled around in the screen saver options and found several things it could be such as 'system protection' but that it is not alterable, not s major wine just something I wish I could cure... 
Sorry mind you wine might explain a few things about it.
modified 20-Jul-15 9:34am.
|
|
|
|
|
Ok, this is so not what I was expecting to see when I read the title! You have an 'H' key. Please employ it and avoid (my) disappointment!
|
|
|
|
|
Ohh Blo*dy Hockysticks there isn't a click this and it will work as every other version of Windows, to get back you have to press a set key rather than just bash the key board??
|
|
|
|
|
Errrmm .... I was referring to your spelling of whine and the misleadingness of your title as a result!
|
|
|
|
|
I'm an engineer, besides wasn't English correction one of the Darlek's things. Just saying have you got a photo of you and Dave together?
|
|
|
|
|
I don't very often do it for the sake of it. It was the level of expectation raised by the mistake in this case! (Otherwise I'd have said something about Dalek not having an R in it, for example). 
|
|
|
|
|
Face + Palm. My spelling isn't that bad normally. I am typing (fat fingers) on a phone while waiting in a car. ...
|
|
|
|
|
Do you explicitly need a screen saver? My 8.1 desktop goes directly to screen off and then recovers without needing a password; so I know that is doable (and was my out of the box configuration inherited from the win7 install I upgraded to 8.1).
Edit: I don't think I had to give a password the last time a greedy piece of software enabled its screensaver by default when I upgraded it; but that was a while back so I'm not certain any longer.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging 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
|
|
|
|
|
Press Win-X to bring up the "system menu"
Choose "Control Panel"
type "Saver" in the "Search Control Panel" box
Click "Change screen saver"
Clear checkbox labeled "On resume, display logon screen"
Press "OK" to save changes.
Note that this is no different than windows 7, windows vista, windows xp, etc...
Decrease the belief in God, and you increase the numbers of those who wish to play at being God by being “society’s supervisors,” who deny the existence of divine standards, but are very serious about imposing their own standards on society.-Neal A. Maxwell
You must accept 1 of 2 basic premises: Either we are alone in the universe or we are not alone. Either way, the implications are staggering!-Wernher von Braun
|
|
|
|
|
The change screen saver option, On resume display logon screen, is what I wanted to changed, the option is greyed out. It's my own machine not connected to a network, I am using suitable permissions (I can create other users) just not alter the bleeding screen saver!
(Off point it is an HP machine bought in a rush as my previous desktop died, 8 installed up until then I always did the build it yourself route or Dell).
|
|
|
|
|
glennPattonBackInThePUB wrote: the option is greyed out
Which I'd expect on a server, not a client.
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
|
|
|
|
|
If you're attached to a domain, you may have a group security policy setting the screen saver logon setting and disabling the checkbox.
To change the group policy
WIN-X
click "Run"
enter gpedit.msc
navigate to User Configuration\Administrative Templates\Control Panel select Personalization
Try changing "Password protect screen saver" or "Prevent changing screen saver" or "Enable screen saver"
You may need to logon/logoff for the setting change to be realized.
If these options are not available, are reset or otherwise don't work, then try the following:
Try setting the registry value HKEY_CURRENT_USER\Control Panel\Desktop\ScreenSaverIsSecure DWORD to 0
If it gets reset then set the permissions for the key HKEY_CURRENT_USER\Control Panel\Desktop and deny Full Control to the SYSTEM. And then set the above DWORD to 0 again.
You may need to logoff/logon to have the registry setting realized.
If none of this works, incinerate the computer and deposit the ashes into the nearest Iranian nuclear facility.
Decrease the belief in God, and you increase the numbers of those who wish to play at being God by being “society’s supervisors,” who deny the existence of divine standards, but are very serious about imposing their own standards on society.-Neal A. Maxwell
You must accept 1 of 2 basic premises: Either we are alone in the universe or we are not alone. Either way, the implications are staggering!-Wernher von Braun
|
|
|
|
|
When I'm next in front of that PC I will give it a go!
|
|
|
|
|
It seems to mostly lead to trouble. For example, the dreaded Greek question mark[^], incomprehensible symbols being used as identifiers, unrendered boxes all over the place, and sometimes it looks like an operator but it counts as a whitespace[^].
Perhaps worst of all, they can't be keyed in easily. No, I'm not going to memorize a list of alt codes. Copy paste works, but it's annoying, especially if there are several different characters in use.
To be more precise, I actually don't mean to ban unicode (makes a catchy title though), but "problematic characters". If it's not on US keyboard (not even US International, no diacritics and such), it can't be in the code. Except string constants, because you may need them.
"But what about my math symbols and Greek letters??" NO! it's not a paper written in LaTeX, it's plaintext.
|
|
|
|
|
|
|
On a more serious note: Using alphabetical characters (plus the usual bit of +-[]{};.->()-stuff) is (at least where I work) considered Standard. Anything else ist just not gonna get into a production System, end of the Story.
|
|
|
|
|
Are there no advantages to being able to represent recognised constants by the Greek letters that usually signify them then? In any case, it will always be the case that making something illegal doesn't mean for a second that it stops happening!
|
|
|
|
|
You can just write out their names. That used to be how it had to be done, and it still is how it is done most of the time.
It's still Math.PI, not Math.π
|
|
|
|
|
harold aptroot wrote: It seems to mostly lead to trouble. For example, the dreaded Greek question mark[^], incomprehensible symbols being used as identifiers, unrendered boxes all over the place, and sometimes it looks like an operator but it counts as a whitespace[^].
Don't try to solve a problem that doesn't exists in the first place Both links are quite entertaining but how could it really happen? How are you going to replace anything in your friend's code without anyone knowing it? Even if you don't use pull requests then even subversion sports blame...
And if they leave their computer unlocked while they leave then it is still no different that old good flip screen orientation prank
--
"My software never has bugs. It just develops random features."
|
|
|
|
|
It also happens accidentally, for example when copying code from the internet or a pdf. Especially minus signs like to get corrupted into some sort of weird dash.
The Greek question mark, ok, that's mostly a joke.
|
|
|
|
|
I would agree. There appears to be little upside to allowing Unicode outside string literals, and lots of downside.
- Until all operating systems universally display all Unicode glyphs, you run the risk of not even being able to read the code.
- Until all compilers universally support Unicode tokens, your code may mean completely different things to different compilers. In the best case, the code won't compile. In the worst case, it will compile and give totally bogus results.
- A programmer who uses non-Latin tokens in their code may make things easier for him/herself, but much more difficult for anyone else who reads his/her code. This is an important consideration in these days of open source and international development teams.
I would rather read comments, etc. in poor English than attempt to puzzle out comments written in a mish-mash of perfect Chinese, English, Japanese, Russian, Urdu, etc.
I also note that if you have language-dependent string literals in your code, you should provide a localized set of strings for each supported locale. Many Standard-compliant (and other) methods exist for doing this.
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
Burn the witch![^]
Decrease the belief in God, and you increase the numbers of those who wish to play at being God by being “society’s supervisors,” who deny the existence of divine standards, but are very serious about imposing their own standards on society.-Neal A. Maxwell
You must accept 1 of 2 basic premises: Either we are alone in the universe or we are not alone. Either way, the implications are staggering!-Wernher von Braun
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
