QDK 1.02 bug... and a little library help!

  Axe Software Forums
  Quest Developer Forum
  QDK 1.02 bug... and a little library help!

Author Topic:   QDK 1.02 bug... and a little library help!

Computer Whizz posted 28-07-2001 01:56 GMT
Now, whenever I try and alter an object's misc ASL from within QDK it always comes up with an error box saying:

quote:

Runtime error 424
Object required..
No other information is given! I have only encountered it 3 or 4 times, since now I'm beggining to code by hand (it's a lot more fun then it sounds!! :) ). But I'd still like to be able to do this!
One more note....
Do I HAVE to have the "define variable" in the MAIN game? I've put them into libraries but Q3.0 doesn't seem to read them..... and what about commands? I have an idea about putting the define variable in a procedure.... but I won't try that until tomorrow!
--CW
MaDbRiT posted 28-07-2001 07:32 GMT

quote:
Do I HAVE to have the "define variable" in the MAIN game? I've put them into libraries but Q3.0 doesn't seem to read them..... and what about commands? I have an idea about putting the define variable in a procedure.... but I won't try that until tomorrow!
According to the manual and my own tests- "define variable" blocks MUST go inside a 'define game' block, though I'm pretty sure you are supposed to be able to put them into an 'addto game' block if you want to put them in a library - though I've had no need to do that myself as yet.
Adding commands can be done in the main file's define game block, or any of it's define room blocks OR in a library's addto game block or in any room added within the library should you need to. My elevator lib / vehicle lib and standard lib manage to do all those things at some point so I KNOW it works in Q2.19 and as the files basically work in 3.0 as well, then it seems clear that should be fine.
Al

Alex posted 28-07-2001 11:10 GMT

quote:

whenever I try and alter an object's misc ASL from within QDK it always comes up with an error box saying:
Is this happening for all ASL files or just the one you're working on? I just tried it and it seemed to work OK - perhaps you could send me your ASL file?
As for "define variable" blocks, as Al says these should be in an "!addto game" section of your library because they should appear to Quest to be in a "define game" block.
Computer Whizz posted 28-07-2001 11:52 GMT
Nope.... the QDK error is happening in ALL ASL files....
As for the library help, yes... I kinda figured that out at 1.30 am, by looking into one of Al's libraries :)
What I DO want to understand is why.... suddenly, Quest has stopped working with Arrays!!! My little demo won't work without them!! Whenever I try and use it, Quest comes up with the log file saying "invalid procedure/call ect... the string 'fighter' is not defined!".... I think I need to TOTALLY re-install Quest, I'm going to do that now.. :)
see ya.
--CW
Alex posted 28-07-2001 13:12 GMT
Reinstalling Quest and QDK will rarely help much. Unlike software that comes out of Redmond, QUEST.EXE and QDK.EXE are mostly self-contained - there aren't any weird external files, other than those VB apps require, to go wrong. Reinstalling usually only helps when things have totally gone awry (like Quest or QDK won't load at all), not when you encounter some niggling bug.

Author	Topic: QDK 1.02 bug... and a little library help!
Computer Whizz	posted 28-07-2001 01:56 GMT Now, whenever I try and alter an object's misc ASL from within QDK it always comes up with an error box saying: quote: Runtime error 424 Object required.. No other information is given! I have only encountered it 3 or 4 times, since now I'm beggining to code by hand (it's a lot more fun then it sounds!! :) ). But I'd still like to be able to do this! One more note.... Do I HAVE to have the "define variable" in the MAIN game? I've put them into libraries but Q3.0 doesn't seem to read them..... and what about commands? I have an idea about putting the define variable in a procedure.... but I won't try that until tomorrow! --CW
MaDbRiT	posted 28-07-2001 07:32 GMT quote: Do I HAVE to have the "define variable" in the MAIN game? I've put them into libraries but Q3.0 doesn't seem to read them..... and what about commands? I have an idea about putting the define variable in a procedure.... but I won't try that until tomorrow! According to the manual and my own tests- "define variable" blocks MUST go inside a 'define game' block, though I'm pretty sure you are supposed to be able to put them into an 'addto game' block if you want to put them in a library - though I've had no need to do that myself as yet. Adding commands can be done in the main file's define game block, or any of it's define room blocks OR in a library's addto game block or in any room added within the library should you need to. My elevator lib / vehicle lib and standard lib manage to do all those things at some point so I KNOW it works in Q2.19 and as the files basically work in 3.0 as well, then it seems clear that should be fine. Al
Alex	posted 28-07-2001 11:10 GMT quote: whenever I try and alter an object's misc ASL from within QDK it always comes up with an error box saying: Is this happening for all ASL files or just the one you're working on? I just tried it and it seemed to work OK - perhaps you could send me your ASL file? As for "define variable" blocks, as Al says these should be in an "!addto game" section of your library because they should appear to Quest to be in a "define game" block.
Computer Whizz	posted 28-07-2001 11:52 GMT Nope.... the QDK error is happening in ALL ASL files.... As for the library help, yes... I kinda figured that out at 1.30 am, by looking into one of Al's libraries :) What I DO want to understand is why.... suddenly, Quest has stopped working with Arrays!!! My little demo won't work without them!! Whenever I try and use it, Quest comes up with the log file saying "invalid procedure/call ect... the string 'fighter' is not defined!".... I think I need to TOTALLY re-install Quest, I'm going to do that now.. :) see ya. --CW
Alex	posted 28-07-2001 13:12 GMT Reinstalling Quest and QDK will rarely help much. Unlike software that comes out of Redmond, QUEST.EXE and QDK.EXE are mostly self-contained - there aren't any weird external files, other than those VB apps require, to go wrong. Reinstalling usually only helps when things have totally gone awry (like Quest or QDK won't load at all), not when you encounter some niggling bug.