C / C++ / MFC

jpyp wrote:

As I stated in my original post, the high word of wParam is 0

jpyp wrote:

I'll investigate the WM_SETFOCUS idea. I don't that is it but you never know.

jpyp wrote:

I have other controls on this dialog that are supposed to be disabled when the dialog opens.

jpyp wrote:

...my handler for that button is called by the framework without any of my code sending a message.

DavidCrow wrote:

While your code may not be doing it directly, a BM_SETCHECK message is being sent to the control, thus the control's handler is doing what it should. If this is undesirable behavior, there's an easy solution.

jpyp wrote:

By easy solution you mean removing the SetCheck(FALSE) call in OnInitDialog()...

void CMyDialog::CMyDialog()
{
    m_bInitializing = true;
}
 
BOOL CMyDialog::OnInitDialog()
{
    CDialog::OnInitDialog();
    ...
    m_bInitializing = false;
    return TRUE;
}
 
void CMyDialog::OnButtonChange()
{
    if (! m_bInitializing)
    {
        // do whatever here
    }
}

jpyp wrote:

the handler is being called after OnInitDialog() completes

led mike wrote:

Read the documentation on the File Formats and implement your own code to obtain the width and height and pixel data

led mike wrote:

Or were you looking for the "Magic" solution?

Mark Salsbery wrote:

why would you give away secrets like that on a public forum

Mark Salsbery wrote:

Now why would you give away secrets like that on a public forum like this??

Moak wrote:

You mean such like SetDIBitsToDevice?

Pavan Tiruveedhula wrote:

without using all those big libraries??