WPF input Interop over DirectX Airspace

re: WPF input Interop over DirectX Airspace

jamiebriant — Wed, 13 Feb 2008 22:27:40 GMT

On my x64 system, it leaks memory like a sieve. Appears to be down in the unmanaged WPF code - managed memory is steady at 2mb. Haven't tried it on a 32bit system. Any ideas?

re: WPF input Interop over DirectX Airspace

pantal — Thu, 14 Feb 2008 08:51:19 GMT

Hmm. Could you email(from the email link on side) me with details/repro on the 64 bit issue you are investigating?

Thanks!

re: WPF input Interop over DirectX Airspace

pantal — Wed, 20 Feb 2008 07:33:47 GMT

I was able to repro the issue Jamie described. The app was erroneoously creating a shader object each render cycle, without explicitly disposing previous due to a caching logic bug.

BTW: In theory, the unmanaged shader resources should eventually get released when the managed objects are disposed via GC, but there is also an explicit api for release of the unmanaged resources.

In ShaderRenderer.cs, Line 34 replace:

reloadTexture = false;

with:

reloadShader = false;

re: WPF input Interop over DirectX Airspace

OverMalo — Tue, 15 Jul 2008 15:55:14 GMT

Hi.

Can i use this form to put WPF Button, WPF Windows or some WPF controls over directx surface... ¿?.

Thanks you.

re: WPF input Interop over DirectX Airspace

chrisk414 — Thu, 05 Nov 2009 22:31:40 GMT

I really appreciate for your post, it's exactly what I'm looking for, however, why does .xaml won't display correctly in "Design" view in VS?

It says below...

A window parent could not be found for MS.Internal.Designer.DesignerPane+ContentRoot

at WpfNuggets.ManagedDirectX.AirspaceOverlay.GetParentWindow(DependencyObject o) in D:\wpf\WPF DX Interop\ManagedDirectXContainer\AirspaceOverlay.cs:line 109

Any help would be appreciated.

Thank you very much.