Simple Bitmap Buttons


Desktop-as-a-Service Designed for Any Cloud ? Nutanix Frame

This is an easy and flexible way to use bitmaps as buttons in your application, however it has its limitations. It is based on CStatic class and its SetBitmap member function.

I did it this way:

  1. Step: Define button states (for instance: default, highlighted, pressed) and draw the bitmap for each state.
  2. Step: Derive a class from CStatic, let's call it CBmpButton.
  3. Step: Add CStatic controls to your dialog template and associate member variable to them. The type of the variables should be CBmpButton.
  4. Step: Add a CBitmap member variable to the CBmpButton class for each button state. Like this:
      CBitmap m_default;     // normal state
      CBitmap m_highlighted; // the mouse is moving over it
      CBitmap m_pressed;     // the button is pressed
  5. Step: Add an initialization function to the class, which will load the bitmaps (from the resource or from file):
    BOOL CBmpButton::LoadButtonBitmaps( int idDefault, 
                                        int idHighlighted, 
                                        int idPressed)
      BOOL retVal = TRUE;
      retVal &= m_bmpDefault.LoadBitmap(idDefault);
      if (idUp < 0) m_highlighted.LoadBitmap(idDefault);
      else retVal &= m_highlighted.LoadBitmap(idHighlighted);
      if (idDown < 0) m_pressed.LoadBitmap(idDefault);
      else retVal &= m_pressed.LoadBitmap(idPressed);
      return retVal;
  6. Step: Catch windows messages you want to react to (WM_MOUSEMOVE, WM_LBUTTONDOWN, WM_LBUTTONUP) and change the bitmap for each one:
    void CBmpButton::OnLButtonDown( UINT nFlags, 
                                         CPoint point)
      // TODO: Add your message handler code here 
      //       and/or call default
    CStatic::OnLButtonDown(nFlags, point); } void CBmpButton::OnLButtonUp(UINT nFlags, CPoint point) { // TODO: Add your message handler code here // and/or call default SetBitmap(HBITMAP(m_bmpUp)); CStatic::OnLButtonUp(nFlags, point); }


  7. Step: I needed another function to reset the button - to restore the default state, after the mouse left the area ( SetBitmap(HBITMAP(m_bmpDefault)) ); This function is called from the parent dialog member function OnMouseMove

And that's all...

Problem: I didn't managed to persuade the bitmaps to clean themselves from the memory--only when the application exits. If you use this method on popup dialogs in a SDI or MDI application it can cause memory overflow.

In my demo project I used the code of David Gallardo Llopis, downloaded from CodeGuru to make a Bitmap Dialog.


Download demo project - 47 Kb


  • free resources

    Posted by brigante on 04/30/2009 05:55pm


  • good

    Posted by eidolon on 12/14/2005 01:29pm


  • one problem

    Posted by Legacy on 11/06/2002 08:00am

    Originally posted by: Kevin Smith

    This is really great, thankyou.
    I am having a minor problem.

    I have integrated your class into my program. But when I left-click on one of my buttons, I cannot hold the button down... as soon as I left-click the button, it performs the BN_CLICKED for the button.

    This should be happening when I release the left-click, what am I doing wrong?

  • error!!

    Posted by Legacy on 06/11/2002 07:00am

    Originally posted by: young

    BmpButs.rc(20) : fatal error RC4214: Codepage not valid:  ignored
    Error executing rc.exe.


    Please answer..

  • flaw with unhighlighting buttons

    Posted by Legacy on 06/03/2002 07:00am

    Originally posted by: Michael Yee

    There is a flaw in the way you are unhightlighting buttons (via trapping WM_MOUSEMOVE messages). For example, if you place the buttons together such that there is little or no gap between them, or if you place a button near the edge of the dialog.

    In such cases, the dialog may not receive a WM_MOUSEMOVE message and one or more buttons can remain highlighted.

    A solution I found is to use mouse capturing instead of trapping WM_MOUSEMOVE.

    *Added June 03, 2002*

    I found a small bug with using mouse capturing (which I could not fix). Hence, I found a cleaner solution, which is to use TrackMouseEvent and trapping WM_MOUSELEAVE. This works great so far!

    - Michael Yee

  • thank's your code

    Posted by Legacy on 05/23/2002 07:00am

    Originally posted by: lee

    This is very useful for me..

  • A Question!

    Posted by Legacy on 04/04/2002 08:00am

    Originally posted by: Hidy

    It's a very good sample!
    I want to ask what's the use of function shown below
    void CBmpButsDlg::OnLButtonDown(UINT nFlags, CPoint point)
    // TODO: Add your message handler code here and/or call default
    CDialog::OnLButtonDown(nFlags, point);
    PostMessage( WM_NCLBUTTONDOWN, HTCAPTION, MAKELPARAM( point.x, point.y));

    If I put "//" before "PostMessage(......)", I got the same
    result after I run it. why?
    What is the function of Message of WM_NCLBUTTONDOWN?


  • Very nice sample

    Posted by Legacy on 01/23/2002 08:00am

    Originally posted by: Petr Havlicek

    Very nice sample, thanks for a good job!

  • Easy to understand and implement

    Posted by Legacy on 01/22/2002 08:00am

    Originally posted by: Franz

    You 've done a great job!

  • Cool

    Posted by Legacy on 01/20/2002 08:00am

    Originally posted by: Zoltan Nagy

    This is a cool Application.

  • Loading, Please Wait ...

  • You must have javascript enabled in order to post comments.

Leave a Comment
  • Your email address will not be published. All fields are required.

Most Popular Programming Stories

More for Developers

RSS Feeds

Thanks for your registration, follow us on our social networks to keep up-to-date