PDA

View Full Version : PIDE error doubleclicking runtime error line in debug log


zehlein
11-02-2006, 10:47 AM
when my program produces a runtime error and i doubleclick the according line in the debuglog window at the bottom of the screen PIDE gives me the error message '1)' is not a valid integer value. I guess it should jump to the right line in the sourcecode instead. Any idea?

kornalius
11-02-2006, 03:45 PM
Please post the whole line of the error message. I will make it work.

zehlein
11-02-2006, 04:00 PM
A message window pops up and tells:

'1)' is not a valid integer value

Nothing more. Ah, and the error occured at some (23,11) sourcecode position. Can't reproduce it anymore but I thought it looked like a wrongly processed string PIDE couldn't handle.

kornalius
11-02-2006, 06:05 PM
Runtime errors line work fine here. It goes to the source code line in error if I double-click.

I need the exact error message line in order to work.

I made a small change to the code that might help correct this issue but again I am not sure.

What OS language are you using?

zehlein
11-02-2006, 06:19 PM
I use german XP SP2. Sorry I can't provide the exact error message line, I fixed the error and can't remember what it was. I try to force another runtime error and get back to you.

kornalius
11-02-2006, 06:42 PM
k thanks.

zehlein
11-03-2006, 01:37 PM
So here we go...

encountered the error again while doubleclicking the runtime error line:


-- Content of debuglog.txt --

03.11.2006 02:31:58 : Generated by the PPL interpreter v.1.06 Pro
03.11.2006 02:31:58 : Root D:\Programme\PPL\Runtime\
03.11.2006 02:31:58 : Available memory 93,450,240 bytes
03.11.2006 02:31:58 : TESTGAMEAPI.PPL started
03.11.2006 02:32:05 : ** runtime error ** (GameAPI.ppl) (SHUTGAMEAPI(1,0))
Access violation at 0xa80947 (152,3)

03.11.2006 02:32:08 : TESTGAMEAPI.PPL ended (10,065 ms)
03.11.2006 02:32:08 : Available memory 92,553,216 bytes

This time the message tells that: '0)' is not a valid integer value.
Hope that helps!

... and off trying to find out what went wrong... !ill

kornalius
11-03-2006, 04:46 PM
Thanks will look into it.

kornalius
11-03-2006, 07:03 PM
This is now fixed in version 1.07.