|
|
Point 2:
That should be coming - this is a bad spelling mistake that I won't explain. And wait until you're home before you research why.
Iain.
Codeproject MVP for C++, I can't believe it's for my lounge posts...
|
|
|
|
|
ROFL 
|
|
|
|
|
You didn't have to delete the message, just edit it a little.
In hindsight, I should have emailed you, rather than posting a reply.
It was a legitimate question, so I hope you repost soon and get helpful replies.
Iain.
Codeproject MVP for C++, I can't believe it's for my lounge posts...
|
|
|
|
|
Iain Clarke wrote: You didn't have to delete the message, just edit it a little
But you can say thanks[^] like me.
Of one Essence is the human race
thus has Creation put the base
One Limb impacted is sufficient
For all Others to feel the Mace
(Saadi )
|
|
|
|
|
Hmm, has he deleted all his messages?
Very polite of you sir!
Iain.
Codeproject MVP for C++, I can't believe it's for my lounge posts...
|
|
|
|
|
Hi All
How to get connected USB Device name?
|
|
|
|
|
newhivc wrote: How to get connected USB Device name?
What do you mean by that?
What kind of device is it?
How do you want to discover it? By enumerating the USB tree or when the user inserts the device in a port or both?
Do you have a way to recognize the device when you encounter it during a USB enumeration, such as part of the device name?
Getting the device name when the user attaches the device to the system is fairly straight-forward:
You register for device notification for the device class the particular device belongs to and handle the WM_DEVICECHANGE message. The device name is part of the struct that is passed as an argument to the message handler.
"It's supposed to be hard, otherwise anybody could do it!" - selfquote
"High speed never compensates for wrong direction!" - unknown
|
|
|
|
|
To extend Roger's answer - if you're interested in devices being plugged in / out, have a look at my article:
http://www.codeproject.com/KB/system/Drive_Detect.aspx[^]
It's aimed at drives, but I use it in my work to detect a certain class of USB devices also - and they're not pen drives.
Iain.
Codeproject MVP for C++, I can't believe it's for my lounge posts...
|
|
|
|
|
|
Jijo raj wrote: 1. Enumerate Properties of an Installed Device[^].
2. Enumerate Installed Devices Using Setup API[^].
Whats the different between these links except their titles?
Of one Essence is the human race
thus has Creation put the base
One Limb impacted is sufficient
For all Others to feel the Mace
(Saadi )
|
|
|
|
|
Hamid. wrote: Whats the different between these links except their titles?
Copy/Paste error.  Thanks!
Regards,
Jijo.
_____________________________________________________
http://weseetips.com[ ^] Visual C++ tips and tricks. Updated daily.
|
|
|
|
|
Yeah. 
Of one Essence is the human race
thus has Creation put the base
One Limb impacted is sufficient
For all Others to feel the Mace
(Saadi )
|
|
|
|
|
Do you need to Win32_USBControllerDevice also this article is helpful form you Detecting Hardware Insertion and/or Removal[^].
Of one Essence is the human race
thus has Creation put the base
One Limb impacted is sufficient
For all Others to feel the Mace
(Saadi )
|
|
|
|
|
hi experts please let me know how to find all depenent .DLLs,.EXES that depends on a particular .exe in vc++ 1.52(dependency walker is not working in vc++1.52)
kir_MFC
|
|
|
|
|
You need to use Dependency Walker[^] why it doesnt work?
Of one Essence is the human race
thus has Creation put the base
One Limb impacted is sufficient
For all Others to feel the Mace
(Saadi )
|
|
|
|
|
Because Visual C++ 1.52[^] produces 16-bit applications and dependency walker won't work on 16-bit modules. Here[^] is a dos utility to find dependencies of 16-bit apps. Hope it helps.
Regards,
Jijo.
_____________________________________________________
http://weseetips.com[ ^] Visual C++ tips and tricks. Updated daily.
|
|
|
|
|
You'll only be able to discover those DLLs that are loaded implicitly.
"Love people and use things, not love things and use people." - Unknown
"The brick walls are there for a reason...to stop the people who don't want it badly enough." - Randy Pausch
|
|
|
|
|
we have developed an application say "A"(form view) where in it hides the entire desktop area(restricting windows access). Title bar has been hidden.
Now we are invoking another dialog based application say "B"using shellexecute through the above mentioned application. As I can see a little gap on left and bottom of the application "A" which can't be covered, and if I perform mouse click over there the invoked application "B" goes back(as per our requirement which shouldn't go back).
Please suggest me how can I handle such situation
modified on Monday, January 12, 2009 1:25 AM
|
|
|
|
|
You can use of this code SetWindowPos(&hwndTopmost, NULL, 0, 0, 0, 0, SWP_NOMOVE | SWP_NOZORDER); but for more info see
Makes any windows "Always On Top"[^]
Keep your Window Always On Top[^].
Of one Essence is the human race
thus has Creation put the base
One Limb impacted is sufficient
For all Others to feel the Mace
(Saadi )
|
|
|
|
|
Hamid has a good idea.
Another alternative is to make B.exe create a full screen, but transparent window - then have CBDlg be a child of that.
Lastly - assuming you're creating both of these applications, you could called B.exe with a parent that can be decoded into a window handle which you then use as the parent window for B.exe.
This is how screen savers work - no parameter means full screen saving. Control panel calls them with various parameters for preview, draw in little window or configuration dialog box - all with a window handle passed as a parameter.
Iain.
Codeproject MVP for C++, I can't believe it's for my lounge posts...
|
|
|
|
|
|
BOOL
PASCAL FAR
AcceptEx (
IN SOCKET sListenSocket,
IN SOCKET sAcceptSocket,
IN PVOID lpOutputBuffer,
IN DWORD dwReceiveDataLength,
IN DWORD dwLocalAddressLength,
IN DWORD dwRemoteAddressLength,
OUT LPDWORD lpdwBytesReceived,
IN LPOVERLAPPED lpOverlapped
);
For the 2nd parameter,
why not use IN SOCKET &sAcceptSocket instead.
|
|
|
|
|
followait wrote: For the 2nd parameter,
why not use IN SOCKET &sAcceptSocket instead.
Because if you look at what a SOCKET is, you'll see that it is just an UINT_PTR. In fact a SOCKET is just a handle to a win32 internal object. So, yjust passing this handle is enough, you don't need to pass the handle by reference.
|
|
|
|
|
because the second parameter is not a return value. In AcceptEx,You need to have accept socket opened already unlike the accept API in which the socket is returned.
from msdn,
Another key difference between the AcceptEx function and the accept function is that AcceptEx requires the caller to already have two sockets:
One that specifies the socket on which to listen.
One that specifies the socket on which to accept the connection.
The sAcceptSocket parameter must be an open socket that is neither bound nor connected.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
