Dec CTP

Hi all,

I have installed Dec CTP and the good news is that it seems
there are no changes in the API - all of my programs recompiled without any
problem.

The bad news is that the problems that I had with Nov CTP are present in Dec
CTP too.
I am going to relist them:

1. Camera transform affects hit test results: If the camera transform is not
the identity, the hit test results are "distorted". It seems that the
transform is not taken into account when converting the 2D hit point into the
3D ray.

2. Trying to animate a property of a ModelVisual3D I get "Multi-step
property paths may not be specified on an
object of type 'System.Windows.Media.Media3D.ModelVisual3D'". The same with
GeometryModel3D.
The workaround was to go up on the tree and use a FrameworkElement (usually
the Viewport3D) as the target name.
But because I have some ModelVisual3Ds as the Children of another
ModelVisual3D I cannot build the path - there is no dependency property
(ChildrenProperty) for ModelVisual3D.

3. I have some custom controls derived from Canvas. These controls are
dinamically added in code and have to be animated
using storyboards.
I register their name using
Application.Current.MainWindow.RegisterName(myControl.Name, myControl);
but I still get the error "The name 'myControlName' could not be resolved in
the name scope of 'MS.Internal.AppModel.RootBrowserWindow'"
It's like the name is not registered at all, I have tried to register the
name at different levels (Grid etc.) but to no avail.

4. I have a list of custom objects to be presented as 3D objects in a
listbox. I am using DataTemplate for this task and in the Triggers section I
start an animation on mouse over. The error I get on mouse over is "The value
of property 'Transform' in the path '(0).[0].(1).[1].(2).(3).(4)' points an
immutable instance of
'System.Windows.Media.Media3D.RotateTransform3D' which may not be
manipulated.". I understand this is a known bug,
but I was hoping to be fixed in Dec CTP.

5. Superscript not working (see a previous thread).

Thank you,
Valentin

1) The Camera transform is a known bug, Avalon's 3D team is still
trying to figure out this '3D' math thing and the fact that you have to
take both object AND camera positions into account. Take it easy on
them.

3) The problem sounds like your custom objects are not getting
registered in the namescope, don't know why. You should be able to work
around this by not using Storyboard.TargetName and instead just
directly starting them using Storyboard.Begin

1) I was just trying to compile a list of the things that don't work for me
.... this is why I have reposted this issue ... I don't want to put any
pressure on the team
The workaround is to apply the transform to the camera properties (Position
, UpDirection, Look Direction) instead of assign it directly to the camera
transform property.

2),3) I was able to make them work (with the help of David Sklar) by using a
different namescope and shorter animation paths.

4) Is a known bug too.

5) Answered in its thread.

Thank you for your help,
Valentin

"loser" wrote:

> 1) The Camera transform is a known bug, Avalon's 3D team is still
> trying to figure out this '3D' math thing and the fact that you have to
> take both object AND camera positions into account. Take it easy on
> them.
>
> 3) The problem sounds like your custom objects are not getting
> registered in the namescope, don't know why. You should be able to work
> around this by not using Storyboard.TargetName and instead just
> directly starting them using Storyboard.Begin
>
>

Yes, the WPF portions of the December CTP are nearly identical to the Nov.
CTP. As we go to a more regular CTP schedule, not every component in the
distribution is going to change significantly with every CTP.

-Nick Kramer [MSFT]
http://blogs.msdn.com/nickkramer

---
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm


"viliescu" <viliescu@discussions.microsoft.com> wrote in message
news:8078FD9C-525A-4D6F-BE64-B1664E4CC12C@microsoft.com...
> Hi all,
>
> I have installed Dec CTP and the good news is that it seems
> there are no changes in the API - all of my programs recompiled without
> any
> problem.
>
> The bad news is that the problems that I had with Nov CTP are present in
> Dec
> CTP too.
> I am going to relist them:
>
> 1. Camera transform affects hit test results: If the camera transform is
> not
> the identity, the hit test results are "distorted". It seems that the
> transform is not taken into account when converting the 2D hit point into
> the
> 3D ray.
>
> 2. Trying to animate a property of a ModelVisual3D I get "Multi-step
> property paths may not be specified on an
> object of type 'System.Windows.Media.Media3D.ModelVisual3D'". The same
> with
> GeometryModel3D.
> The workaround was to go up on the tree and use a FrameworkElement
> (usually
> the Viewport3D) as the target name.
> But because I have some ModelVisual3Ds as the Children of another
> ModelVisual3D I cannot build the path - there is no dependency property
> (ChildrenProperty) for ModelVisual3D.
>
> 3. I have some custom controls derived from Canvas. These controls are
> dinamically added in code and have to be animated
> using storyboards.
> I register their name using
> Application.Current.MainWindow.RegisterName(myControl.Name, myControl);
> but I still get the error "The name 'myControlName' could not be resolved
> in
> the name scope of 'MS.Internal.AppModel.RootBrowserWindow'"
> It's like the name is not registered at all, I have tried to register the
> name at different levels (Grid etc.) but to no avail.
>
> 4. I have a list of custom objects to be presented as 3D objects in a
> listbox. I am using DataTemplate for this task and in the Triggers section
> I
> start an animation on mouse over. The error I get on mouse over is "The
> value
> of property 'Transform' in the path '(0).[0].(1).[1].(2).(3).(4)' points
> an
> immutable instance of
> 'System.Windows.Media.Media3D.RotateTransform3D' which may not be
> manipulated.". I understand this is a known bug,
> but I was hoping to be fixed in Dec CTP.
>
> 5. Superscript not working (see a previous thread).
>
> Thank you,
> Valentin
>