Sorry your browser is not supported!

You are using an outdated browser that does not support modern web technologies, in order to use this site please update to a new browser.

Browsers supported include Chrome, FireFox, Safari, Opera, Internet Explorer 10+ or Microsoft Edge.

AppGameKit Classic Chat / Possible bug! Unrecognised instruction 0 in at line 0

Author
Message
CJB
Valued Member
20
Years of Service
User Offline
Joined: 10th Feb 2004
Location: Essex, UK
Posted: 20th May 2015 18:11
When trying to run this code in Windows, it crashes with pop-up dialogue error "Unrecognised Instruction 0 in at line 0" - followed by a message in the app window: "Tap/click the screen to exit":



If I replace one of the "Case default" statements, it works fine:



Is this a bug with "CASE DEFAULT"? - The last batch of case statements also includes a CASE DEFAULT but works fine. Very odd.

V2 T1 (Mostly)
Uzmadesign
Markus
Valued Member
20
Years of Service
User Offline
Joined: 10th Apr 2004
Location: Germany
Posted: 20th May 2015 18:48 Edited at: 20th May 2015 18:48
this looks strange, i guess there must be a variable name or not?
EndFunction "Error!"

local ret$ = ""
EndFunction ret$

AGK 108 (B)19 + AppGameKit V2 Beta .. : Windows 8.1 Pro 64 Bit : AMD Radeon R7 265 : Mac mini OS X 10.10 (Yosemite)
CJB
Valued Member
20
Years of Service
User Offline
Joined: 10th Feb 2004
Location: Essex, UK
Posted: 20th May 2015 19:02
changing the final return value from "Error!" to a variable string makes no difference to the error I am getting when I include the first occurrence of "case default" in the code.

Can anyone confirm if the they are also getting the "Unrecognised Instruction" error? I have tried installing 12.0.14b but still get the error.

V2 T1 (Mostly)
Uzmadesign
Paul Johnston
TGC Developer
22
Years of Service
User Offline
Joined: 16th Nov 2002
Location: United Kingdom
Posted: 20th May 2015 20:02
Thanks for the example code, fixed for the next version. The actual bug is that ExitFunction being the final statement of the last case block meant it wasn't handled properly. Adding an additional command after the ExitFunction can be used as a workaround, like so

Login to post a reply

Server time is: 2024-11-25 22:02:25
Your offset time is: 2024-11-25 22:02:25