From a8a48bb809950438139221c7e43f1ee9969b16dd Mon Sep 17 00:00:00 2001
From: vsariola <5684185+vsariola@users.noreply.github.com>
Date: Wed, 10 Feb 2021 13:37:44 +0200
Subject: [PATCH] widget: fix bug how f.pos is calculated in widget.Float

The order of subtraction when calculating f.pos from value was wrong,
so setting a minimum value for a Float never really worked, although
min = 0 worked as intended which is why this probably went unnoticed.

Signed-off-by: vsariola <5684185+vsariola@users.noreply.github.com>
---
 widget/float.go | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/widget/float.go b/widget/float.go
index 8d9c9145..571d5a8e 100644
--- a/widget/float.go
+++ b/widget/float.go
@@ -48,7 +48,7 @@ func (f *Float) Layout(gtx layout.Context, pointerMargin int, min, max float32)
 		f.pos = xy / f.length
 		value = min + (max-min)*f.pos
 	} else if min != max {
-		f.pos = value/(max-min) - min
+		f.pos = (value - min) / (max - min)
 	}
 	// Unconditionally call setValue in case min, max, or value changed.
 	f.setValue(value, min, max)