In Sub GPSGetBuffer you can access GPS(0) as the compiler knows that it is now a byte array because the assignment is in that Sub. The IDE and legacy compilers, being interpreted, can cope with arrays changing type at runtime, the optimising compiler can't, it tries but often fails causing strange problems like this - if indeed that is what the problem is. Look at post #2 here I suspect this is your problem with the optimising compiler. GPS() should be defined as a Byte array because that is what Serial2.InputArray returns. NET Char is a 16bit Unicode character, a Byte is an 8bit value. Msgbox("You have become disconnected from the GPS")Ĭlick to expand.Yes, a. GPSBufferLength = ArrayLen(GPS()) 'Not always the same as i ! I = gps(0) 'DEBUG This does not cause a crash. ' Returns the character count in the buffer (0 if none available) Msgbox("Error in GPSGetChar (" & j & ")") If i Chr(0) Then ok = True ' Ignore nulls I = Chr(GPS(GPSBufferPointer)) '(original line) J = ArrayLen(GPS()) & " " & GPSBufferPointer If GPSBufferPointer >= GPSBufferLength Then 'Returns the next character from the GPS, or chr(0) if none available (It appears that something to do with the pointer for the array GPS has gone awry.
Oziexplorer runtime error code#
As always, it could always be something in my programme writing where it shouldn't, but here is the code including the debugging bits in case you have any ideas: I have added debugging bits to the code, and it appears that something is getting written over that shouldn't.
There were no troubles under 6.3 of basic4ppc, but thr programme crashes under 6.5. (2) I am using serial2, having not known about your serialEx.
Oziexplorer runtime error .dll#
dll required seems to exist on the PDA, but not on the PC, which adds to the interest of debugging!
0 kommentar(er)
