Either if or else if would've worked in this case. If you use else then it will catch EVERYTHING other than summer and spring... including any bogus seasons, which might be undesirable ie. not only will it catch winter and autumn, but it'll also catch "dry/wet seasons", "3rd season of breakin' bad", "your mom!". The if/else if is a bit more accurate.
Try an array of strings with a season index, rather than a pile of 'if' statements. Also, since you are just converting a set of strings to a set of colors, then just use season number to index a table of colors and skip the string conversion altogether. Less code overall and easier to maintain.
sure .... in the case of seasons that makes a lot of sense .... create an array etc etc ... however this is just a good example of how the "else if" vex works, and its application in other areas :)
While I definitely appreciate these tutorials and they are very helpful, they seem to be inconsistent about their assumption of the users technical level. For example the first example you gives feels like the tutorial is going to just go over basic coding practices, which to someone who is somewhat experienced in coding is kinda a waste of time. But then you go into built in attributes which is hugely important and individual to Houdini, but would go over the heads of people who have never coded before. This makes it seem like its unfocused because it shifts between a general coding tutorial and a more detailed tutorial, which kinda has the middle ground of being too advanced for beginners but also wastes the time of coders. I really wish that attributes was separated into its own video instead of, say the tutorial explaining basic loops, because someone who is interested in VEX is probably someone more technical who needs to know the unique feature of Houdini, not someone who has no experience with any programming language. Just direct that person who is a new coder to learning python, otherwise the scope of people you are trying to appeal to is to large to effectively please both.
@@KZLR The thing is loops are concepts that transfer over from other fields, it's likely that people have seen loops before. If they haven't theres a bunch of guides out there explaining the concepts. The built-in attributes is a system local to houdini, thus there aren't really any other resources out there aside from pouring through documentation.
![[VEX for Algorithmic Design] E01 _ Attribute Basics](http://i.ytimg.com/vi/V5i6KM_-8X0/mqdefault.jpg)
i wished you covered matrices too , i hope you make a tutorial about matrices ,how to use and how they can be useful
@10:46 why did u use another if statement and not just "else" ?
Either if or else if would've worked in this case.
If you use else then it will catch EVERYTHING other than summer and spring... including any bogus seasons, which might be undesirable ie. not only will it catch winter and autumn, but it'll also catch "dry/wet seasons", "3rd season of breakin' bad", "your mom!".
The if/else if is a bit more accurate.
thank you for this series I learned a lot very helpful
Try an array of strings with a season index, rather than a pile of 'if' statements. Also, since you are just converting a set of strings to a set of colors, then just use season number to index a table of colors and skip the string conversion altogether. Less code overall and easier to maintain.
sounds logic - could you please share an example how the code would look instead with your array approach ? :)
sure .... in the case of seasons that makes a lot of sense .... create an array etc etc ... however this is just a good example of how the "else if" vex works, and its application in other areas :)
@@ericprochnow7584
int seasonNum = chi("season");
string seasonArray[] = {"winter", "spring", "summer", "autumn"};
s@mySeason = seasonArray[seasonNum];
While I definitely appreciate these tutorials and they are very helpful, they seem to be inconsistent about their assumption of the users technical level. For example the first example you gives feels like the tutorial is going to just go over basic coding practices, which to someone who is somewhat experienced in coding is kinda a waste of time. But then you go into built in attributes which is hugely important and individual to Houdini, but would go over the heads of people who have never coded before. This makes it seem like its unfocused because it shifts between a general coding tutorial and a more detailed tutorial, which kinda has the middle ground of being too advanced for beginners but also wastes the time of coders.
I really wish that attributes was separated into its own video instead of, say the tutorial explaining basic loops, because someone who is interested in VEX is probably someone more technical who needs to know the unique feature of Houdini, not someone who has no experience with any programming language. Just direct that person who is a new coder to learning python, otherwise the scope of people you are trying to appeal to is to large to effectively please both.
What's so hard about built in attributes? Loops are more complicated... I like how he structured it.
@@KZLR The thing is loops are concepts that transfer over from other fields, it's likely that people have seen loops before. If they haven't theres a bunch of guides out there explaining the concepts. The built-in attributes is a system local to houdini, thus there aren't really any other resources out there aside from pouring through documentation.