www.f-in-box.com

[asdw]

Hello,

can you explain what does the FPCS_ATTACH_TO_PARENT_INTERNAL flag when added to the flash window style?

This helps to forward mouse messages correctly to the flash window (based on the OpenGL sample, but i redraw flash content with GDI+ in my main window), but the main window (and the flash window too) constantly gets WM_MOUSEMOVE messages, without moving the mouse, slowing down the whole app.

If i remove the FPCS_ATTACH_TO_PARENT_INTERNAL flag from the flash window style, no WM_MOUSEMOVEs, but the input behaves oddly (sometimes gets the mouse input, sometimes not).

In the f-in-box header it defines 0x00000008L, but this isn't a standard window flag, isn't it?

Thanks!

[Softanics]

Hello,

We added this flag, yeah...

Actually, we tested idea of attaching flash activex to a window. I don't think that it's great idea to use this flag now as it's not documented.

Thank you.
_________________
Best regards, Artem A. Razin,
F-IN-BOX support
Ask your question here: http://www.f-in-box.com/support.html

[asdw]

Is there (or will be) any solution for this problem?

My app. needs to "redraw" the flash's picture and interacts with it (like the DX/OGL samples, but in 2d, and with interactions). Now I just pass forward the mouse and keyboard events to the flash window, but this is not perfect, as i mentioned in my first post.
After this i managed to get working this in another way (mouse clicks reach the flash window, always) by moving the (hidden) flash window to the coordinate where the mouse event comes from (so the xy coords matches in both window's client area). The problem is that this window moves (happens on mousemove too, not just mouse up/down) slow down the application.

Seems like there is no win-win solution here.

[Softanics]

Hello,

Have you read this topic:
http://www.f-in-box.com/forum/viewtopic.php?t=325

Thank you.
_________________
Best regards, Artem A. Razin,
F-IN-BOX support
Ask your question here: http://www.f-in-box.com/support.html

[asdw]

Yes, i did.
But the solution (or workaround) mentioned there not working here.