kl422

Looking at a recent tutorial on mixing WPF and DX, an example of compositing
wpf/dx overlapped areas contains code which requests the parent window. In
Blend 2 this is interpreted to mean that Blend itself is the parent window
and the code for this causes blend to constantly execute this code,
preventing mouse clicks/mouse over from registering with Blend at all,
although keyboard shortcuts continue to work. Is there a known way to resolve
this type of issue? From my personal standpoint as a developer, code running
in a 'sandbox' environment should never 'break in' to the running application
itself. This particular case is only an example, but I fear worse could occur
with more complicated routines. This issue occurs both on XP32 and Vista64.