Stopping flicker during updates

When making major changes to a list control (and other controls) it is a good idea to turn off updating of the control. To do this you would use SetRedraw(false) at the start of the change and SetRedraw(true) at the end, and then invalidate the control.

However, SetRedraw simply turns redraw on or off, it does not let you know whether or not redraw was on or off before the call. And there is no function that can tell you this.

For this reason, I have my own SetRedraw function that counts the number of times you have turned it on and turned it off.

Define a member variable:
     int m_redrawcount;

In your contructor do:

     m_redrawcount = 0;

And then define the following function (in this case for a list control):

void CMyListCtrl::SetRedraw( BOOL bRedraw) {
     if (! bRedraw) {
          if (m_redrawcount++ <= 0) {
               CListCtrl::SetRedraw(false);
          }
     } else {
          if (--m_redrawcount <= 0) {
               CListCtrl::SetRedraw(true);
               m_redrawcount = 0;
               Invalidate();
          }
     }
}

The first time you turn redraw off, the real SetRedraw function is called to turn redrawing off. Subsequently the function increases a counter when you requested redraw be turned off, and decreases it when you request redraw to be turned on again. When the counter gets back down to zero, the real SetRedraw function is called to turn redrawing back on again and the control is invalidated (so that redrawing actually takes place).

This means you can not put SetRedraw(false) at the start of, and SetRedraw(true) and the end of, any function that makes large changes to the lsit control (like loading, sorting, changing with column widths or order etc).



Comments

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

Top White Papers and Webcasts

  • Live Event Date: September 10, 2014 @ 11:00 a.m. ET / 8:00 a.m. PT Modern mobile applications connect systems-of-engagement (mobile apps) with systems-of-record (traditional IT) to deliver new and innovative business value. But the lifecycle for development of mobile apps is also new and different. Emerging trends in mobile development call for faster delivery of incremental features, coupled with feedback from the users of the app "in the wild". This loop of continuous delivery and continuous feedback is …

  • Packaged application development teams frequently operate with limited testing environments due to time and labor constraints. By virtualizing the entire application stack, packaged application development teams can deliver business results faster, at higher quality, and with lower risk.

Most Popular Programming Stories

More for Developers

Latest Developer Headlines

RSS Feeds