Timelapse, in general, changes the displayed image both when changing to a more restrictive filter and when changing back to a more permissive filter. However, with most filters the filter and current image index are saved at shutdown so the user returns to that same view on the image set the next time it's opened. This does not occur with custom filters as the custom settings are dropped at shutdown, the filter reverted to all, and the image index left unchanged. So when the user reopens the image set they're now on a different image, often much "earlier" in the image set. This is particularly annoying with date based custom filters as, by losing track of the current image, Timelapse also loses track of an appropriate default value for the custom filter's date/time if the user needs to recreate the filter.
The minimum fix to get consistent behaviour is to persist custom filter settings in the image set table.
It would probably also be nice to retain the current image in general, when possible. ColumnTuplesWithWhere.SetWhere(string, string, string) provides some support for this but rationalizing the image selection methods in TimelapseWindow to take advantage of it is a somewhat involved change.
Timelapse, in general, changes the displayed image both when changing to a more restrictive filter and when changing back to a more permissive filter. However, with most filters the filter and current image index are saved at shutdown so the user returns to that same view on the image set the next time it's opened. This does not occur with custom filters as the custom settings are dropped at shutdown, the filter reverted to all, and the image index left unchanged. So when the user reopens the image set they're now on a different image, often much "earlier" in the image set. This is particularly annoying with date based custom filters as, by losing track of the current image, Timelapse also loses track of an appropriate default value for the custom filter's date/time if the user needs to recreate the filter.
The minimum fix to get consistent behaviour is to persist custom filter settings in the image set table.
It would probably also be nice to retain the current image in general, when possible. ColumnTuplesWithWhere.SetWhere(string, string, string) provides some support for this but rationalizing the image selection methods in TimelapseWindow to take advantage of it is a somewhat involved change.