Blog Post
BriceMaret-a1ab
Community Member
Very nice looking and quite simple for a sequence.
I just think about the variables instead of states, maybe using the "visited" state, but I'm not sure in this example if that would make the programmation lighter.
In any case, good job!
I just think about the variables instead of states, maybe using the "visited" state, but I'm not sure in this example if that would make the programmation lighter.
In any case, good job!
Yvonne
2 years agoCommunity Member
Thanks so much for your feedback, Brice!
I forgo using the built-in visited state if I want to retain control of how an object is presented. In this instance, I wanted to keep the "Current" state available, if the user decided to return to a previously visited date. Showing that visited date as "Current" when the user is reviewing it helps me (as a user, too) know "where" I am. It's a small consideration, but this is a strategy I use commonly. :)
I forgo using the built-in visited state if I want to retain control of how an object is presented. In this instance, I wanted to keep the "Current" state available, if the user decided to return to a previously visited date. Showing that visited date as "Current" when the user is reviewing it helps me (as a user, too) know "where" I am. It's a small consideration, but this is a strategy I use commonly. :)