I have been using Quest 4.0 and I am finding it to be very time saving when compared with 3.53. However I have found something that might want to be addressed in the next addition.

When you create a flag 4.0 remembers it in a handy pull down menu for easy use later (thank GOD for that, big improvement). However, the pull down menu makes everything lowercase and the flags ARE case sensitive.

For example, if you want to have a differant room description for the bathroom you might use a flag. Lets say that after the player enters the bathroom the first time the flag "bathroomD" is turned on. When you are coding, the pull down menu will show you "bathroomd" and you will select it because that is the one you made before. IF you do this, the code will not execute unless you manualy go back in and change "bathroomd" to "bathroomD" yourself. (or you could change the first code, either way something has to be changed).

This is a rather minor thing but I thought I would bring it up.

Thanks,
Dr.Froth

Did Alex ever say which parts of Quest are case-sensitive?

I do not remember reading anything about what parts are case-sensitive...
but that does not mean that they are not there.

Various parts I've seen are case sensitive..
Some define blocks are/were peculiarly case sensitive (so you can't have 'Define game'... But perhaps 'define Game')

I didn't think flags would be - as variables aren't IIRC.
Usually I keep them mostly lower case anyway.. Much nicer that way.

Flags shouldn't be case sensitive, but I will take a look into this.

Quest should be entirely case insensitive for everything that appears inside a < parameter >.

Keywords are case sensitive though - "define game", "set numeric" etc. should all be lower case. This is mentioned here: http://www.axeuk.com/quest/developer/do ... ngnote.htm

I've had a look into this and can't reproduce a problem. Flags can be set, unset and checked and it doesn't matter what case you use.

Can you please send me an example file showing the problem?