Mouseover event

Hmm... To be sure we are talking about the same thing...

You have 2 Picture Controls on your main dialog?
The Picture Controls are set to tyoe Bitmap, and the Image property is set to a bitmap resource? (You can see the image in the Picture Control on the dialog in the dialog editor?)

In my example code, the resource ID's for the Picture Controls, are IDC_STATIC1 and IDC_STATIC2, you would change your code (where you get the HWND for the picture control) to use the resource ID's you assigned for the picture control (I assume they are IDC_NORMAL and IDC_HIGHLIGHT).

Make sure you do not comment out or remove any of the original code (except for the LoadBitmap lines). You still need to send the BM_SETIMAGE message to the buttons in WM_INITDIALOG, to set the initial image property for your buttons. This should be done after you use STM_GETIMAGE to get the handle of the bitmaps from the picture control's. (again the code should be exactly the same as it was previously except you replace the LoadBitmap lines with the above code, the rest of the code should not change and should be in the same order, etc).

I modified the previous sample to use Picture Controls, and STM_GETIMAGE as you requested and re-attached it. (scroll up and you will see that it is now sample4.zip).

I tried modifing my bitmaps so that they are true color bitmaps using gradient colors with a actual unique color count of approx. 461 colors. I tried using LoadBitmap, and using Picture Controls, and had no problems using either method. The pictures displayed properly in both cases, so I am not sure why you might be having a problem with your bitmaps. One possibility might be the size of your pictures. BM_SETIMAGE, centers the bitmap on the button by default, and if the image is to large to fit within the button, it is clipped on either side. As for the picture being grey, I would assume that either the button is disabled, or the bitmap handle is invalid (the picture control may not have a bitmap set, or the STM_GETIMAGE message was sent to wrong window (maybe the HWND is invalid, check the lines that get the HWND for the Picture Control's and verify that the correct Resource ID's of the Picture Control's are used (case sensative), and that the correct HWND for the parent dialog is used, also make sure that that the variable that you are using to store the bitmap handles is global, otherwise it will go out of scope when WM_INITDIALOG returns, and thus the handle will be invalid when it is used in WM_MOUSEMOVE)

I set the button (in your case is IDC_DLGBTN1 and IDC_DLGBTN2) to be "Owners Draw" and "Bitmap". "Owners Draw" is the one who make the grey area that I mentioned.

I want the button to be owners draw, so that I don't need to see the button shape there.

In your sample, when click IDC_DLGBTN1, child dialog will open, and if move the mouse away, it will back to IDC_NORMAL. How to make it stay at IDC_HIGHLIGHT eventhough the mouse is move away, since that the child dialog is still open.

and when close that child dialog, it will back to IDC_NORMAL.

Thanks.

another thing (with regard to my previous post), I only want to see the swapping between IDC_NORMAL and IDC_HIGHLIGHT without the button being visible. The BUtton should be OWNER DRAW and BITMAP.

Quote:

---

Originally posted by Dimension
I set the button (in your case is IDC_DLGBTN1 and IDC_DLGBTN2) to be "Owners Draw" and "Bitmap". "Owners Draw" is the one who make the grey area that I mentioned.

I want the button to be owners draw, so that I don't need to see the button shape there.

---

Owner drawn means that you have to draw the button yourself.
You would need to handle the WM_DRAWITEM message and actually draw the button yourself. There are plenty of example out there for owner drawn buttons that you can refer too (look on the Codeguru and CodeProject sites).

Quote:

---

Originally posted by Dimension
In your sample, when click IDC_DLGBTN1, child dialog will open, and if move the mouse away, it will back to IDC_NORMAL. How to make it stay at IDC_HIGHLIGHT eventhough the mouse is move away, since that the child dialog is still open.

and when close that child dialog, it will back to IDC_NORMAL.

Thanks.

---

Ok, this is completely different. To do this, you would probably check to see if the child dialog is visible in WM_MOUSEMOVE and WM_MOUSELEAVE, and only change the bitmap if the dialog is not visible. Then in the "OK" button handler for the child dialog, set the bitmap back to the normal one.

BTW: If you do not want the 3D button look, why not just use flat buttons?

OK. if I don't want to involve the button, and I would just place IDC_NORMAL and IDC_HIGHLIGHT as visible in Same Position. then the mouseover only dealing with IDC_NORMAL and IDC_HIGHLIGHT with SW_SHOW and SW_HIDE. Is that possible ?

When you hide the window, I would assume the would trigger a WM_MOUSELEAVE message which might cause problems with that scanario, you could however just use the picture controls, instead of the buttons as you want, and change the picture in the picture controls when the mouse is over it, etc (instead of hiding and showing, just change the bitmap same way that was done with the button).

RussG1, it would be nice if you re-post the sample project with this approach. Sorry to trouble you.

Example will make thing easier.. Many thanks.

Allright, I made all the changes that I think you want:

Removed buttons and replaced them with Picture Controls.
(note that I added the "Notify" style to the Picture Controls so that we can receive the WM_MOUSEMOVE/WM_MOUSELEAVE messages for the control).

Changed button subclassing code to subclass the picture control's instead.
Enabled mouseover action for the picture controls (bitmap changes when mouse is over the picture control).
Modified MouseOver and OnClick handlers for the Picture Controls so that if the child dialog is visible the picture does not go back to it's normal state until the child dialog is hidden (in the OnOk handler for the child dialog), etc.

The sample is attached as before and is now sample5.zip.
Hopefully this is what you are looking for.

Thanks RussG1. It works fine for me. Thanks.

One more question, How can I put a tooltips on those picture control (e.g IDC_STATIC1) ?

Baiscally you create a Tooltip Control window and add tools for each picture control. You add the TME_HOVER flag to the TRACKMOUSEEVENT structure so that we are sent WM_MOUSEHOVER messages in addition to the WM_MOUSELEAVE message. You would need to keep track of when the tip is visible, using a global boolean variable.

In WM_MOUSEHOVER, set boolean variable to TRUE, and send a message to the tooltip control to tell it to show the tooltip associtaed with that window.
In WM_MOUSELEAVE, check the value of the boolean var, if it is true, set it to false, and send a message to the tooltip control to tell it to hide the tip, etc.

This is a bit harder to explain so I just modified the example (now sample6.zip) and added tooltips.

The tooltip is shown when the mouse hovers over either of the picture control's (and hidden when the mouse leaves the pic controls window). I used a callback to set the tooltip text for each picture control. You can modify the text in the TTN_GETDISPINFO handler (in the WM_NOTIFY handler) of the picture control's window procedure.

Cool. Thanks.
I have One last question.
If I can change cursor to Hand Cursor, when mouseover, how can I achieve that ?

Assuming I have hand icon (IDI_HAND) under my resource.