follow.it gives you an easy way to subscribe to DotNetByExample - The Next Generation's news feed! Click on Follow below and we deliver the updates you want via email, phone or you can read them here on the website on your own news page.
You can also unsubscribe anytime painlessly. You can even combine feeds from DotNetByExample - The Next Generation with other site's feeds!
Title: DotNetByExample - The Next Generation - DotNetByExample - The Next Generation
Is this your feed? Claim it!
Ah, Unity. The company that was instrumental in me being able to venture into Mixed Reality, the very embodiment of the Silicon Valley motto “move fast and break things”… with unfortunately, emphasis on the second part.
Early HoloLens days, I learned an important lesson quickly: one of the scariest things you could do is upgrade your apps to a new Unity versi...
In ye olden days - in Lens Studio time units, this is about 8 weeks ago - we used a PinchButton from the Spectacles Interaction Kit to create a button on some kind of menu. This was - and still is - a pretty full-featured component, but all those options made it sometimes a bit hard to use. Enter UIKit, which makes it a lot simpler. You just, for instance, add a UIKit Rectang...
In part 1 I described how this component can be used, and I promised to go deeper into the details about how it worked in a follow-up post. This is that post.
The ScrollMenu prefabI usual...
If you have played with my Spectacles lens HoloATC you might have noticed the start menu with a scrollable list of buttons, which allows you to choose airports. This is a dynamic menu, that gets its data by downloading it from ...
Yet another small thing, this time to solve something that annoyed the heck out of me since day one. I really dislike this construction that you have to use when you have to get a reference to a component from a SceneObject
someSceneObject.getComponent(MyComponentClass.getTypeName()) as MyComponentClass;And what is even worse, it does not work at all
