PatrykDabrowski wrote: I have written "as long as I dont have leaks, I care more about performance:)";)...so my priority is to avoid memory leaks and then I optimize my code. ok for me then :cool: [VisualCalc][Binary Guide][CommDialogs] | [Forums Guidelines]

Since you're essentially dividing pixel RGB values by 25.5 then yes, any values less than 25 are going to end up being 0. There's still something strange - I'm going to try your original code so I can see it. I'll be back. Mark "Great job, team. Head back to base for debriefing and cocktails." (Spottswoode "Team America")

PatrykDabrowski wrote: It means, I have to override WM_PAINT message and blit buttons by myself? yep. but you'd have to do that for a button with any kind of image. you can use icons, which have built-in transparency, if you want to simplify things. but you still have to handle OnPaint. PatrykDabrowski wrote: Is there any way to 'prepare' somehow my bitmaps that Windows could draw them with transparency by its own routines, like it does for non-transparent toolbar buttons??? not with any built-in classes. but, there are dozens of bitmap button classes out there (a few really good ones here on CP). ex. : i like this one. image processing toolkits | batch image processing | blogging

PatrykDabrowski wrote: I was asking how to disable this square "3d-like" frame around my buttons. Image lists do not solve this problem because they are 32x32 pixel and this box is bigger, about 38x38 pixels. The closest I think you'll get is using the TBSTYLE_FLAT style. But you'll still see the hot- track, 3d button outline indication. The buttons are 7 pixels wider and 6 pixels higher than the bitmaps. I tested to see if this could be changed but the system defaulted them. OnEraseBkgnd is fine but the buttons are not drawn transparently. The images on the buttons are. This is the behavior of the toolbar control. The 3d box around buttons indicates to the user that it's a button. You could use the TBSTYLE_CUSTOMERASE style and respond to NM_CUSTOMDRAW messages. In the passed NMTBCUSTOMDRAW struct there's a NMCUSTOMDRAW struct member that you can look at to see if a button is about to be drawn hot and if so, change the state to normal so it gets drawn normally. You could also draw the buttons yourself. It sounds like you may just need to transparently draw images on a background and respond to clicks within the images. Maybe that's a viable alternative route as well(?) Mark

Use LVSCW_AUTOSIZE_USEHEADER for the cx param when you set the size of the LAST column.

PatrykDabrowski wrote: I can't load my 32x32 24-bit bitmaps into it (Visual Studio 2003 resource editor converts them to some ugly-looking 8-colors bitmaps...) When you create the image list for the toolbar control, try building it like this... CBitmap bitmap; bitmap.LoadBitmap(IDB_TOOLBARBITMAP); // (the '2' in the following call is the number of buttons in the bitmap) m_ToolBarImageList.Create(32, 32, ILC_COLOR24|ILC_MASK, 2, 1); // (RGB(0x00,0xFF,0x00) sets the transparent color to bright green) m_ToolBarImageList.Add(&bitmap, RGB(0x00,0xFF,0x00));

Probably because you are statically linking to the C Runtime. There is an option there somewhere to not do that - so that it dynamically links. Jon Humphreys ActivePlanet Software

Use MoveWindow in OnInitDialog(). "Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997 ----- "...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001

PatrykDabrowski wrote: Is it also this case I dont think so. Prasad Notifier using ATL | Operator new[],delete[][^]

PatrykDabrowski wrote: Is it possible with a class derived from CDialog? Can I do some SetMinimiseButtonPos() or SetCloseButtonPos() tricks somehow? And another question about titlebar, is it possible to center titlebar's text? You will have to draw the whole title bar yourself, hide all the buttons and provide all default functionality yourself, See this article[^] mostly applications just hide the title bar and paint a new title bar on the window area itself. If you think you can than you can, if you think you can't you are right.

Thanks! After couple of articles descibing this 'bug' I have successfuly tested this solufion: Instead of using plain SetForegroundWindow()/SetFocus() I use this: //Attach AttachThreadInput(GetWindowThreadProcessId(::GetForegroundWindow(),NULL),GetCurrentThreadId(),TRUE); //Do our stuff SetForegroundWindow(); SetFocus(); //Just playing safe //Detach the attached thread AttachThreadInput(GetWindowThreadProcessId(::GetForegroundWindow(),NULL),GetCurrentThreadId(),FALSE); ...and it's working fine! (on winXP)

PatrykDabrowski wrote: PostThreadMessage(m_appthreadid,WM_APP+1,0,0); instead of using the WM_APP+1, use RegisterWindowMessage to create a unique message. nave

Use spy++ utility and check the message(s) when double-clicking My computer icon. Me I think the message is for the SHELLDLL_DefView/SysListView32 classes that displays the icons, and not for #32769 desktop window.