GameMaker v3.9.93

[Al Staffieri]

GameMaker has been updated to version 3.9.93. You can download the latest update patch from the GameMaker web site at:
http://www.macgamemaker.com

v3.9.93 - 2/08/09
-FIX: There was still a REPEAT bug that caused an error when changing cards from inside a REPEAT loop with GOTOCARD command.
-FIX: A change in the graphics copying routines caused crashes when using Undo menu or the selection tool.

[Silverwind]

Cool, downloading now!

btw, the GM homepage still has 3.9.92 listed as the latest version. Just mentioning it incase you missed it.

EDIT:

That's odd, the download is the 3.9.92 updater for me, and like last time the un-archived folder isn't showing up.

[Al Staffieri]

Go back to the GameMaker web page and hit the refresh button on your browser. It should be the updated page.

[Tireas Dragon]

THANK-YOU SO VERY MUCH NOW I CAN UNDO A MISTAKE!!!!

[Silverwind]

Whilst working on the Supa Pong update I discovered a glitch that only occurs in compiled games. If a REPEAT loop contains an IF THEN condition it returns a Script Error. Also, the Option key won't break out of a REPEAT loop if the REPEAT loop has an ON KEYDOWN block in it. Not that a REPEAT loop should have an ON EVENT block in it mind you, but I just had to try it.

[Al Staffieri]

Whilst working on the Supa Pong update I discovered a glitch that only occurs in compiled games. If a REPEAT loop contains an IF THEN condition it returns a Script Error. Also, the Option key won't break out of a REPEAT loop if the REPEAT loop has an ON KEYDOWN block in it. Not that a REPEAT loop should have an ON EVENT block in it mind you, but I just had to try it.

I'll take a look at those. Thanks.

[Al Staffieri]

If a REPEAT loop contains an IF THEN condition it returns a Script Error.

Have you tried using SELECT CASE for a work around? I should just try it myself.

[Silverwind]

I'll try that right away. *goes to do so*

[Silverwind]

*reappears* Yup, SELECT CASE works. Thanks Al! Once again the day is saved by the ingenuity of a programmer!

[Al Staffieri]

This code works fine when compiled:

Code: [Select]

x = 1
REPEAT 5
  IF x = 3 THEN
    PRINT X = $x$
  ELSE
    PRINT $x$
  END IF
  x = x + 1
END REPEAT

I also tried it without the ELSE

Code: [Select]

x = 1
REPEAT 5
  IF x = 3 THEN
    PRINT X = $x$
  END IF
  PRINT $x$
  x = x + 1
END REPEAT

and I tried it with a single line IF

Code: [Select]

x = 1
REPEAT 5
  PRINT $x$
  IF x = 3 THEN PRINT X = $x$
  x = x + 1
END REPEAT

They all worked. Could there be a different problem in your script?

[Silverwind]

Ah, you're right, it's actually the EXIT REPEAT command that's causing the trouble. Try this in a compiled app:

Code: [Select]

x = 0

REPEAT
  x = x + 1
  IF x = 5 THEN EXIT REPEAT
END REPEAT

ALERT Hello there.

The result for me is that GM stops running the script when it reads the EXIT REPEAT command, thus the ALERT line isn't executed. The glitch occurs regardless to the location of the code, (as in card script, button script, within an ON EVENT condition and so on) and for some strange reason that thing happened again where the app requires OS9 to play. It happened half a dozen times or so and then suddenly stopped happening after I made changes to the code.

Now I'm more baffled than ever.

[Tireas Dragon]

It said you need OS9 to play? That doesn't make any sense I would be so baffled I would die of a disease that my body created by its baffledness.

[Silverwind]

It said you need OS9 to play? That doesn't make any sense I would be so baffled I would die of a disease that my body created by its baffledness.

Yup, that gets my vote for April's Quote of The Month.

[Al Staffieri]

for some strange reason that thing happened again where the app requires OS9 to play. It happened half a dozen times or so and then suddenly stopped happening after I made changes to the code.

Now I'm more baffled than ever.

If that happens, go to File and Get Info. Uncheck the Open in Classic box.

[Al Staffieri]

The result for me is that GM stops running the script when it reads the EXIT REPEAT command, thus the ALERT line isn't executed. The glitch occurs regardless to the location of the code, (as in card script, button script, within an ON EVENT condition and so on)

This was an easy fix. Thanks for pointing it out. All I had to do was delete a single line of code. I'll send you an update soon.