It looks like you're new here. If you want to get involved, click one of these buttons!
You give them a call. 'Hi, I'm <<cyclinglink "$call" "an intern" "a reporter" "an environmental protestor">>.'<br /><br />[[Next|$call]]
Comments
Honest question: do you or anyone else think that I should tweak the link syntax so that the destination expression is evaluated lazily - as in, only at the moment of clicking?
(One problem with this is that it would break the :visited CSS selector I added in 1.4.1, because it wouldn't be possible to determine visitedness initially.
No. I don't believe that these should behave differently: The $a should not receive early evaluation in one case (call time) and late evaluation in the other (click time).
Nor do I believe it wise to make the (two basic) parts of the link & text syntax behave differently: Since $text must be evaluated at call time, why wouldn't $link.
Additionally, as noted, this would be a breaking change. Beyond, what's already been mentioned, all existing code which functions like the following would suddenly fail:
That's what I'm looking for.
Where are state methods like display documented by the way?
Nowhere at the moment. SugarCube's API docs were generally meant to document the differences between it and the old vanilla headers. Times change, however, and putting more of the APIs into the docs is on my TODO list (in which case state.display(), which is part of the History prototype, would be found in the story API docs).