Where should I start from? And an obsolete content report
See original GitHub issueFirst of all, thank you very very much for your toolkit! It would be really helpful for there are very little resources about SharpDX on UWP.
I would like to know how to use this toolkit, which function should I call first from my XAML page? I have tried Viewport3DX()
(constructor), but it didn’t raise the event Loaded
, and certainly I can’t raise it myself.
And I report the DisplayProperties
class used in the Viewport3DXLoaded
method is obsolete now. VS2015 suggest it should be replaced by DisplayInformation, and it seems to be requiring an instantiation.
Issue Analytics
- State:
- Created 7 years ago
- Comments:12 (2 by maintainers)
Top Results From Across the Web
What to Do With Old and Outdated Content
Review the content and identify any outdated information or broken links. Remove or update this information as needed. This involves going through your...
Read more >Why Removing Outdated Content Could Save Your Site
Find outdated content using Ubersuggest, Google Search Console, Google Analytics, or a full content audit. Evaluate outdated content and see if it can...
Read more >Fix Outdated Content To Boost Your SEO Results
Delete references to outdated stats in the content you're keeping. Comb through reasonably good and accurate posts. Edit out any inaccurate data ...
Read more >The Step-by-Step Guide to Conducting a Content Audit in ...
Head to your Google Analytics account and open Reports >> Engagement >> Pages and Screens. The Reports menu on Google Analytics. Here, you...
Read more >Content Migration: How to Handle Legacy and Duplicate ...
The second step to handle legacy, outdated, or duplicate content during migration is to update and refresh your content that still has value...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think you need to use x:Name instead of Name in the XAML file to be able to reference it in the code-behind file. http://stackoverflow.com/a/1128660/2252268 https://msdn.microsoft.com/de-de/library/ms752290(v=vs.110).aspx It seems Name is just a property of the super-class FrameworkElement.
I think this should be helpful https://github.com/helix-toolkit/helix-toolkit/wiki/Getting-started-with-WPF-3D.
The way I used to create scene was kind of mixed approach. I defined the Viewport in XAML and specified all it’s properties, but the scene itself was created in code. To do this, you need to get reference of Viewport that is already defined in XAML, not construct a new one. One of the ways to do this is to give a name to the Viewport
<hx:Viewport3DX Name="ViewportDx" ...
and then get reference to it in code,var hVpDx = FindName("ViewportDx") as Viewport3DX;
. You can do this in.cs
file of XAML (e.gMainWindow.xaml
hasMainWindow.xaml.cs
) and continue on building the scene as described in tutorial.