richardbunt/Telemachus — pull request #21 by evanova (2014-09-04 22:18:25+00:00)
Title: Fix issue #16: use inverseStage instead of inStageIndex: Staging.current...

This fixes issue #16 (current resource is always 0).

Staging.CurrentStage contains the stage index as shown in the UI (from N to 0) and the Part.inStageIndex is actually -1 or 0, but never matches a stage index. The fix is to use Part.inverseStage.