C / C++ / MFC

Re: Simple Question on Button and Sound

13-Feb-05 10:26

Use the PlaySound() function specifying the SND_LOOP flag.

"You're obviously a superstar." - Christian Graus about me - 12 Feb '03

"Obviously ??? You're definitely a superstar!!!" mYkel - 21 Jun '04

Within you lies the power for good - Use it!

Honoured as one of The Most Helpful Members of 2004

normanS13-Feb-05 23:10

normanS

13-Feb-05 23:10

That's only half the answer.

The original question also said that the sound was only played when the button was released. How do we detect that the button was pressed, as opposed to when the button is released?

WM_KILLFOCUS / WM_SETFOCUS

PJ Arends13-Feb-05 10:17

13-Feb-05 10:17

I have a form with Chris Maunder's MFCGrid and some buttons. My problem is when the user is editing something on the grid he would be using an edit control that destroys itself in it's WM_KILLFOCUS handler

CInPlaceEdit::OnKillFocus(CWnd *pNewWnd)
{
    ...
    SendMessage(WM_CLOSE, 0, 0);
}

My problem is that when one of the buttons recieves the input focus it has to know the HWND of the control that lost the focus

COneClickButton::OnSetFocus(CWnd *pOldWnd)
{
    CButton::OnSetFocus(pOldWnd);
 
    HWND old = pOldWnd->GetSafeHwnd();

So far all my testing seems to indicate that the GetSafeHwnd() function is returning the correct HWND, but can I be sure that it always will or am I better off changing the SendMessage(WM_CLOSE) to a PostMessage(WM_CLOSE) in the CInPlaceEdit class?

"You're obviously a superstar." - Christian Graus about me - 12 Feb '03

"Obviously ??? You're definitely a superstar!!!" mYkel - 21 Jun '04

Within you lies the power for good - Use it!

Honoured as one of The Most Helpful Members of 2004

Ryan Binns13-Feb-05 17:14

Ryan Binns

13-Feb-05 17:14

Using SendMessage() won't cause any problems because closing a window is treated as a focus-changing event, and therefore the window that is to receive the focus will receive a WM_SETFOCUS during the SendMessage() call before the window is destroyed.

At least, that's how I recall it happening... Unsure | :~

Ryan

"Punctuality is only a virtue for those who aren't smart enough to think of good excuses for being late" John Nichol "Point Of Impact"

PJ Arends14-Feb-05 9:30

14-Feb-05 9:30

Unfortunately that does not seem to be the case. I tried it by placing some TRACE statements in the code on either side of the SendMessage(WM_CLOSE) and in the OnSetFocus() handler. It seems that SendMessage(WM_CLOSE) returns before the WM_SETFOCUS message is handled by the button.

I guess for now I will leave the code as I have it, just leaving a note about my suspicions in case I get any complaints about stange behaviour later on Unsure | :~

"You're obviously a superstar." - Christian Graus about me - 12 Feb '03

"Obviously ??? You're definitely a superstar!!!" mYkel - 21 Jun '04

Within you lies the power for good - Use it!

Honoured as one of The Most Helpful Members of 2004

Ryan Binns14-Feb-05 12:15

Ryan Binns

14-Feb-05 12:15

Hmmmmm... ok. Does the WM_CLOSE handler for the window actually destroy the window, or does it post a WM_DESTROY message or something similar, ie. Has the window been destroyed in the WM_SETFOCUS handler (use IsWindow() to check the HWND).

Ryan

"Punctuality is only a virtue for those who aren't smart enough to think of good excuses for being late" John Nichol "Point Of Impact"

PJ Arends14-Feb-05 20:56

14-Feb-05 20:56

GetSafeHwnd() returns the HWND I am looking for, but IsWindow() returns FALSE. So that tells me the window was destroyed.

What I am now thinking is that the CWnd passed to OnSetFocus is a CTempWnd class, so that would mean that it is just a copy of the CWnd of the CInPlaceEdit class that was destroyed. Being a copy it contains the same m_hWnd value as the original even though the original has already been destroyed and deleted.

It all makes sense to me now. Thanks for the push in the right direction so that I could figure out what was going on Big Grin | :-D

"You're obviously a superstar." - Christian Graus about me - 12 Feb '03

"Obviously ??? You're definitely a superstar!!!" mYkel - 21 Jun '04

Within you lies the power for good - Use it!

Honoured as one of The Most Helpful Members of 2004

AnimateWindow & OnPaint problem

Ryan Binns14-Feb-05 22:57

Ryan Binns

14-Feb-05 22:57

PJ Arends wrote:
What I am now thinking is that the CWnd passed to OnSetFocus is a CTempWnd class, so that would mean that it is just a copy of the CWnd of the CInPlaceEdit class that was destroyed. Being a copy it contains the same m_hWnd value as the original even though the original has already been destroyed and deleted.

AFAIK, That's not quite how CTempWnd works. If the window was an MFC window, and has not been deleted, then you will always get a pointer to the actual window class. If the window has been destroyed (or is not an MFC window), then you'll get a pointer to a CTempWnd. I think what's happening is that Windows is passing the HWND of the destroyed window to the WM_SETFOCUS handler, intending it purely for information, and MFC is creating a CTempWnd object to map it to, because the window has already been destroyed.

PJ Arends wrote:
Thanks for the push in the right direction so that I could figure out what was going on

Glad to be of help Smile | :)

At least it's enlightened me as well Smile | :)

Ryan

"Punctuality is only a virtue for those who aren't smart enough to think of good excuses for being late" John Nichol "Point Of Impact"

Anonymous13-Feb-05 8:49

Anonymous

13-Feb-05 8:49

Hi,
I'v got a problem trying to draw on DC of a dialog while using animatewindow(....AW_BLEND)
My drawings does NOT appear until I call Invalidate() manually!

So what happends is that an empty dialog Fades In and then all drawings suddenly appears.
It's so ugly!

However, I found a solution that I did not understand(!):

OnPrint(WPARAM wParam, LPARAM lParam)
{
CDC* pDC = CDC::FromHandle((HDC)wParam);

if ( lParam & PRF_NONCLIENT )

Do some drawings...

return 0;
}

[Author Mr. Shog9] did the following in a window(CWnd)

2 things:

1-It's difficult to understand, why a dialog box may have OnPrint Message[ consider the fact that I'm a beginner ]?!! Confused | :confused:

2-While Fading out, the code (some times) frozens the application
as Mr. 'richard sancenot' mentiond at the end of that article (Title:Balloon Help as a non-modal replacement for MessageBox())

Could any one Help me please?
Even if there is any article previously, would you tell me please.
I thank you in advanced.
Best regurds, Hamed.M
p.s.Excuse me if my english is not well.

run-time dll linking - getting a variable

Kuniva13-Feb-05 8:18

Kuniva

13-Feb-05 8:18

Hi, my scenario is like this:

I link a dll at run-time by calling LoadLibrary() and then I call GetProcAddress to get the location of a function within that DLL so i can call it. This works fine. But now I wanted to get the location of a variable, and address that, but it doesn't work. In my DLL I have a declaration as follows:

extern "C" { char * szLogFile = "C:\\log.txt"; }

So I try to address the variable from my program as follows:

char * test = (char*)GetProcAddress(hinstDLL, "szLogFile");

But when I then try to show the variable test using a messagebox I just get garbage so the pointer must be wrong.

Any ideas whats wrong?

Kuniva
--------------------------------------------

Re: run-time dll linking - getting a variable

Neville Franks13-Feb-05 9:43

Neville Franks

13-Feb-05 9:43

I've seen this same problem. I can't recall why now. I suggest you add a set/get function to the DLL and use that to access the variable instead. BTW global variables are evil.

Neville Franks, Author of ED for Windows www.getsoft.com and Surfulater www.surfulater.com "Save what you Surf"

Re: run-time dll linking - getting a variable

Kuniva13-Feb-05 12:40

Kuniva

13-Feb-05 12:40

Heh, damn, I was kinda hoping for an explanation, I hate having to have to avoid the problem. But I guess I don't have much choice so thank you for your reply anyway.

And as for the global variables are evil thing, so they keep telling me.. I don't see any reason why they should be evil in very small programs though :P
And generally I believe it to be said by people who can't make sense of their own programs after a while Wink | ;)

Also, no stack operations means more speed, weee.

So, in short, global variables are evil, but fun!

lol.. just messing.

Kuniva
--------------------------------------------

UDP sockets -> select() not working .. Please HELP!

Member 172877313-Feb-05 7:51

Member 1728773

13-Feb-05 7:51

Hi,

If someone has the answer to this I will be most greatful. I cannot get the select() function to work here. My program successfully sends the message and the server responds to this message(I have seen the results on ethereal). What I am trying to accomplish is send out a UDP message(the one defined by RequestStatMsg(which is properly formatted and correct and works fine)), then use the select function as shown below to simply listen for a reply for one second, and log if there is a reply, then repeat. The idea is to test a device to see if it responds to this UDP status request message promptly, and to log failures...testing over long durations(days). This is driving me mad. Thank you for any input you may provide!!

CODE

//Global

typedef struct{
unsigned short MsgID; /* REQUEST_STAT_MSG (0x00) */
unsigned short MsgSize; /* Bytes in this message */
}RequestStatMsg;

SOCKADDR_IN remote; // For client
SOCKET sock; // For client
SOCKADDR_IN RecvAddr; // "server usage on PC side"
SOCKET RecvSocket; // for recieving the Stat request message

struct timeval stTimeOut; // Create the timestruct for the

fd_set stReadFDS; // Set the file descriptors
fd_set stXcptFDS;
.
.
.
// everything else isinside <int cjtf_appdlg::onsend()="">
sock = socket(AF_INET, SOCK_DGRAM, IPPROTO_UDP);
RecvSocket = socket(AF_INET, SOCK_DGRAM,IPPROTO_UDP);
.
.
.
while(true)
{
// the sendto works fine
sendto(sock, (char *)&ReqStatMsg,sizeof(ReqStatMsg),
0,(SOCKADDR *)&remote, sizeof(SOCKADDR));

StatMsgSent++;
TempStr.Format("%d", StatMsgSent);
m_MsgSentCnt.SetWindowText(TempStr);

stTimeOut.tv_sec= 1; // 1 sec timeout
stTimeOut.tv_usec=0; // use for milliseconds

// Bind the socket to RED SIDE and the specified port.
RecvAddr.sin_family = AF_INET;
RecvAddr.sin_port = htons(prt); //
RecvAddr.sin_addr.s_addr = inet_addr(IPAddrStr);

bind(RecvSocket, (SOCKADDR *) &RecvAddr,
sizeof(RecvAddr));

// Prep the members
FD_ZERO(&stReadFDS);
FD_ZERO(&stXcptFDS);
FD_SET(RecvSocket, &stReadFDS);
FD_SET(RecvSocket, &stXcptFDS);

// set up to for 1 second
retvalue = select(0,&stReadFDS, NULL, NULL, &stTimeOut);

// handle the case that no message is available
through(timeout 1sec)
// else receive the message
recvfrom(RecvSocket,RecvBuf,BufLen, 0,(SOCKADDR*)
&SenderAddr, &SenderAddrSize);

// This ALWAYS times out after one second, but I know the response is coming back(ethereal). The server simply responds to the clients ip address and port that it sent from. I'm not getting it though???
Thank you in advance for your help!

Rich

Getting size of file?

Moochie513-Feb-05 7:48

Moochie5

13-Feb-05 7:48

I am opening and reading from a text file and am trying to figure out the function to get the size of the file.

Windows reports the file as being 33KB, and I want my program to be able to report that as well.

Appreciate the help.

Ravi Bhavnani13-Feb-05 8:29

Ravi Bhavnani

13-Feb-05 8:29

CFile::GetStatus()

/ravi

My new year's resolution: 2048 x 1536
Home | Articles | Freeware | Music
ravib@ravib.com

Neville Franks13-Feb-05 9:38

Neville Franks

13-Feb-05 9:38

Or lseek() to end of the file or ftell() for the old fashioned streams.

Neville Franks, Author of ED for Windows www.getsoft.com and Surfulater www.surfulater.com "Save what you Surf"

David Crow14-Feb-05 3:51

David Crow

14-Feb-05 3:51

GetFileSize() comes to mind.

"Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow