Just wanted to let everyone know - so if we enter test mode, check our game out, then get back to the editor, change a few things and press Ctrl-T it will prompt us to save and then run the game. Right? Not so. Or rather, not so if your only change was to the global script. If you change only the global script (minor adjustements, it seems), it won't prompt you to save, ergo it will use the previous exe in the Complied directory, ergo whatever went wrong before will still go wrong and you'll get crazy trying to figure out why THAT didn't fix it.
Just thought y'all should know.
hmm, for me it saves all properly (v2.56d)
I just added some code then ctrl+t. All works.
btw, are you sure that you saved the script?
Perfectly sure. I had to delete the exe file before it worked.
BTW, here's exactly what happened - I had a certain mesage display on a certain mouse click, and when I tested the thing, it said the string contained illegal characters. Fair enough - I must have been distracted, and instead of typing ' , I typed ´ , which ain't an SCI character. THEN I tested, without bothering to save (it always saves automatically, after all, and I've disabled the CONFIRM prompts), and the same mistake happens again. Just to be sure, I assigned the correct message to a keycode, F2, which previously housed an input box. And when I test the game (once again, assuming it'll save for me), and press F2, the input box comes on! And for the next minute and a half I go crazy, switching between the scripteditor (which, by the way, is NOT the default - but at some point I DID switch back to the default, and no help there) and the game. I even scanned the global script for the text in the input box that kept showing up. I was sure it had been deleted! And it had, but still it showed! I had to delete everything in my Compiled folder and restart AGS.
Oh well, *sigh* maybe it was one of those once-in-a-lifetime glitches.
I just tested it out and it worked fine.
Strange though, you didn't exit the script editor without saving changes or anything?
Nope. As I said, I switched back and forth, and all the time the script said one thing, and the game said another, which shouldn't have been there anymore.
I'm terribly afraid of sticking my foot in my mouth again, like the time about that walking "problem", but I really don't see what it was all about this time.
Then again, this all may very well be useless - I've corrected the problem, and anyway, I'm not sure I could replicate it.
I got something like this with some older version.. I just selected File -> Save Game, then tested, and it works fine...
In this case, saving didn't work. I had to delete the exe.
Well, it's good to know I'm not the only one...
Wait a sec, you said older version? How old? This has happened to me with 2.56c.
2.54 and/or 2.55... My memory ain't the best here... :P