Go to the Source Code Page for Latest Version
Minor updates to Thriple are not always bundled up into the download package available on this page. For the latest and greatest code, I suggest you go to the Source Code page for this project (which is available on the navigation bar above).
What's In Thriple v1.0
The first release of Thriple contains two 3D components: ContentControl3D and Panel3D. Each component is accompanied by samples that show their capabilities. There is also the WPF Disciples Blog Roll 3D demo, which uses both components to create a 3D blog roll containing members of the WPF Disciples e-mail group.
Thriple was built and tested in Visual Studio 2008, with Service Pack 1. It runs against the .NET Framework 3.5 with Service Pack 1.
There are currently three known issues related to the 3D components in Thriple, as listed below:
- ContentControl3D can cause a severe memory leak when running on a computer whose video card does not meet the criteria for allowing WPF to perform hardware acceleration. When this control's rotations are rendered in software, as opposed to being hardware accelerated, large amounts of memory is used and never released. Microsoft has verified that this is a defect in WPF, which has already been fixed. The fix will be available in Windows Vista SP2, Windows 7, and as an upcoming patch for Windows XP. If you encounter this memory leak, try updating your video card driver to the latest version.
- If a ContentControl3D is contained in a ScrollViewer, such as the ScrollViewer present in a ListBox by default, and the user navigates to it via the Tab key, an unhandled exception occurs. It appears that this, too, is a WPF defect, and the WPF Team at Microsoft is looking into it. The workaround for this issue is to handle (i.e. 'eat') the Tab keystrokes directed at ScrollViewer. The 'Rotation Direction' and 'Easing Modes' samples in the ContentControl3D_Demo project show how to implement this workaround.
- In certain situations, rotating a ContentControl3D causes a minor memory leak to occur. This leak can be observed in the 'Content Templates' sample in the ContentControl3D_Demo project. I have analyzed this leak for hours but cannot track it down. The WPF Team at Microsoft is investigating this leak, as it very well might be a leak in the platform. There is no known workaround at this time.