FMSC-Measurements / FScruiser

0 stars 0 forks source link

Allow each device to store its own sampling state #17

Open BenCamps opened 5 years ago

BenCamps commented 5 years ago

With the changes being made to the process of working with cruise file on multiple devices, moving away from the requirement that individual component files need to be created for each device specifically, and allowing users to create copies as needed. The issue of managing the sampling state and maintaining the integrity of the sample selection needs to be addressed.

The proposed solution is to allow the cruise file to store multiple sampling states, one for each device that is using the file. That way when data from all copies of the file are combined the sampling state for all the devices using the file is retained.

When the user starts cruising with a file on their device the application will look to see if a sampling state already exists for that device. If there are no sampling states the app will automatically create one and associate it with the device. If no sampling state exists for the current device but there is one for another device, the app will give the user the option to create a copy of an existing sampling state or start fresh. If a sampling state exists associated with the current device the app will automatically use it for sampling.