C / C++ / MFC

19-Jun-02 5:45

Hi!

I want to remotely close an app. What I already tried was to use SendMessage() with messages like WM_CLOSE, WM_QUIT, WM_ENDSESSION and so on. I want to close the filesharing program "KaZaA". But for some reason it does not like the messages Wink | ;)

WM_CLOSE: Kazaa simply minimizes itself
WM_QUIT: Nothing happens
WM_ENDSESSION: Kazaa quits, but it crashes Big Grin | :-D

Is there another SMOOTH way to close an app so that it still will be able to finish some tasks before quitting?

thanks in advance

modified 12-Sep-18 21:01pm.

Hans Ruck19-Jun-02 5:56

Hans Ruck

19-Jun-02 5:56

Try using Spy focused on Kazaa to see the messages it receives on closing.

rechi

User 665819-Jun-02 6:02

19-Jun-02 6:02

Seems like Kazaa processes WM_DESTROY and WM_NCDESTROY, but it doesn't help work if I send them via SendMessage()

modified 12-Sep-18 21:01pm.

Marc Richarme19-Jun-02 7:05

Marc Richarme

19-Jun-02 7:05

This might be a little tricky, but you could try to simulate the user clicking "Close" in the trayicon menu

Cheers,
Marc
_{Click to see my *real* signature}

User 665819-Jun-02 7:07

19-Jun-02 7:07

I already thought about this option, but have no clue how to do that Frown | :(

regards

modified 12-Sep-18 21:01pm.

19-Jun-02 8:02

try sending WM_SYSCOMMAND, wParam=SC_CLOSE, lParam=0

User 665819-Jun-02 8:15

19-Jun-02 8:15

This minimizes the window into the tray

modified 12-Sep-18 21:01pm.

19-Jun-02 8:54

okay, then send a close request to the mainframe (the parent window which is creating the systray icon and main dialogs).
If Kazza is an MFC application I would send a WM_COMMAND with wParam=ID_APP_EXIT. Or try spying which messages Kazza is sending to itself when terminating.

PS: are you doing a new P2P worm? Smile | :)

User 665819-Jun-02 9:16

19-Jun-02 9:16

*lol*, no

I'm coding a plugin for a Half-Life/CounterStrike server joining tool, which terminates filesharing programs in order to prevent lags when joining a server.

Back to topic:
It seems line Kazaa sends WM_COMMAND with following values:
wParam 00008066
lParam 00000000

maybe this works Smile | :)

SendMessage(wndKazaa, WM_COMMAND, ???, 0);

with what do I replace the three questionmarks?

modified 12-Sep-18 21:01pm.

James R. Twine19-Jun-02 8:09

Any samples for inserting an image into a BLOB field of a DB2 table using VC++ 6.0?

19-Jun-02 8:09

Use the aforementioned Spy++ utility to see what message(s) get sent to it when it is closed from the context menu.

Peace!

-=- James.
"Some People Know How To Drive, Others Just Know How To Operate A Car."
[Get Check Favorites 1.4 Now!]

Shayna19-Jun-02 5:27

Shayna

19-Jun-02 5:27

Anyone has any sample code for inserting an image into a BLOB field of a DB2 table using VC++ 6.0?

Please help. Cry | :((

Retreiving BSTR

Hans Ruck19-Jun-02 5:09

Hans Ruck

19-Jun-02 5:09

I use this:

STDMETHODIMP CMediaServer::GetUrnList(BSTR *pRetval)
{
  char *sz=global_heart.m_pDataBase->GetUrnList(); // works fine, sz is ok
  if (sz)
  {
    *pRetval=_bstr_t(sz);
    delete [] sz;
  }
return S_OK;
}

to obtain a string from an interface, and this:

BSTR x;

((IMediaServer *)ptr)->GetUrnList(&x); // ptr is ok
_bstr_t xx(x, FALSE);
CString szMan;
szMan.Format("%s", xx);
AfxMessageBox(szMan);

to test the stuff. The string in the message box is something unreadable, so i'm asking: where is the mistake?

rechi

Nope (Was: Re: Retreiving BSTR)

19-Jun-02 5:19

Bogdan Rechi wrote:
szMan.Format("%s", xx);

The mistake is there

Format takes variable number of args and so xx would not be converted to char*.

The correct way is

CString szMan;
const char* chxx = xx;
szMan.Format("%s", chxx);

James R. Twine19-Jun-02 8:25

Re: Nope (Was: Re: Retreiving BSTR)

19-Jun-02 8:25

Anonymous wrote:

<br />
CString szMan; <br />
const char* chxx = xx;<br />
szMan.Format("%s", chxx);<br />

That code is attempting to cast a BSTR/_bstr_t to a const char *, which is a no-no.

And, if all you need to so is display the contents of the BSTR as an ASCIIZ string, you can change %s to a %S (uppercase) and it will treat the parameter as a wide string, which is what a BSTR contains:

<br />
// (Typo: "xx" is supposed to be "x", the original BSTR)<br />
// szMan.Format( _T( "%S" ), xx );    // Assuming An ANSI Build Here...  <br />
szMan.Format( _T( "%S" ), x );    // Assuming An ANSI Build Here...  <br />

Peace!

-=- James.
"Some People Know How To Drive, Others Just Know How To Operate A Car."
[Get Check Favorites 1.4 Now!]

Philippe Mori19-Jun-02 9:29

Philippe Mori

19-Jun-02 9:29

This solution suffer from the same problem than the original code that you try to correct...

Conversions operators are not called for function which variables arguments and the whole object is push on the stack.

_bstr_t is not a BSTR. It's an object that contains a pointer to a sub-object that will hold the BSTR and the converted string (if it was asked).

Philippe Mori

Re: Nope (Was: Re: Retreiving BSTR)

James R. Twine19-Jun-02 9:47

19-Jun-02 9:47

> This solution suffer from the same problem than the original
> code that you try to correct...

   If you are referring to my typo, then yes.  If you are saying that I cannot use a BSTR like that, then no.

> Conversions operators are not called for function which variables
> arguments and the whole object is push on the stack

   That is why the format specifiers tell _stprintf/CString::Format(...) how to treat the parameter:

>> szMan.Format( _T( "%S" ), x );

   Under an ANSI build, the "%S" (remember: UPPERCASE) tells CString::Format(...) to treat the passed parameter as a WIDE STRING, which is what x (a BSTR) really is: A BSTR is a specially allocated _wchar_t string with a length value (a DWORD) 4-bytes before the pointer value.

   Peace!

-=- James.
"Some People Know How To Drive, Others Just Know How To Operate A Car."
[Get Check Favorites 1.4 Now!]

James R. Twine19-Jun-02 8:14

19-Jun-02 8:14

Hmmm... I am under the impression that when the temporary bstr_t object is destroyed, it deallocates the BSTR it wrapped...? That would cause the BSTR you return to be invalid. Try looking at the contents (not value) of *pRetval in the debugger right when you get to the delete [] sz line.

You should just be using SysAllocString(...) directly, similar to:

<br />
#include <AFXPriv.h> // -or- <ATLConv.h><br />
<br />
USES_CONVERSION;<br />
<br />
*pRetval = ::SysAllocString( A2CW( sz ) );<br />

Peace!

-=- James.
"Some People Know How To Drive, Others Just Know How To Operate A Car."
[Get Check Favorites 1.4 Now!]

Hans Ruck19-Jun-02 8:31

Hans Ruck

19-Jun-02 8:31

No! The BSTR object is valid. _bstr_t in this case is just attaching itself to the object without handling the memory allocation/deallocation process.
Thanx to both of you for the efforts and time spent.

rechi

James R. Twine19-Jun-02 9:27