When a large or spacious amount of text displays all at once, Quest has a nifty little underplayed feature in which the text shown in the window is fixed with the top being the last command you entered, which is logical and nine times out of ten, is exactly what you would hope for.

However, I've got a little function in which text is constantly being displayed: a timer is counting down, sometimes two at once (the situation is hectic and it's supposed to feel that way, and this does a good job of that; hopefully without being overwhelming). Unfortunately, as waiting is part of the challenge, the nifty little snap feature hinders you here: once the text reaches the bottom of the screen it keeps going, but you're still looking at exactly what fits on your screen with your last command at the top.

tl;dr I would like to know if there's a way to turn off the window snapping that keeps you from following the text to its end; preferably in-game so that it could be turned back on, but I'll find work arounds if not.

Thanks, everybody!

This looks like the timer problem which can be found in the issue tracker for Q5.5.

Actually Pertex it sounds to me like a different issue - it's not related to the problems running frequent timers when playing via the web.

I think one problem here is that the text will scroll to the top of the last command, even if the user has already below that. So that's a bug that should be looked at. The other thing is that it would probably be a good idea to have a script command to force the text to scroll to the end - that way you could keep adding countdown text without the user having to scroll manually.

I'll add these to the issue tracker.

I think it should be quite simple to work around the issue, by manually calling the JavaScript function "markScrollPosition" when writing the countdown text.

It looks like I've encountered another bug that was pointed out in this post: http://www.textadventures.co.uk/forum/viewtopic.php?f=10&t=3403#p22358

It doesn't seem to recognize markScrollPosition when I try to call it.

Thanks again, you guys!

It's a JavaScript function so you need to call it like this:

request (RunScript, "markScrollPosition")

See http://quest5.net/wiki/Using_Javascript

Perfect! Works like a charm.

I suspected having no understanding of JavaScript had something to do with it. Call it fixed.