I cannot explain why using the visited state doesn't work for this, but it's a problem I also commonly have.
My best practice for this is to avoid using the "built-in" states, such as visited and normal, and duplicate these to create custom states, as in the screenshot below.
I've attached an updated version of your .story file, hope this helps!
PS - the built-in states should automatically work great when used as intended, i.e. you should technically never have to trigger the visited state, for example, it should just automagically work.
Most of the time this works great for me. The original .story file you attached seemed to be having some major issues with both visited and selected though...
I sometimes find that Visited, Selected etc. come with some built-in conditions that I cannot change. If you make your own custom versions, then it is open-season on how you want it to work, and add the relevant trigger to do so.
4 Replies
I cannot explain why using the visited state doesn't work for this, but it's a problem I also commonly have.
My best practice for this is to avoid using the "built-in" states, such as visited and normal, and duplicate these to create custom states, as in the screenshot below.
I've attached an updated version of your .story file, hope this helps!
PS - the built-in states should automatically work great when used as intended, i.e. you should technically never have to trigger the visited state, for example, it should just automagically work.
Most of the time this works great for me. The original .story file you attached seemed to be having some major issues with both visited and selected though...
Totally agree with you Brian.
I sometimes find that Visited, Selected etc. come with some built-in conditions that I cannot change. If you make your own custom versions, then it is open-season on how you want it to work, and add the relevant trigger to do so.
Hi Brian Thank you for your reply. I thought I was going mad I will try the custom option as you suggested.. Thank you