Making my desktop app owned by explorer thread

Question

2.50/5 (2 votes)

See more:

Hi all !
When you peak to your desktop the gadgets still visible because it's owned by explorer thread , so is there any way to make my application stick to desktop when I switch to Desktop !?

Any help is appreciated.. thanks.

Posted 10-Oct-12 6:18am

Mazen el Senih

Add a Solution

Comments

fjdiewornncalwe 10-Oct-12 12:46pm

If you want a gadget, then build a gadget and not a desktop application.

Mazen el Senih 10-Oct-12 12:53pm

No I don't want a gadget ,The question is simple I think !

fjdiewornncalwe 10-Oct-12 12:59pm

Obviously not as simple as you think. If you want your application to behave like a gadget then you need for your application to be a gadget. If that is not what you want then you may need to use the Improve Question widget and add more information so that we get a better idea of what you need.

Christiaan Rakowski 10-Oct-12 13:05pm

I'm pretty sure this will be possible in C++ via some weird Win32 API, but that's only a guess. I also don't think C# will allow you to do this, since from a security point of view this could lead to many bad things. Again, I a not certain, just assumptions.

Mazen el Senih 10-Oct-12 13:08pm

Thanks for that encouragement ,yep I think that too (that's why I'm asking this) :)

Mazen el Senih 10-Oct-12 13:19pm

I think they should called it (Cww) "C weird weird" instead of "C plus plus" !!! :D

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)