1  |   Order by index

Apr 25, 2003, 12:57am

The unfortunate thing is really that this kind of situation has not been handled consistantly from version to version, but sometimes that's unavoidable. As it stands right now, in build 481 of the AW 3.4 public beta and in every build I tested all the way baco to build 402 of AW 3.2, you can get away with adding a fake trigger and all the commands you want after it whether they are real or not. Here's an example...

fauxtrigger nonexistantcommand unknown_parameter test=yes ; create texture water1

It used to also be possible to add fake parameters as long as they were set to a value. This could have come in handy if AW 3.0 had supported a mask= parameter with the animate command rather than just a "mask" parameter, because AW 2.x would have ignored that parameter. Ideally, I would think it would be best if eventually you could type in a command any way you want and the parts of it that are understood would work but you would get a warning from the building inspector about any parts that were not understood. This, of course, would not be an AW 3.4 issue, and probably not even an AW 3.5 issue, but in preperation for the ability to add such warnings it would be good if those parts which are valid would work, even if an unknown command comes before them. I'm cross-posting this reply to the wishlist newsgroup, so people can take their pick which newsgroup to follow up in... depending on whether they would like to discuss what really "needs" to be done in AW 3.4, or what they would like to see done eventually.

TechnoZeus

[View Quote]

1  |   Order by index