QDK Acting Strange
Dr.Froth
23 Aug 2006, 22:34OK. Here is a strange problem I have encountered for the first time today.
I am editing in QDK and I am using a conditional for a room description and for some reason right after I click the OK button the command that I entered for a "Print" becomes a "Other Script Command" and no matter how many times I go back and change it, the minute I get out of it the change takes place. What is going on?
I am editing in QDK and I am using a conditional for a room description and for some reason right after I click the OK button the command that I entered for a "Print" becomes a "Other Script Command" and no matter how many times I go back and change it, the minute I get out of it the change takes place. What is going on?
Elexxorine
24 Aug 2006, 13:06I used to get that quite a bit, take it up strongly with Alex - in the mean time try putting in it manually through ASL.
Arbutus
24 Aug 2006, 21:15Not sure why QDK does that. I usually delete the object or room and start over because that works.
witch wyzwurd
25 Aug 2006, 09:09I've experienced other quirks where info would get either changed or lost and have had handled it like elexxorine and Arbutus. I really do suggest that if you plan to take either of those routes, you open your game in a textpad like program and learn to write/fix code that way if possible.
Why these probs happen, I believe is the result of errorful coding. I think what happens is if a line isn't recognizable the editor reads container tags but skips the bad code, so anything afterwards become embraced by previous container tags even if you don't want them to.
This crossed my mind because as I'm getting better at coding, problems are disappearing, and I can't see how the Editor will "choose" to goof up at times and not goof up at others. It must be a direct result of the code being input.
Search your code, I might be right.
W.
Why these probs happen, I believe is the result of errorful coding. I think what happens is if a line isn't recognizable the editor reads container tags but skips the bad code, so anything afterwards become embraced by previous container tags even if you don't want them to.
This crossed my mind because as I'm getting better at coding, problems are disappearing, and I can't see how the Editor will "choose" to goof up at times and not goof up at others. It must be a direct result of the code being input.
Search your code, I might be right.
W.
Dr.Froth
25 Aug 2006, 23:31
You guys are great...as always.
Dr.Froth
GameBoy
26 Aug 2006, 04:52Problems like this have occured in the past, like the time the status variables would screw up unless you fixed it in ASL after.