Thanks for the new DLL Damien.
In your email you say that you get MAVs with this layout -
So what exactly is it causing the MAV? Is it the UpdateVehicle function using the global veh.vehicle or is it something else?
I've checked through my code and all my FOR..EACH loops just work upon the type within the loop, ie. they don't call another function with the instance of the type as a parameter, so would I have the same problem as you?
If so, why doesn't it MAV all the time? Why just on XP in non-compat. mode? Very odd.
In your email you say that you get MAVs with this layout -
For veh.vehicle=each vehicle ;blah blah here Updatevehicle(veh) ;This function uses the Veh.Vehicle inside, but its not set to local, so it disrupts the for loop. next ;I get MAV here because my VEH.vehicle has been changed by Updatevehicle.
So what exactly is it causing the MAV? Is it the UpdateVehicle function using the global veh.vehicle or is it something else?
I've checked through my code and all my FOR..EACH loops just work upon the type within the loop, ie. they don't call another function with the instance of the type as a parameter, so would I have the same problem as you?
If so, why doesn't it MAV all the time? Why just on XP in non-compat. mode? Very odd.