|
I can not add more than one button. It builds and compiles OK but the dialog won't show UP, and the program doesn't start at all.
When I have one button its OK, but when I add one more I can't start the program.
Lex
|
|
|
|
|
Recall SetSkin function should be increase the GDI ,why?
|
|
|
|
|
I hope the other endevors were as rewarding. You must be good in anything you do. Thanks for all the contributions.
|
|
|
|
|
i recently building a mfc regular dll using xSkinButton
but if i use a radio button,
when check one radio button ,the other radio buttons can't automatically
uncheck itself,
who knows why this happen?
how to solve the problem?
thanks a lot!
arlerzhang
life is like a pack of chaocolite
|
|
|
|
|
how can add icon in bitmap?
|
|
|
|
|
I found this really useful, and want to use this in my application !
Can I use this in a commercial application? Does the license permit it ?
|
|
|
|
|
Whenever I Use the Mask Bmp the Button Gets Disabled please help me why button gets Disable when I use Mask image.
m_Button_ScanTool2.SetSkin(IDB_CROP_NORMAL,IDB_CROP_PRESSED,IDB_CROP_HOVER,IDB_CROP_PRESSED,0,IDB_MASK,0,0,0);
|
|
|
|
|
I'd like to automatically map appropriate images according to resource ID. What's the easiest way to get nIDCtl from the subclass?
Is it possible to use:
OnDrawItem(UINT nIDCtl, LPDRAWITEMSTRUCT lpDrawItemStruct)
Instead of:
DrawItem(LPDRAWITEMSTRUCT lpDrawItemStruct)
Or, is there another way that I could try?
Thanks!
|
|
|
|
|
My dialog have 10-20 "CxSkinButton" buttons
And some buttons does now draw text!
In debug version - it's ok
But in release - there are no text on the buttons!
Can anyone help me?
ps Compiled with VC++ 6.0, Windows 98 SE
|
|
|
|
|
My dialog have 10-20 "CxSkinButton" buttons
And some buttons does now draw text!
In debug version - it's ok
But in release - there are no text on the buttons!
Can anyone help me?
ps Compiled with VC++ 6.0, Windows 98 SE
|
|
|
|
|
In xSkinButton.cpp, line 311, change the code as follows:
< dcBmp.SelectObject(hBmp);
> HBITMAP hOldBitmap = (HBITMAP)dcBmp.SelectObject(hBmp);
Then add the following line 356 (just before dcBmp.DeleteDC()):
dcBmp.SelectObject( hOldBitmap );
Otherwise, you will be deleting the DC with the bitmap still selected.
Steve
|
|
|
|
|
There are many other places where SelectObject() needs to store the return value and then select the old object before calling DeleteDC(). Here are a few, but it's best if you simply search for all calls to SelectObject() and DeleteDC().
For example, SelectObject() calls near lines 198, 202, and 207 need to be changed so they store the return value. For example:
HBITMAP hOldBitmap1 = (HBITMAP)hdcMem.SelectObject(hBitmap);
Then you need to deselect the old bitmap just before the calls to DeleteDC() (near lines 225, 228, and 243) by adding code similar to:
hdcMem.SelectObject( hOldBitmap1 );
Steve
|
|
|
|
|
There is still at least one other GDI leak in the SetSkin() method assuming that one will set the skin more than once:
Change the the follwing lines in CxSkinButton::SetSkin(...):
SetWindowRgn(m_hClipRgn, TRUE);
SelectClipRgn((HDC) GetDC(),m_hClipRgn);
to:
SetWindowRgn(m_hClipRgn, TRUE);
CDC *pDC = GetDC();
SelectClipRgn(pDC->GetSafeHdc(), m_hClipRgn);
ReleaseDC(pDC);
to ensure, that the DC is properly released.
modified on Friday, December 19, 2008 3:08 AM
|
|
|
|
|
There's IMO a flaw in CxSkinButton::DrawItem method.
If the CxSkinButton object represents e.g. a checkbox with "normal" button text, the text in the pushed/checked state of the button is not displayed properly if the button becomes disabled. That is the position of the checked, disabled button text is wrong.
To fix this change the appropriate section in the DrawItem() method as follows:
// Select the correct skin
if (lpDrawItemStruct->itemState & ODS_DISABLED){ // DISABLED BUTTON
if(m_bDisabled.m_hObject==NULL)
// no skin selected for disabled state -> standard button
pDC->FillSolidRect(&r,GetSysColor(COLOR_BTNFACE));
else // paint the skin
DrawBitmap(pDC,(HBITMAP)m_bDisabled,r,m_DrawMode);
// if needed, draw the standard 3D rectangular border
if (m_Border) pDC->DrawEdge(&r,EDGE_RAISED,BF_RECT);
// paint the etched button text
pDC->SetTextColor(GetSysColor(COLOR_3DHILIGHT));
//Fix: Check if button is in checked/pushed state
if (m_Checked)
OffsetRect(&tr,1,1);
pDC->DrawText(sCaption,&tr,DT_SINGLELINE|DT_VCENTER|DT_CENTER);
pDC->SetTextColor(GetSysColor(COLOR_GRAYTEXT));
//Fix: Remove this line: OffsetRect(&tr,-1,-1);
pDC->DrawText(sCaption,&tr,DT_SINGLELINE|DT_VCENTER|DT_CENTER);
} else { // SELECTED (DOWN) BUTTON
...
|
|
|
|
|
Great class!
I'm working on a user-skinnable application so I need to load the images from files. The way I accomplished this was to replace the UINT's with LPCTSTR's in the SetSkin() parameters and modified the following code:
if (normal>0)
{
HBITMAP hNormal=(HBITMAP)::LoadImage(AfxGetInstanceHandle(),
normal,
IMAGE_BITMAP,
0,
0,
LR_LOADFROMFILE);
m_bNormal.Attach(hNormal);
}
My question is, will this cause any problems, or is there any additional clean-up that I need to be concerned with? I'm fairly new to C++.
Thanks,
Wolf
|
|
|
|
|
WolfSupernova wrote:
Great class!
thanks
WolfSupernova wrote:
will this cause any problems
you must release the bitmaps in the destructor or before you Attach a bitmap over an existing one. With resources this was not necessary
|
|
|
|
|
I want to have the same effect on key board usage.
What I mean is that when you push up-arrow key
the button change the state from normal to mouse over
Thanks
Shin
|
|
|
|
|
|
Hey.
I have a question.
In my program, i want to hide the buttons so they dont' show up in some pages, any of you know how to do that ?
thanks.
|
|
|
|
|
Hi again.
I just figured it out =)
groups.google.com is a good resource as well.
I used the ShowWindow function.
ShowWindow(SW_SHOW);
or
ShowWindow(SW_HIDE);
thanks anyways
|
|
|
|
|
Hey.
I have a question.
In my program, i want to hide the buttons so they dont' show up in some pages, any of you know how to do that ?
thanks.
|
|
|
|
|
I'm currently using the cxSkinButton class and noticed some problems with it under VC++7. It's not a huge deal but kind of annoying. If I create a new project using the wizard and include the manifest the tool tips don't work 100%. They will show up but if I click a button the tool tip for that button doesn't come back. Also, if I hold my mouse over a button until the tool tip goes away it won't come back again either. I'm only able to get the tool tip to come back if I pop up an AfxMessageBox and then close it. If I create another new project without a manifest the tool tips work perfectly. Has anybody else had this problem? I'm not even adding anything into the manifest. It only contains the stuff that VC++ puts in there by default. I could just remove the manifest but then I'd lose the newer interface features like the rounded buttons etc. I guess I could just use the skin control and make them whatever I want anyway but I'd like to find away to make the tool tips work right with the manifest and cxSkinButton.
-scully12
|
|
|
|
|
Hi scully12,
I have the same problem here with the lost tooltips, independent if I use the CxSkinButton class or simply the CButton class. So, CxSkinButton is not the reason why, it seems to be a general problem in VC++7 (the same sources built with VC++6 work perfectly, w/o the manifest, of course).
Did you find any solution in the meantime fro the issue?
Bernd
|
|
|
|
|
Hi Bernd,
I never did find a solution. I ended up just removing the manifest and using it that way. I was hoping that it really was a bug in VC and it would get fixed eventually. It's good to hear that I'm not crazy though.
-scully12
|
|
|
|
|
Hi scully12,
I have the same problem, I add some code at when the button losted focus.
//code :
if ( m_ctrlTooltip.m_hWnd != NULL )
m_ctrlTooltip.Pop();
//code end;
now, my button work fine!
sorry, my english was very pool
|
|
|
|