A subtlety / messy point: "overqueued" warning for gID Status currently only looks at the prep from the Registry that is meant to be used, and if not enough of it is available for queued gIDs, flags them. But what if other mIDs are available to immediately replace that "use for GG" mID? The overqueued warning appears anyway, when there's no problem (a different part source just needs to be substituted for some assemblies). Also, if you queue up a new mID from a stored strain, the g sheet doesn't have any way to acknowledge this (see #95). In general, how the "overqueued" warning is handled should be tightened up.
A subtlety / messy point: "overqueued" warning for gID Status currently only looks at the prep from the Registry that is meant to be used, and if not enough of it is available for queued gIDs, flags them. But what if other mIDs are available to immediately replace that "use for GG" mID? The overqueued warning appears anyway, when there's no problem (a different part source just needs to be substituted for some assemblies). Also, if you queue up a new mID from a stored strain, the g sheet doesn't have any way to acknowledge this (see #95). In general, how the "overqueued" warning is handled should be tightened up.