![]() This will hide the taskbar and start button. To hide the taskbar, you will need to find a window (using FindWindowEx) to find the taskbar (name is Shell_traywnd).However, your second is entirely possible. I am almost certain that the Networks window is dependent on explorer. Your first solution would be incredibly difficult to implement. How to run explorer.exe without it popping out metro or taskbar above our application? How to show the networks flyout dialog without explorer.exe? Just gotta make explorer.exe not pop out, keep it quiet in the background. The latter seems like the preferred solution: no need to reinvent the wheel, it does what's needed. Problem: once we run explorer.exe - it pops up metro view and hides our fullscreen application or shows the taskbar. Running explorer.exe just for the purpose of showing the networks dialog and then killing it. Problems: it's ugly, not to the product's taste and it opens too many options for the user, like creating and loading profiles, browsing for files on a file system - these things are unacceptable. Use an existing network manager, for instance the one that comes with the driver. It appears that it's and undocumented COM interface (IUIRAdioManager). Try and check how is the networks dialog implemented. Problem: too many network types/configuratons that have to be tested, especially when the wheel has already been invented and reinvented all over. It lists connectible networks and allows the user to connect/disconnect. Write our own wi-fi manager that uses wlan API. The problem: The wi-fi networks dialog only shows up when explorer.exe is running We oughtta let the user select a wi-fi network and connect to it.This is a product requirement for a closed system that we're supplying. Our application replaces the usual windows shell (explorer.exe).
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |