Rogad wrote at 2013-11-30 16:32:

objo wrote at 2013-12-02 19:52:

Rogad wrote at 2013-12-03 20:07:

behnam263 wrote at 2014-07-21 08:19:

behnam263 wrote at 2014-07-27 10:06:

milosgregor wrote at 2013-08-25 01:51:

Dim we As New Viewport2DVisual3D
Dim mesh = New MeshGeometry3D()
Dim pos As New Point3DCollection
pos.Add(New Point3D(Well1.X, Well1.Y, Zmax))
pos.Add(New Point3D(Well1.X, Well1.Y, Zmin))
pos.Add(New Point3D(Well2.X, Well2.Y, Zmin))
pos.Add(New Point3D(Well2.X, Well2.Y, Zmax))
mesh.TriangleIndices = New Int32Collection(New Integer() {0, 1, 2, 0, 2, 3})
mesh.TextureCoordinates = New PointCollection(New Point() {New Point(0, 0), New Point(0, 1), New Point(1, 1), New Point(1, 0)})
mesh.Positions = pos
we.Geometry = mesh
Dim material = New DiffuseMaterial(New SolidColorBrush(Colors.Transparent))
Viewport2DVisual3D.SetIsVisualHostMaterial(material, True)
we.Material = material
Dim SectionCanvas As New Canvas
SectionCanvas.Width = (Math.Sqrt(((Well2.X - Well1.X) * (Well2.X - Well1.X)) + ((Well2.Y - Well1.Y) * (Well2.Y - Well1.Y)))) * ScalingFactor
SectionCanvas.Height = (Zmax - Zmin) * ScalingFactor
SectionCanvas.Background = New SolidColorBrush(Colors.Transparent)
For geo As Integer = 0 To Sections3DDefinition(i).Section.SectionSegments.Count - 1
            Dim pol As New System.Windows.Shapes.Polygon
            pol.Stroke = New SolidColorBrush(Colors.Black)
            pol.ToolTip = Sections3DDefinition(i).Section.SectionSegments(geo).GeoID & " - " & Sections3DDefinition(i).Section.SectionSegments(geo).GeoName
            pol.StrokeThickness = 1
            pol.Fill = imgBrush
            For k As Integer = 0 To Sections3DDefinition(i).Section.SectionSegments(geo).TopPoints.Count - 1
                pol.Points.Add(New Point(Sections3DDefinition(i).Section.SectionSegments(geo).TopPoints(k).X * SectionCanvas.Width, Sections3DDefinition(i).Section.SectionSegments(geo).TopPoints(k).Y * SectionCanvas.Height))
   Next
            For k As Integer = 0 To Sections3DDefinition(i).Section.SectionSegments(geo).BottomPoints.Count - 1
                pol.Points.Add(New Point(Sections3DDefinition(i).Section.SectionSegments(geo).BottomPoints(k).X * SectionCanvas.Width, Sections3DDefinition(i).Section.SectionSegments(geo).BottomPoints(k).Y * SectionCanvas.Height))
            Next
        Next
        we.Visual = SectionCanvas
        my3D.Children.Add(we)

objo wrote at 2013-09-05 08:14:

stfx wrote at 2012-03-03 07:44:

Hey there, long time no see ;)

You have been doing some great work here though I didnt check the code in detail yet.

One thing that has always been an issue though, not just with this awesome toolkit but rather WPF 3D in general, is performance (atleast compared to directx). Thats why we really need to optimize the code.

Like in HelixViewport3D.cs you should remove the this.Viewport.Children.Contains check in the Add(), Clear(), Remove() functions as this is something which should be checked by the overlaying code. In fact I would even remove them completely since we already have access to Viewport.Children and can add/remove/clear them just as easy (in windowsforms.listview you also add the items like listview1.items.add(...) and not listview1.add(...)).

Also it might we worth considering in general which code should be in the library and which could be added to the examples. For example the headlight seems like a really seldom used feature which slows the viewer down a bit. Probably not noticable but still why not add an handler for camerachanged and export it to the example code. Although I guess its easy enough for anyone to remove it from the code if they so wish.

There are probably more places where performance could be optimized - maybe its even possible that the models that use the same models could somehow not redundantly save the mesh .

Thanks and keep up the good work

EDIT: Just out of curiosity how do you compare the performance of the first revs to the current one? Also is your screen line implementation also quite slow compared to usual DirectX line drawings? This was always bothering me with WPF actually. Btw were there any improvements in .net 4.0 for WPF 3D?

EDIT2: I need to have a scene with many models and emissive simple meshes (sphere, box, plane) which can be seen on a screen here: http://code.google.com/p/freelancermodstudio/ which need to be selected (display a bounding box) and then translated, scaled, rotated. I know for a fact that its possible with this toolkit but Would you say using directX approach might be more suitable as in performance?

objo wrote at 2012-03-10 16:02:

Thanks for the feedback! I think you are right, the Add,Clear and Remove methods are not needed. See changelist a79030ea7c0e.

I have not run a profiler on this library lately, but I don't think the 'headlight' feature has any noticable performance impact. 

Using the HelixViewport3D to calculate the total number of triangles will have a performance impact, so this should be used with care.

The line implementation (LinesVisual3D) in this library is of course slow compared to using DirectX LineList primitive, but it should be faster that the other two WPF3D implementations shown in the PointsAndLinesDemo.

If you need to draw a lot of lines (more than 1000 segments) or more control of the shaders, I think you should go for DirectX. The SlimDX library includes a WPF example! 

stfx wrote at 2012-03-11 00:23:

Thanks for your answer.

Btw before I forget:

• HelixViewport3D:OnApplyTemplate() ... last assert is incorrectly the same as the previous one

• Viewport3DHelper:FindNearest() ... the 5 lines after

  // first transform the Model3D hierarchy
  

  seem to break correct detection of clicked visual for me

• Also Resharper notices some small coding issues which might be worth looking into

Right now I am struggling to correctly use the LinesVisual3D class (cant seem to find out the correct points). I was delighted when I first noticed the  BoundingBoxVisual3D.cs file thinking that this one would create those screen space lines around an object until I found out that its just some tubes being aranged like a boundingbox :D

objo wrote at 2012-03-11 20:46:

OnApplyTemplate fixed, thanks!

Let me know if you find the bug in Viewport3DHelper:FindNearest!

Yes, I try to keep the Resharper/Stylecop status on 'green'. Viewport3DHelper and HelixViewport3D seems to be ok, but I am sure there are warnings in other classes. Please report if you see some bugs.

Yes, BoundingBoxVisual3D is using cylinders - I made that class before making the LinesVisual3D. Should add a property where you can select between lines or cylinders.

stfx wrote at 2012-03-11 22:23:

Well commenting out the 5 lines after that comment fixed the FindNearest function for me ;)

Hm I would rather replace the functionality in BoundingBoxVisual3D as I think nobody would use cylinders for something like that :P

Other than that I only found some code styling issues which dont affect anything like why are your comments in the functions in MeshBuilder.cs commented out twice? Also in MeshBuilder.AddTriangeStrip() the  wikipedia link exists twice.

objo wrote at 2012-04-05 02:08:

Could the error be in GetTransform(Visual3D, Model3D)? Can you create a small example model where the current implementation fails?

I have tested with the stick figure in ExportDemo (this contains lots of Model3D transforms), and it seems to work ok here (double click on the 'fingers', and you see the target point will be set correctly).

Bounding box with lines - I added this issue http://helixtoolkit.codeplex.com/workitem/9950

Thanks, the MeshBuilder wiki-link comments will be fixed in the next code push. I use "////" when I don't want resharper to reformat comment 'figures'.

peterthesaint wrote at 2014-07-25 12:44:

rakelmasuta wrote at 2014-03-13 00:35:

objo wrote at 2014-04-29 10:56:

rakelmasuta wrote at 2014-05-19 18:02:

<Window x:Class="PanoramaDemo.MainWindow"
        xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
        xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" xmlns:ht="clr-namespace:HelixToolkit.Wpf;assembly=HelixToolkit.Wpf" Title="TA Rakel" 
        xmlns:k="http://schemas.microsoft.com/kinect/2013"
        Height="480" Width="640">
        
    <Grid>
        
        <ht:HelixViewport3D x:Name="view1" ShowViewCube="False" ShowCameraTarget="False" CameraMode="FixedPosition" RotationSensitivity="0.6">
            <ModelVisual3D>
                <ModelVisual3D.Content>
                    <AmbientLight Color="White"/>
                </ModelVisual3D.Content>
            </ModelVisual3D>
            <ht:PanoramaCube3D Source="Models\Opera\"/>
        </ht:HelixViewport3D>
        <k:KinectSensorChooserUI HorizontalAlignment="Center" VerticalAlignment="Top" Name="sensorChooserUi" />
        <k:KinectUserViewer VerticalAlignment="Top" HorizontalAlignment="Center" k:KinectRegion.KinectRegion="{Binding ElementName=kinectRegion}" Height="100" UserColoringMode="Manual" />
        <k:KinectRegion Name="kinectRegion">
            <Grid>
                <k:KinectTileButton Label="Press me!" Click="ButtonOnClick" VerticalAlignment="Top" Margin="28,0,0,0" HorizontalAlignment="Left"></k:KinectTileButton>
                <k:KinectCircleButton Label="Circle" HorizontalAlignment="Right" Height="200" VerticalAlignment="Top" Click="ButtonOnClick" >Hi</k:KinectCircleButton>
                <k:KinectScrollViewer VerticalScrollBarVisibility="Auto" HorizontalScrollBarVisibility="Auto" VerticalAlignment="Bottom">
                    <StackPanel Orientation="Horizontal" Name="scrollContent" />
                </k:KinectScrollViewer>
            </Grid>
        </k:KinectRegion>
    </Grid>
</Window>

// --------------------------------------------------------------------------------------------------------------------
// <copyright file="MainWindow.xaml.cs" company="Helix 3D Toolkit">
//   http://helixtoolkit.codeplex.com, license: MIT
// </copyright>
// --------------------------------------------------------------------------------------------------------------------

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Windows;
using System.Windows.Controls;
using System.Windows.Data;
using System.Windows.Documents;
using System.Windows.Input;
using System.Windows.Media;
using System.Windows.Media.Imaging;
using System.Windows.Media.Media3D;
using System.Windows.Navigation;
using System.Windows.Shapes;
using Microsoft.Kinect;
using Microsoft.Kinect.Toolkit;
using Microsoft.Kinect.Toolkit.Controls;
using Microsoft.Kinect.Toolkit.Interaction;

namespace PanoramaDemo
{
    /// <summary>
    /// Interaction logic for MainWindow.xaml
    /// </summary>
    public partial class MainWindow : Window
    {
        private KinectSensorChooser sensorChooser;

        public MainWindow()
        {
            InitializeComponent();
            Loaded += OnLoaded; /// kinect Loaded
            var camera = view1.Camera as PerspectiveCamera;
            camera.Position = new Point3D(0, 0, 0);
            camera.LookDirection = new Vector3D(0, 1, 0);
            camera.UpDirection = new Vector3D(0, 0, 1);
            camera.FieldOfView = 120;
           


        }
        /// <summary>
        /// Deteksi Status kinect
        /// </summary>

        private void OnLoaded(object sender, RoutedEventArgs routedEventArgs)
        {

            this.sensorChooser = new KinectSensorChooser();
            this.sensorChooser.KinectChanged += SensorChooserOnKinectChanged;
            this.sensorChooserUi.KinectSensorChooser = this.sensorChooser;
            this.sensorChooser.Start();
        }


        private void SensorChooserOnKinectChanged(object sender, KinectChangedEventArgs args)
        {
            bool error = false;
            if (args.OldSensor != null)
            {
                try
                {
                    args.OldSensor.DepthStream.Range = DepthRange.Default;
                    args.OldSensor.SkeletonStream.EnableTrackingInNearRange = false;
                    args.OldSensor.DepthStream.Disable();
                    args.OldSensor.SkeletonStream.Disable();
                }
                catch (InvalidOperationException)
                {
                    // KinectSensor might enter an invalid state while enabling/disabling streams or stream features.
                    // E.g.: sensor might be abruptly unplugged.
                    error = true;
                }
            }

            if (args.NewSensor != null)
            {
                try
                {
                    args.NewSensor.DepthStream.Enable(DepthImageFormat.Resolution640x480Fps30);
                    args.NewSensor.SkeletonStream.Enable();


                }
                catch (InvalidOperationException)
                {
                    error = true;
                    // KinectSensor might enter an invalid state while enabling/disabling streams or stream features.
                    // E.g.: sensor might be abruptly unplugged.
                }
            }

            if (!error)
                kinectRegion.KinectSensor = args.NewSensor;
        }




        /// <summary>
        /// Untuk event on click button
        /// </summary>
        /// <param name="sender"></param>
        /// <param name="e"></param>
               
        private void ButtonOnClick(object sender, RoutedEventArgs e)
        {
            MessageBox.Show("Well done!");
        }
    }
}

objo wrote at 2014-05-19 21:45:

rakelmasuta wrote at 2014-05-20 00:47:

soheilvb wrote at 2012-03-28 05:05:

Hey guys ,

tnx for this toolkit , that's really great .

I'm having problems with texture of some object files that i extracted using a script from unity ..

these are two sample of object files : (Direct link)

http://parsaspace.com/files/9680754884/objects.zip.html

3ds max open these files perfectly . but Meshlab can't load the texture .

i also, loaded these files in 3ds max and exported them to .3ds format and loaded them with toolkit. there was the same problem !

i'm using the the last version of your component . (Compiled from last source code)

i have another question :

I want to load for example 2000 object files into one scene. I loaded them from object files into one Helixviewport . that takes about 20 second and 820 meg of memory and that's slow and not smooth ... ( in my quad core 3.4 imac).

anyway to optimize this ?

tnx for your time .

sorry for poor english .

soheilvb wrote at 2012-03-28 12:25:

for the texture problem. i was using the previous version . then i use the new version and i see everything is white !!!

then comment out these :

  if (this.AmbientMap == null)
                {
              //      var ambientBrush = new SolidColorBrush(this.Ambient) { Opacity = this.Dissolved };
               //     mg.Children.Add(new EmissiveMaterial(ambientBrush));
                }
                else

and now everything is goood.

also for 3ds format, i think you forgot that change

var textureBrush = new ImageBrush(img);

with

var textureBrush = new ImageBrush(img) { ViewportUnits = BrushMappingMode.Absolute, TileMode = TileMode.Tile };

. this solved the problem .

I still have the second problem though , tnx

objo wrote at 2012-04-05 01:28:

thanks for the files and the bug report, I will look into this soon!

objo wrote at 2012-04-05 23:14:

I applied the two bug fixes! Thanks! Your example .obj files look ok now.

objo wrote at 2012-04-05 23:17:

are you loading 2000 different models? If not, you should freeze and share the geometry for all models that should look the same.

soheilvb wrote at 2012-04-06 13:17:

yes. 2000 different models. i guess WPF 3D can't manage this amount of objects. i should probably go to Directx and slimdx.

tnx for your response.

objo wrote at 2012-04-08 13:15:

Try the latest version of the obj reader, it should have better performance when using smoothing groups. I also profiled the code and found that the most expensive operation was splitting the input string by a regular expression. I changed it into a compiled expression, but maybe there are faster ways to solve this..

See also http://msdn.microsoft.com/en-us/library/bb613553.aspx

Did you try adding all models into a Model3DGroup? That should be more efficient than adding 2000 Visual3Ds.

soheilvb wrote at 2012-04-08 14:42:

tnx

i read that msdn article multiple times .

I used single Model3DGroup method before. there was no improvement in performance at all.

i have about 40 textures  and many meshes use the same material. i'm thinking about merging the meshes that have the same material into larger meshes but there is two problem:

1. i don't know how to merge them and does it really effect the performance?

2. i need every model clickable .

i used Simplify method in Meshgeometryhelper too. but there was some errors ...

there is ultimately about 900,000 vertices in all the models.

tnx a lot ..

soheilvb wrote at 2012-04-08 15:02:

Ohhhhhh myyyyy gooooood !!

i just tried your last version ...

the ram decreased from 800 meg to 300 meg.

time of importing objects decreased to half ...

i'm really grateful .

i think the problem was with the meshbuilder that you fixed. am i right?

now if i share material, that's gonna effect the performance?

HDNguyen wrote at 2012-03-13 20:33:

Hi Objo

I am studying Helix and find it very good. I try also to extend the example RhinoDemo at the first place but without success. Could you help me ?

As you know the RhinoDemo has actually 4 windows with 4 not related HelixViewport3D. What I try to extend is the left window that contain the main HelixViewport3D and should show the HelixViewport3D with a FrontView, the right window shows the BackView, the bottom left shows the LeftView and the bottom right shows the RightView but of the same HelixViewport3D

Is it possible with WPF 3D in general and specifically with Helix ? What should we do so that we can have 2 or more windows show the same Viewport3D but with different camera look direction and camera positions ?

govert wrote at 2012-03-13 22:26:

You're seeing a place where the WPF design and the Helix Toolkit design does not fit together so well. I'd also love to hear Objo's response, but can give some background (filled with a painful amount of jargon).

In WPF there is a Visual tree, and every Visual (say a BoxVisual3D) can appear only once in the Visual tree. A Viewport3D (which has the Camera) is itself a Visual, and will display its Visual3D children, so those Visual3D children can appear in at most one Viewport3D. So if we want to see the same 'scene' from different Camera positions (in different Viewport3Ds), the different Cameras have to be looking at _different_ ModelVisual3Ds.

Now, different ModelVisual3Ds can display the same Model3D. This makes me prefer an approach which puts the geometry construction on the Model3D side, rather than to have the Visual3Ds build the mesh, as happens in the various Visual3D classes in the current Helix Toolkit.

For example, say you want a draw a Box that will have some fixed dimensions (Length x Width x Height) and you want to see it in different Viewport3Ds (like in the different RhinoDemo views). Then you certainly need to have at least one Visual3D of your box for each Viewport3D (say we have four Viewport3Ds) - this is just how WPF works. But the current design in the Helix Toolkit might lead you to make a BoxVisual3D with the right dimensions, which can then only be displayed once (in one Viewport3D). So you'll end up making four BoxVisual3Ds, each with the same dimensions etc., but representing a single box in the 'real' world.

One might prefer to have the four Visual3Ds share a single Model3D (probably a GeometryModel3D with a MeshGeometry, which could be textured etc.) That way there is one shared Box model, displayed through the four Visual3Ds. This would put the Mesh generation code (currently in the Tesselate methods of the XXXVisual3Ds) on something like a BoxModel3D (though you I don't think you can derive from GeometryModel3D that way - so maybe BoxModelBuilder3D) . This is to generate the meshes once for the 'real' Box object and then have them 'display' through different Visual3Ds - each Visual3D might now be a simple Visual3D, and no longer a model-specific Visual. Adding and using the interactivity of the UIElement3D can be tricky, because you now have to push interactions into the Model3D if they are to display in the different views. (Imagine you want to select one side of your Box).

So - this is a tricky issue, and the BoxVisual3D etc. design in Helix Toolkit at the moment doesn't really make this kind of multi-view interface easy. By moving the tesselation code out of the Visual3Ds, you'll be able to make a single Model3D (or rather a few Model3DGroups, each with many Models and various transforms) that are 'displayed' by a few very simple Visual3Ds into the different Viewport3Ds. The granularity of your Model / Visual breakdown might be determined by what kind of interactivity you need to support.

I think the current Helix Toolkit  Model / Visual design with the mesh being built in the Visual3D came from an early sample by one of the WPF3D developers, and it might have some other advantages like being able to instantiate those shapes in XAML. Here is one discussion from around the time WPF3D was implemented, http://blogs.msdn.com/b/danlehen/archive/2005/10/09/478923.aspx, with the follow-up example here http://blogs.msdn.com/b/danlehen/archive/2005/10/16/481597.aspx. But, with due respect, I think the ModelVisual3D-derived primitives approach is problematic, and in particular it makes something like the RhinoDemo very clumsy to implement.

-Govert

objo wrote at 2012-03-14 00:32:

That's a great explanation from Govert. Thanks!

There should be no difference between using a Viewport3D and a HelixViewport3D, the same limitations apply. Use ModelVisual3D elements (not the Visual3D types in Helix toolkit) if you want to share the Model3D between different visual elements. And remember to Freeze() the Model3Ds. 

The RhinoDemo was mostly an experiment to create a user interface that looked close to the original, and define as much as possible of the user interface in XAML.

HDNguyen wrote at 2012-03-14 13:03:

Thank a lot, govert and objo

The explanation of govert is great. As i understand, for short, since a Viewport3D can have only 1 camera so when we want to get several views from different Camera positions, we must create the same amount of Viewport3Ds, so the problem is how to synchronize them

What do you think about the strategy: In the sample RhinoDemo I will grab and clone the children of the main Viewport3D, say the top right window, and add them as children to the Viewport3D of the other windows, another problem is also to override the methode OnVisualChildrenChanged(DependencyObject visualAdded, DependencyObject visualRemoved) to get them synchronized

Wait to hear your opinions

Thanks

viettp wrote at 2011-09-23 10:04:

I must use WPF 3.5 (.NET 3.5) in my solution.

And I've tried build release of Helix in .NET 3.5.

When using the output .dll files (.xml files included) in an WPF4 application, it's ok. But when I try those .dll files with my WPF3.5 application (also with examples with setting in .NET 3.5), it didn't recognize mouse gestures.

Any advice??

viettp wrote at 2011-09-23 10:09:

Problem happened when I was trying to rotate the model in HelixViewbox3D

viettp wrote at 2011-09-23 11:43:

I've found the reason. Somehow binding in .NET 3.5 is different with in .NET 4.0.

In .NET 3.5, the bindings in those lines in theme "Generic.xaml" don't work:

<local:CameraController.InputBindings>
   <local:InputBindingX Gezture="{Binding Path=ResetCameraKeyGesture, RelativeSource={RelativeSource Mode=TemplatedParent}}" Command="{x:Static local:CameraController.ResetCameraCommand}"/>
   <local:InputBindingX Gezture="{Binding Path=RotateGesture, RelativeSource={RelativeSource Mode=TemplatedParent}}" Command="{x:Static local:CameraController.RotateCommand}"/>
   <local:InputBindingX Gezture="{Binding Path=PanGesture, RelativeSource={RelativeSource Mode=TemplatedParent}}" Command="{x:Static local:CameraController.PanCommand}"/>
   <local:InputBindingX Gezture="{Binding Path=ZoomGesture, RelativeSource={RelativeSource Mode=TemplatedParent}}" Command="{x:Static local:CameraController.ZoomCommand}"/>
   <local:InputBindingX Gezture="{Binding Path=ZoomRectangleGesture, RelativeSource={RelativeSource Mode=TemplatedParent}}" Command="{x:Static local:CameraController.ZoomRectangleCommand}"/>
   <local:InputBindingX Gezture="{Binding Path=ChangeFieldOfViewGesture, RelativeSource={RelativeSource Mode=TemplatedParent}}" Command="{x:Static local:CameraController.ChangeFieldOfViewCommand}"/>
   <local:InputBindingX Gezture="{Binding Path=ChangeLookAtGesture, RelativeSource={RelativeSource Mode=TemplatedParent}}" Command="{x:Static local:CameraController.ChangeLookAtCommand}"/>
   <local:InputBindingX Gezture="{Binding Path=ZoomExtentsGesture, RelativeSource={RelativeSource Mode=TemplatedParent}}" Command="{x:Static local:CameraController.ZoomExtentsCommand}"/>
   <local:InputBindingX Gezture="{Binding Path=ResetCameraGesture, RelativeSource={RelativeSource Mode=TemplatedParent}}" Command="{x:Static local:CameraController.ResetCameraCommand}"/>
   <local:InputBindingX Gezture="{Binding Path=TopViewGesture, RelativeSource={RelativeSource Mode=TemplatedParent}}"  Command="{x:Static local:CameraController.TopViewCommand}"/>
   <local:InputBindingX Gezture="{Binding Path=BottomViewGesture, RelativeSource={RelativeSource Mode=TemplatedParent}}"  Command="{x:Static local:CameraController.BottomViewCommand}"/>
   <local:InputBindingX Gezture="{Binding Path=LeftViewGesture, RelativeSource={RelativeSource Mode=TemplatedParent}}"  Command="{x:Static local:CameraController.LeftViewCommand}"/>
   <local:InputBindingX Gezture="{Binding Path=RightViewGesture, RelativeSource={RelativeSource Mode=TemplatedParent}}"  Command="{x:Static local:CameraController.RightViewCommand}"/>
   <local:InputBindingX Gezture="{Binding Path=FrontViewGesture, RelativeSource={RelativeSource Mode=TemplatedParent}}"  Command="{x:Static local:CameraController.FrontViewCommand}"/>
   <local:InputBindingX Gezture="{Binding Path=BackViewGesture, RelativeSource={RelativeSource Mode=TemplatedParent}}"  Command="{x:Static local:CameraController.BackViewCommand}"/>
   <local:InputBindingX Gezture="{Binding Path=OrthographicToggleGesture, RelativeSource={RelativeSource Mode=Self}}"  Command="{x:Static local:HelixViewport3D.OrthographicToggleCommand}"/>
</local:CameraController.InputBindings>

So, I write some additional binding code in HelixViewport3D.OnApplyTemplate() doing the same work:

            if (this.cameraController == null)
            {
                this.cameraController = this.Template.FindName(PartCameraController, this) as CameraController;
                if (this.cameraController != null)
                {
                    this.cameraController.Viewport = this.Viewport;
                    this.cameraController.InputBindings.Add(new InputBinding(CameraController.RotateCommand, this.RotateGesture));
                     ...
                }
            }

I think this's a notable attention for you.

objo wrote at 2011-09-30 07:30:

thanks for the feedback, I will have a look at this soon.

I will check if setting the input bindings in code could help - note that the xaml also bind the gestures.

objo wrote at 2011-10-03 19:59:

I just tried building the library with .NET 3.5, and everything seems to work ok. The mouse gestures work just like they do in 4.0.

Can you try again, and let us know if you still have the problem.

viettp wrote at 2011-10-04 03:54:

If I compile HelixToolkit in .NET 3.5   AND   use the library in a .NET 3.5 WPF project, the problem will happen

keithtmccartney wrote at 2011-10-31 14:37:

Hey there, I'm currently toying with the panorama sample but am having trouble alternating between the left mouse button (LMB) and the default right mouse button (RMB) for controlling the camera around the pano's.

How would I go about changing this gesture?

Thank you.

viettp wrote at 2011-10-31 16:11:

Search for InitBinding() function in solution, you'll see ;)

keithtmccartney wrote at 2011-11-01 11:55:

I'm having difficulty finding that function Việt.

I firstly used Ctrl+F to search the above throughout the entire solution, but found nothing.

I then searched throughout the HelixToolkit reference in the object browser, but could locate nothing.

I searched throughout Google with the above function as keywords, but located only Java-related articles, but did find one C#-related article with no thorough material that I could've used.

If you are able to assist me further please do so, I would really love to swop the default right-button manoeuvring to the left-button.

Thank you, Keith.

viettp wrote at 2011-11-01 16:57:

the function is CameraController.InitializeBindings() . Sorry for my mistake.

You can find these things in HelixToolkit project that make input structure:

---- The binding for intput: in file Themes\Generic.xaml

this contains the ControlTemplate for the HelixViewport3D. You can find tag CameraController.InputBindings in this file. It bind gestures with corresponding command of CameraController (a part of HelixViewport3D).

---- The gesture definitions: in file Controls\HelixViewport3D.cs

this contains default definitions for all mouse gesture. You can find RotateGestureProperty . It is set MouseAction.RightClick. Change it to MouseAction.LeftClick for your need.

---- The binding for commands: in file Controls\CameraController\CameraController.cs

in function InitializeBindings() you can see the binding for command with corresponding handler. If you want to change what to do with a command, you can make it here.

Regards,

Việt.

objo wrote at 2011-11-01 20:37:

thanks for replying to this question, Việt! You are right, the RotateGesture property should be used to change which mouse button to use. I think you can also add additional InputBindings to the HelixViewport3D instance, but I have not tested this. 

keithtmccartney wrote at 2011-11-02 14:01:

Thank you very much for that Việt.

I have now implemented my panorama project with left-click mouse gesturing.

Also, I have updated my project to the now stable engine status.

Within the project there is jumping from panorama to panorama through xml.

However, I am experiencing problems with that very functionality whereas with engine version: 0.9.0.0 it worked suitably.

Below are links to the updated/original versions of the project.

Please help in debugging this, if availability prevents this, then I can resort to the original use of the version. Although, progress would be nice (I like the new 'Move' cursor, it's seemingly more fluid!).

Thank you Việt for your help, and thank you Objo for your wonderful engine.

Keith.

keithtmccartney wrote at 2011-11-02 14:33:

Here are the links (Mediafire):

Original: http://www.mediafire.com/?340cb7lcfbuc0vi

(If the 'PanoramaCube3D' Source is set to 'Opera' then the MouseWheel function should be set to GrandHotel, and vice versa.

The zoom point is in the XML. For 'Opera', the zoom point in on the steps to the very left of the 'Right' face between the two lights.

For 'GrandHotel', the zoom point is on the face - 'Back' - and is located on the policeman with horse foot-patrol.)

Updated (Present): http://www.mediafire.com/?9245lb63skc626t

Thanks.

objo wrote at 2011-11-02 19:56:

cool project, I like the way you zoom in to go to a new panorama :)

Reading the transition.xml didn't work with my culture (',' decimal point) - so I just added this line to your demo            

Thread.CurrentThread.CurrentCulture = CultureInfo.InvariantCulture;

The rotation gesture can be set by xaml:

<ht:HelixViewport3D.RotateGesture>
  <MouseGesture MouseAction="LeftClick"/>
</ht:HelixViewport3D.RotateGesture>

or in code

myHelixView3D.RotateGesture = new MouseGesture(MouseAction.LeftClick);

I see there are a few more features to be added to the control (e.g. don't allow change of camera position, reset camera etc. in this application) but I don't have time to implement that myself right now.

keithtmccartney wrote at 2011-11-03 11:48:

Ahh, Objo, so you managed to transition onto a new panorama in the updated version?!

I am having difficulty doing this. There is no 'RotateGesture' in the original version which is why I am limited to progress with my alpha-state reference library.

Please do so continue working on those features and keep me notified of updated.

Or suggest to me some guidance on progressing them myself.

I'm currently trying to implement some visual cue's (hotspots) for multimedia, using the same ideology as that what I'm using for the transitioning hotspot's.

Would you be able to link me to a download of the project with the above fixes?

Thank you, Keith.

objo wrote at 2011-11-03 23:04:

hi Keith, I only checked that RotateGesture property worked as intended. Sorry I don't know why your hotspot code doesn't work. Did you consider using spherical coordinates for the hotspots?

rufus9876 wrote at 2011-10-07 08:34:

I had a look at the SpaceNavigatorDecorator.
The SpaceNavigatorDecorator within HelixToolkit.Input uses TDxInput (TDx.TDxInput.dll).

I was wondering about the origin of the dll (3dconnexion?) and if it is allowed to spread the dll together with any kind of project using the HelixToolkit3D?

objo wrote at 2011-10-07 09:02:

Go to 3dconnexion, register and accept their SDK license agreement

http://www.3dconnexion.com/service/software-developer/licence-agreement.html

terry_513 wrote at 2014-01-23 13:13:

I want to create a TubeVisual3D on a  TubeVisual3D - inner tube & outer tube. I want the inner tube to be on the Outer tube -so inner tube can be visible over outer. My code is :- 

            <HelixToolkit:TubeVisual3D Path="-12 7 -1.45 -2 0.5 0 -8 -55 0.45" x:Name="myTube" Diameter="5" Fill="Gray" IsPathClosed="False"
                                          />
            <HelixToolkit:TubeVisual3D Path="-10 5 -0.45 2 0.5 0 -8 -55 0.45" x:Name="myInnerTube" Diameter="2" Fill="White" 
                                          />

<HelixToolkit:TubeVisual3D x:Name="tube1" Path="{Binding TubePipe}" Diameter="1.5" IsPathClosed="False"
                                        Fill="#FFD61D1D"/>

// Code Behind

public WellBoreWindow()
        {
            InitializeComponent();
            //Pipe = CreatePath();
            TubePipe = CreateTubeVisual();
            DataContext = this;
        }

private IList<Point3D> CreateTubeVisual()
        {
            // -9 0 -0.45 -8 0.1 0 -9 0 0.45
            List<Point3D> pts = new List<Point3D>();
            pts.Add(new Point3D(-12, 0, 0.45));
            pts.Add(new Point3D(-11, 0.1, 0));
            pts.Add(new Point3D(-12, 0, 0.45));
            return pts.ToList();
        }


        public IList<Point3D> TubePipe { get; set; }

objo wrote at 2014-01-25 22:36:

            TubePipe = new Point3DCollection(CreateTubeVisual());

            pts.Add(new Point3D(-12, 0, 0.45));
            pts.Add(new Point3D(-11, 0.1, 0));
            pts.Add(new Point3D(-10, 0, 0.45));

terry_513 wrote at 2014-01-27 06:56:

objo wrote at 2014-02-02 12:02: