I am writing some .net 2.0 applications that query the PicoScope.
One thing I have noticed is the difference in stated integer sizes. For example the manual defines the time_interval pointer for ps3000_get_timebase as a long. However, it only returns a 32 bit integer.
If I try to fit a long (64bit) to stated long function parameters I often get a mismatch error between the managed and unmanaged code, or an attempt to write protected memory error.
As it goes, assigning a int64 to this value does not return an error, but the value returned does not go above 2147483648... which is 32 bits?
Would it be possible for someone to publish the correct byte sizes for the function definitions in the manual.