JoePfeiffer 724cd3f5dc Don't set a warning if recovery device is deployed (for instance, due to apogee detect) while motor is coasting.
Background:  a motor that has burned out can be in one of two states:  DELAYING (the delay charge has not yet fired) or SPENT (either the delay charge, if any, has fired or there was no delay charge).

The existing SimulationStatus:getActiveMotors() method returned a list of motors that were active for the stage, and which were not SPENT.  The test for the warning redudantly tested for a SPENT motor, still didn't test for a DELAYING motr, and consequently set the warning.

This PR
(1) adds a boolean MotorClusterStatus:isDelaying() method, analogous to the existing state test methods

(2) modifies SimulationStatus.java:getActiveMotors() to return all the motors, not just the ones that aren't SPENT.  This is to improve consistency with FlightConfiguration:getActiveMotors(), and to make for a more consistent usage between the two calls to the method.

(3) adds !isDelaying() to the test for the warning.
2020-08-30 11:18:57 -06:00
..
2016-09-27 08:10:59 -05:00
2012-01-08 02:23:06 +00:00
2012-12-16 00:12:44 -08:00
2016-09-27 08:10:59 -05:00
2013-04-16 22:55:01 +03:00
2012-08-04 08:46:33 +00:00