Axe Software Forums
  Quest Developer Forum
  Nothing really!


Author Topic:   Nothing really!
Computer Whizz posted 27-10-2000 21:03 GMT     
Hey all!
I've been a bit busy lately and so I thought I'd just end my silence with a quick hello!
A greetings to Luca Brazzi!
well that was it really.... I won't say hi to Alex since he's at collage and should be far too busy to look at this! :)
Oh I have had a slight problem with the shell command. it looks OK and in Quest (2.17 AND 3.0) it returns quest.shellsucess as 1.
Can anyone post the code (in raw!) so I can look at the code and correct it!
thanx.

--CW

Luridii posted 04-11-2000 13:55 GMT          
Do you mean you want Quest to return '1' into a numeric variable if it shells something sucessfuly?

'~'

Luridii posted 07-11-2000 19:17 GMT          
If not, what do you mean?
Computer Whizz posted 15-11-2000 21:33 GMT          
sorry, I thought I'd already posted it!
I mean that it wont open the actual file.
It replies with '1' but nothing happens outside of quest! no files opening.. or anything. What I want is to look at the raw coding of the 3-5 lines, to open a file. Then I'll compare it to the code I have and will see if I can correct it.
sorry if it didn't seem clear! I must have posted it earlier on.
anyway TIA..
--CW
Luridii posted 16-11-2000 18:44 GMT          
Code should be:

shell <Filename.gif> for example

If that doesn't work look in Quest's security options to see whether it is not allowing a file type (.exe etc) to run.
On my computer using the shell <...> command will only run something in the same folder Quest is installed in.

That help?

Alex posted 18-11-2000 12:59 GMT          
The shell command *should* be running things from the directory that the game's .asl file lives in. I have had a few problems in the past with the same code that shells things "pretending" to work but patently doing nothing, so I'll take a look into this at some point.

Unfortunately I'm not overwhelmed with time in which I can look into things, but hopefully I'll be able to take a look into these problems (and reply to a few emails which have been sitting around for a few weeks - sorry!) within the next week. Maybe even release Quest 2.18... (but don't hold your breath). Failing that, perhaps Christmas time will see a few smallish updates to Quest, provided I'm not too busy.


Alex Warren,
Axe Software

MaDbRiT posted 21-11-2000 11:47 GMT          
Quest 2.18???

O.K. Alex, you have my attention.. what changes are planned???

Al

Alex posted 21-11-2000 19:26 GMT          
Quest 2.18 has been sitting on my hard disk for a while now and I'll release it soonish after I've checked out a couple more bugs:

Here's the snippet from VERSIONS.TXT:

- One-line multiple "if" statements such as:
if ask <A> then if ask <B> then msg <1> else msg <2>
else msg <3>
were not being executed properly - if the player answered no
to A, B's "else" condition was being executed, and if the
player answered yes to A and no to B, no "else" condition was
being executed.
- Quest would revert to the default font if the text box on the
main window had text selected in it.
- changed the behaviour of "here" - it would previously find the
first object of that name that existed and check if it was in
the current room. As multiple objects in Quest 2.x can have
the same name, it now just checks the current room for an
object of that name. No error is reported if the object
doesn't exist.
- when loading .QSG saved games where multiple objects shared
the same name, all .QSG data would be applied to one object
only, meaning objects weren't in the correct places if they
shared names with other objects.
- clicking a direction button when Quest was waiting for any key
to be pressed caused a run-time error.
- QDK 1.01 now included.

Alex Warren
Axe Software