prevent monitor getting turn on by key board or mouse

Question

3.33/5 (3 votes)

See more:

Dear Friends,
I tried turning off monitor using sendMessage.
but whenever a mouse is touched or any key is pressed it will turn back on.
Is there a way to trap these mouse/keyboard events in between and prevent turning on monitor back. I can make a special combination like alt+a or whatever when pressed only then monitor will get turn on other wise will remain off. If there a way around please show me.

Posted 24-Feb-11 7:29am

Rohit Bansal The Great

Updated 19-Mar-11 21:42pm

Abdul Quader Mamun

v2

Add a Solution

Comments

Toli Cuturicu 24-Feb-11 16:08pm

Don't do it!
Else people will delete your software at once and call you Rohit Bansal The little!

fjdiewornncalwe 24-Feb-11 22:37pm

Perhaps you need to explain why you are trying to do this and then someone here is likely to have a solution for you. At the outset, I see very little practical use for this type of process other than a piece of code that is invasive.

Аslam Iqbal 20-Mar-11 6:06am

Really? its not a good idea.

cyril269 19-Apr-11 8:05am

One good reason for this is that for example when you are running Windows in Mac BootCamp and there is no physical power button to turn off the monitor only. And I usually remote control my office workstation from home so I wouldn't want anyone else in the office see what I am actually doing because they can see what the computer is doing without me actually being there.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Answer 1 · 2011-03-19T22:36:00

Solution 1

I can see no good reason to want to do this, but I can see several malicious ones.

If you have a good reason to do this, but do not know how to, what are you doing in your current job?

Posted 19-Mar-11 22:36pm

OriginalGriff