Try changing the Dots per inch to 120
then see how your buttons look. They do not automatically
scale to the correct size as the system buttons do.
If you goto properties on your desktop
then select advanced and set to larger font
120 DPI (dots per inch) you will notice that your
buttons will be noticably smaller as they do not
scale correctly as the system buttons do.
Todays laptops are coming set at these higher DPI
I have a small problem using SetMenu. Everything works fine,
menu is displayed, actions can be performed, but when I add a toolbar, the menu looks like before, no icons there (BCMenu support is enabled, of course). I tried it exactly like in the example even with the same toolbar, but it doesn't work! Whats going wrong???
I don't know if I'm doing something wrong. I've downloaded the demo-project and buil it in all the 4 versions (debug, release, debug UNICODE, and release UNICODE). The only version that does excute without a crash is the debug version!
My compiler is that of Visual C++ 6.0.
Someone does know what is happening? I use the CButtonST class for a small project I'm currently in, and I'm experimenting this problem. My debug version works fine, but the release version crashes inmediatly. I have to explain this a little: In release mode, I execute the program, and wait til the application has been loaded. The moment y touch any key or move or click the mouse, the program crashes with some strange error (Unhandled exception in MFC42.dll - Acces Violation 0x000000005). I have been able to discover that the problem resides in the message-loop driven by the application. In fact it is the FilterToolTipMessage() that causes the exception.
The following line can not be executed:
CWnd* pWnd = CWnd::FromHandle(pMsg->hwnd);
I think the handle is to a window of a button created with the CButtonST class, and somehow it has an invalid value!
If someone (perhaps the great author of the class!) couls explain me what's happening, I would be very pleased!