Thanks Peter. That explained the most.
It is hypothetical at this point, but i imagine changing one variables value will impact the internal simulation state and hence will inturn impact more than one offset's value. Basically, i am thinking about writing a program to handle my overhead logic something like mini pmsystems. I can't think of a perfect example, but say turning off an engine in flight may cause altitude to drop, some overhead annunciators light up etc., So, it is my program, that it should know what all these attributes that can be impacted and read them correct?
Also, in general, if a client program is interested in say 50 offsets, it is upto the client program to decide it's strategy about when and how to read these correct?
As these group of calls are stacked up on the client program before FSUIPC_Process() is called, what is the impact of first writing and then some reads (of variables impacted due to the write call before) following the write call within the same batch? Would client program be able to see the effect of write in the following read calls within the same batch executed through the FSUIPC_Process() call?
thanks and I appreciate.
regards
srini