Комментарии:
great tips
Ответитьyou can do that! wow! Great tip
ОтветитьUnfortunately, the split into 3 Lines for the Short format is unreadable, since most of the screen is covered by the overlay :-p
ОтветитьOne thing to look out for is when you need to rename the variable, typically you would use [FormerlySerializedAs] on the backing field to keep its' inspector values (your IDE might do this automatically), but when the backing field is implicit, it's harder to rename it, since you need to know the system generated name for it (IDE doesn't automate this process).
ОтветитьI learned this some time ago and I do think it's kinda cool, but I've never really used it because the FormerlySerializedAs attribute doesn't work with this format. So I still go with the explicit field and the get-only property wrapper.
Ответитьman i CAN"T see the same effect, there are links to other vids
ОтветитьThis is amazing - thanks very much for the tip!
ОтветитьWhaaaaaaaaaat since when does this exist?
Ответить20sec in the vid gets covered so no idea what you did.
ОтветитьPlease make normal videos.
Ответитьi actually dont like the shorts format because you can't scroll through it at your own pace and you are forced to rewatch it
Ответитьlike
ОтветитьI do not like the short format, you can only stop it, you can't fast forward, go back, slow down, make it faster. Short video in normal format is much much better
ОтветитьIt`s awesone. THANKS!!!
ОтветитьGreat tip! Thank you for pointing it out.
Ответить❤️
Ответитьi hate this format because you can't go forward/back or change the speed of the video.
ОтветитьKnew about this for a while. Great tip nonetheless
ОтветитьI remember learning about the field: specifier for attributes and tried it out with properties and it didn't serialize. I must have messed up because a few weeks ago I tried it again and it suddenly worked.
ОтветитьThis YT Shorts format is just bad. I wish you would have made an actual video about the topic.
ОтветитьLove the Shorts format Jason!
ОтветитьThat's awesome! Thanks for sharing
ОтветитьNOOOOOOOOOOOOOOOOO WAYYYYYYYYYYYY. I have been doing the annoying field & property because of [SerializeField] (can get around it with Custom Inspector but would be silly to make one just for that). I'm gonna test this now, this is gold!!!
ОтветитьI like this short but the only problem is, it can't rewind, or I can't rewind
ОтветитьHi Jason,
this is such a nice tip my code got so much cleaner, thank you!!!
Ich got a queston for you, why don´t you use internal instead of public, i think i never saw you use it. I would love to see a video in which you show the advantages, becouse may devs are concerned about the security of there code.
What do you think about internal :)?
Thanks Jason, this is great! Also, if you use Odin Inspector, you can do [Show in inspector] next to your field. Odin is actually quite a nice editor plugin for making inspectors. I recommend it (when it goes on sale or in a bundle of course)
ОтветитьThis is a fantastic tip. I have always hated the clutter of adding backing fields to public getters. I am running into a problem adding these to my custom editor scripts though. I can access a private serializedfield from my class by finding with through serializedObject.FindProperty and then linking it to an EditorGUILayout.PropertyField but when I try to do the same with a property using this method I get an error that its null and my editor won't draw. Anyone have ideas on what I am missing? :)
ОтветитьAwesome tip, thanks!
Ответить😱😱😱😱😱😱✌🏻✌🏻✌🏻✌🏻✌🏻✌🏻✌🏻
ОтветитьIs it possible to use this with a statement body? I need to enable/disable a component when my property is set. But this setup doesn't seem to like statement bodies for the get{} set{}
ОтветитьYou've unleashed one epic AF refactor...
ОтветитьYou are the best, now I FINALLY can use interfaces effectively!!!
ОтветитьWould be cool if it showed up in inspector. If not then I guess ima stick to a serialized private var with m_ 😂
Ответитьonly works for property that is get? not set? only get?
ОтветитьJust wanted to thank you, about two years ago you came on a Discord call with me because I was stuck with my project and the lessons you taught me in that half an hour is the reason I am where I am today. :)
Ответить