From 87ebd4bc76c85cd0f954b0e39c2e2757abff6b48 Mon Sep 17 00:00:00 2001 From: James Barnett Date: Tue, 29 Aug 2017 12:21:38 +0100 Subject: Add CPU utilisaiton indicator mode --- NucLedController/FadeColourCyclerControlMode.cs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'NucLedController/FadeColourCyclerControlMode.cs') diff --git a/NucLedController/FadeColourCyclerControlMode.cs b/NucLedController/FadeColourCyclerControlMode.cs index ba982ca..9beed18 100644 --- a/NucLedController/FadeColourCyclerControlMode.cs +++ b/NucLedController/FadeColourCyclerControlMode.cs @@ -39,7 +39,7 @@ namespace NucLedController private void Tick(object source, ElapsedEventArgs e) { - LEDController.SetLEDState(LEDTransition.AvailableTransitions.Find(t => t.Identifier.ToString() == "ALWAYS_ON"), LEDColour.AvailableColours.ElementAt(currentColourIndex), currentBrightness); + LEDController.SetLEDState(LEDTransition.getLEDTransition("ALWAYS_ON"), LEDColour.AvailableColours.ElementAt(currentColourIndex), currentBrightness); // TODO more of the fade duration should be spent at the lower brightness levels, since the perceived change in brightness is much more apparent at the bottom end. // e.g. the perceived difference between 0x10 and 0x20 is much larger than 0x50 and 0x60, so scaling up linearly wastes a lot of time increasing imperceivable brightness changes at the top of the range. -- cgit v1.2.3