ATL & Windows Media

[TechSupport]

That might make a problem for those of us that capture the X button and block it...unless you return %TRUE from it or something and route everything through WM_CLOSE, or put it in the blocks after the form's CUSTOM.

If you still need to block the "X" you can process the Form's WM_CLOSE message and set Function = 1.

[Roger Garstang]

Cool, so from that I'm guessing you are returning true so it doesn't go further, that way either method of closing only goes through WM_CLOSE?

[Jose Roca]

The problem arises when you terminate the program clicking the x button and %WM_SYSCOMMAND isn't intercepted. It looks like something is bypassed and the OCX isn't destroyed. It doesn't happen when using DDT dialogs. This is not a problem of FireFly, I have noticed it in my tests with OCXs.