![]() I like a broad introduction followed by a specific example. You of course argue that if you don't find results, then broaden to C# in general. Because they don't realize it's a C# thing. I often catch people (OP even did it) confusing things about the C# language as if it's a "unity thing" and can't find any results. If you don't find helpful Unity-specific examples/explanations then yes, absolutely go check out general C# but I recommend starting with Unity and branching off from there.Ĭlick to expand.But also often limits the perspective of what's going on development wise. And so on.Īnd it's not likely that someone who needs to know what those things are will know whether it's best to search for a Unity-specific explanation or not.Īnd just in general, having examples that are more relevant to the environment you're actually working in will make those examples much easier to process and understand. Constructors are also treated differently in Unity than in other C# scenarios. Also, non-Unity discussions of null comparisons might make someone more confused about how "!= null" means to check if an object has been destroyed, thanks to Unity's overridden null comparison. ![]() IEnumerators/coroutines come to mind, for example. There are certain things which if searched this way would produce search results that are not only unhelpful, but may even make it harder to grasp the concept as far as it's relevant to Unity. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |