Forum

Hi Sergiy,
next problem ;-)

CExtStatusControlbar::OnPaint() line 136ff

The border of the last indicator is too small. I couldn’t figure out why. O.k. all of your samples work fine, may be my App is too complex ;-)
I compared my app with yours and didn’t find major differences ;-) My app is wizard-generated (and sometimes chaotic)...

But I didn’t change the sizes of any indicator but the first (I hope). If I didn’t change the first width, even so the error occurs.

I fixed the problem (for me) by testing the size of the last indicator and correct it, if it is too small:
CRect rcClient;
  GetClientRect ( & rcClient );
  rcClient.right -= ::GetSystemMetrics( SM_CXVSCROLL ) + 2;
  dc.SelectStockObject( NULL_BRUSH );
INT nItem = m_bOuterRectInFirstBand ? 0 : 1;
  for( ; nItem < m_nCount; nItem++ )
  {
    CRect rc;
    GetItemRect( nItem, rc );
    if ( nItem == m_nCount -1 && rc.right != rcClient.right )
      rc.right = rcClient.right;
    CExtPaintManager::PAINTCONTROLBARBORDERSDATA _pcbbd(
      this,
      CExtPaintManager::__CB_INNER_STATUSBAR_ITEM,
      0,
      rc
      );
    g_PaintManager->PaintControlBarBorders( dc, _pcbbd );
  } // for( ; nItem < m_nCount; nItem++ )

Any idea, where I have to search ?

please do not spent to much time for this problem. I will be able to adjust the next version of the ProfUIS too ;-)

ExScrollWnd
shuld I use CExScrollWnd-Class instead of CScrollView ? I didn’d find the class in the samples (I didn’t view not all of them ;-)...

Some Problems araise in the Bitmap-Editor too ;-( If you load big BMPs (like me, my png’s are at least 130MB and the coresponding bmp’s are at least 150MB) the app slows down ;-) I tested your bmp-classes but they are of no use for me because of the big overhead.

All other classes I used are very usefull ! Your lib is a big assistance to me

kind regards, stefan.

Dear Stefan,

The status bar problem is interesting. Please let me take a look at the status bar’s initialization code (may be in CMainFrame::OnCreate()). I hope to find the answer in the structure of your status bar bands.

The CExtScrollWnd class was designed as a parent class for CExtImageEditWnd, CExtColorPaletteWnd and future library controls which will need the scrolling feature. Its design is not finished and we didn’t make documentation and/or samples for it yet. Future version of CExtScrollWnd may optionally replace scrollbar-like areas with pager-control like buttons but I will not promise this feature now. Unlike CScrollView it works with MM_TEXT mapping mode only (see MSDN library help for SetMapMode()) and with build-in scrollbar-like parts of the non-client window area. The CExtScrollWnd class is a simplified version of the CScrollView class with a set of virtual methods which are more convenient for coding custom controls.

I agree with you about slow effects with 100 MB images but I should note image editor is not a replacement for Corel Photo Paint / Adobe Photo Shop. The main idea was to provide bitmap editor for UI items like toolbar/menu images which are usually much less than 1 MB :-) Image editor does not support virtual uploading mode for the parts of extremely large images.

Best regards, Sergiy.