Matt Breckon
Matt Breckon
I have answered a similar question on StackOverflow in which I ended up creating an attached property to zoom the extents based on changes to properties in the ViewModel. Whilst...
The Model Viewer example uses the WPF (rather than the WPF.SharpDX) version of the toolkit. The WPF version uses an internally deprecated file importer rather than providing the Assimp library...
See also https://github.com/Caliburn-Micro/Caliburn.Micro/issues/634
I don't use Caliburn.Micro across a wide enough set of scenarios (and so far only on 3.2) to take a huge amount on but I'd like to see it continue....
@KasperSK referencing https://github.com/Caliburn-Micro/Caliburn.Micro/issues/708#issuecomment-646445768 I've created this issue to gather together thoughts and specific changes we might want to do to the documentation for V4.0. Please feel free to contribute (see...
I wonder if we risk losing the bigger picture if we move *all* the documentation discussion to the other repo. What do people think about keeping the discussion here around...
Something to make clear in the UWP platform section - namespace syntax! [Issue 710](https://github.com/Caliburn-Micro/Caliburn.Micro/issues/710)
I assume this is the SharpDX version. If you look in https://github.com/helix-toolkit/helix-toolkit/blob/develop3/Source/HelixToolkit.Native.ShaderBuilder/Common/DataStructs.hlsl you can see that there is a constant number of lights - this is done for performance reasons...
I think I'd want to squash this into a single commit but I'm not familiar with github workflows - do I need to do something or can it be done...