WPF 4.5 – Part 8 : No more airspace problems

3 Kicks

submitted by jmix90(570) 8 months ago

Integrating win 32 component is already possible in WPF 4.0, even in WPF 3.5 but there is the well-know issue : airspace problems. Each render technology belongs to only one airspace only. So when you place Win32 components in your WPF application they behave as black hole for input, render transformation are not (well) applied, etc. With this 4.5 release, the WPF team solves this drawback. In this post more explanation and an example of how it improves developers’ life will be gived. This post is a part of a serie on WPF 4.5 new features.

1 comment |category: Windows Presentation Foundation |Views: 60
Tweet

tags: WPF another

Everyones tags:

Your Tags:

Please login or signup.

Add a live kick counter to your blog >> liveImage

You can even customize the image by choosing your own colors, and then clicking the button below to update the preview and the html code:

"Kick It" text
"Kick It" background
kick count text
kick count background
border

Simply copy and paste this HTML into your blog post.

Users who kicked this story:

Craxy(0) -

dpeterson(4397) -

jmix90(570)

Comments:

posted by dpeterson(4397) 7 months, 29 days ago +1

I'd really be interested in learning more about the technical details behind how they accomplished overcoming the impedance between the two rendering systems. It's fantastic that they've made this possible, there are some win32 controls out there that do not have wpf equivalents, and I imagine this is especially true in situations where companies have integrated third party controls into their applications.

Most Active Users

What's this?