Quest 4.01 is now available for download.

The easiest way to update is to launch Quest, click Help and then select "Check for Updates".

This release fixes a number of minor bugs in Quest and QDK:

Quest

- Improved compatibility with JAWS and Window-Eyes screen readers. When either of these is detected, all text is spoken through the screen reader, instead of SAPI.
- Fixed bug where games for Quest 2.x wouldn't work properly.
- Fixed problem loading MP3 files from locations other than the Quest folder.
- Fixed run-time error when the Object Debugger was minimised.
- Fixed run-time error when an invalid array index was specified.
- Fixed bug where specifying the "normal" parameter for the "exec" command would still process user-defined commands and verbs.
- If an infinite loop is created by an "exec" command calling itself, Quest no longer fails with a run-time error (stack overflow). Instead the loop is halted when the stack is full.
- When loading a game, Quest no longer calls the game start room before loading the QSG save data. This was usually not noticeable, but caused problems if the start room contained a script that prompted for user input, or checked string variables etc.
- Properties and flags set in a start room script were not being saved.
- Embedded CAS resources wouldn't work the second time they were called.
- In v3 (and earlier) games that didn't implement an open, close, put, add or remove command, no error message was printed when the player used these commands.

QDK

- If you save a game before setting a start room, QDK now automatically sets the start room to the first room that has been set up.
- script lines longer than 1024 characters were being truncated when they were edited.
- a run-time error occurred if you tried to run QDK at a resolution of 800x600.
- clicking the Edit button on the Rooms, Objects, Verbs or Commands list when no item was selected would cause a run-time error.
- room afterturn scripts weren't being loaded properly.
- a run-time error occurred if you dragged the splitter too far to the right of the screen.
- a run-time error occurred when trying to open an ASL file that contained a duplicated object name.
- when moving a room, the objects contained within it did not move on the treeview.

Holy sh*t dude. You wasted no time! Congratulations! And thanks alot.

for a minor upgrade that's a lot of work!
Congrats Alex

Alex! Under "Pictures and Sounds" the last option "Show an animated GIF with persistent frames" doesn't allow me to click on it. When pointer hovers over it, it highlights with a yellow background, but can't be clicked. Is there a reason this option is disabled? --- QDK Lite 4.01

Strange... it works for me. I can't think of any reason why it would be disabled. Does the problem also occur with other long commands, such as "Other>Execute a command as it if were typed by the player"?

Stretch Scrip Editor window so whole command name shows (enabled).
Condense Script Editor window so whole command doesn't show (disabled).

An animation runs fine in my Animation Editor (JASC) and when inserted into a web page, but when Quest displays it, the first frame appears fine, but thereafter every frame is screwed up. The background color turns to the grey color of the picture box and the frames bleed together. This is in non-persistent mode. I'm guessing it has something to do with how the original file is condensed to minimize file size. What experience do you have in this matter Alex?

What exactly is supposed to happen when an overflow is stopped in the newest version? (My tests revealed Quest just halting, giving no apparent cause.)

An animation runs fine in my Animation Editor (JASC) and when inserted into a web page, but when Quest displays it, the first frame appears fine, but thereafter every frame is screwed up. The background color turns to the grey color of the picture box and the frames bleed together. This is in non-persistent mode. I'm guessing it has something to do with how the original file is condensed to minimize file size. What experience do you have in this matter Alex?

Yes, it's probably the way the frames are set up in the file. The animated GIF code is unfortunately a bit clunky. Could you please send the GIF to me so I can take a look?