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 / #include parameter mismatch error

Author
Message
MjG0001
14
Years of Service
User Offline
Joined: 19th Jan 2011
Location: U.S.A. - Indiana - Cedar Lake
Posted: 3rd Feb 2014 07:34
Make sure your press enter at the last line of your included files, so that you have one empty line at the end of them.
easter bunny
12
Years of Service
User Offline
Joined: 20th Nov 2012
Playing: Dota 2
Posted: 3rd Feb 2014 09:05
What happens when you don't...?

BatVink
Moderator
22
Years of Service
User Offline
Joined: 4th Apr 2003
Location: Gods own County, UK
Posted: 3rd Feb 2014 11:14
"Parameter Mismatch" error

Markus
Valued Member
21
Years of Service
User Offline
Joined: 10th Apr 2004
Location: Germany
Posted: 3rd Feb 2014 11:15
@easter bunny
i believe without linebreak it will add wrong
at end of main temp file.

AGK 108 (B)19 : Windows 8.1 Pro 64 Bit : AMD Radeon HD 6670
JimHawkins
15
Years of Service
User Offline
Joined: 26th Jul 2009
Location: Hull - UK
Posted: 3rd Feb 2014 12:17
Without and end-of-line character the last line may no be read. This is not uncommon in reading lines from text files.

-- Jim - When is there going to be a release?
Ancient Lady
Valued Member
21
Years of Service
User Offline
Joined: 17th Mar 2004
Location: Anchorage, Alaska, USA
Posted: 3rd Feb 2014 17:15
If you don't end the include file with a line return, whatever comes immediately after the #include statement is added to the end of the text in the included file. If it isn't a blank line, then it is very likely to cause an error.

If you have two #include lines with no space and the second starts with anything other than a blank line or comment, that will cause strange things to happen.

This bit me in the butt for a couple of days.

All AppGameKit code files should end with a blank line for safety.

Cheers,
Ancient Lady
AGK Community Tester and AppGameKit Master
Naphier
14
Years of Service
User Offline
Joined: 2nd Oct 2010
Location: St Petersburg, Florida
Posted: 4th Feb 2014 18:59
Yup! This got me a few times a couple of times I think it even happened when I did have a new line at the end of the include file, but now I also put a comment at the end //--EOF-- and then a new line. Helped me out a bit.

Phaelax
DBPro Master
22
Years of Service
User Offline
Joined: 16th Apr 2003
Location: Metropia
Posted: 5th Feb 2014 10:41
I guess I've never run into this problem because I never start my files on the first line.

Digital Awakening
AGK Developer
22
Years of Service
User Offline
Joined: 27th Aug 2002
Location: Sweden
Posted: 5th Feb 2014 11:28
I have never run into this issue myself as at the end of all my files there's an end command and that doesn't turn blue in the editor unless there's a blank line at the bottom. So I always add one

Login to post a reply

Server time is: 2025-05-24 11:36:38
Your offset time is: 2025-05-24 11:36:38