@Ken - this is great.
What about this case: a new target/event is added after a sequence has already started? Or is that stupidity beyond fixing? 
Also - for folks that have a filter wheel defined, is there a way to warn when no filter (ie. “None”) is selected (before or after a sequence has started)?
Cheers,
DaveNL
I’m not sure how to accomplish a warning in this scenario. Mostly because I’m not sure how to tell if you’re “done” adding it.
I thought we had this one already, but I’ll check.
I suspected that might be the case. How about doing a check at the point a sequence is saved?
You probably do, for pre sequence start. I guess I was thinking more about post sequence start.
Other approach ideas that could help mitigate:
a) Have default value for all fields set to “NOT SET” or similar value and flag in an obvious way (ie. diff colour etc.)
b) Provide a way for users to define their own “default/template” of values for new Events
c) Provide a “validation” button that forces check for “bad” values
I recognize that these suggestions might not be possible, easy or worthwhile spending time on …
Cheers,
Dave