widgets: Clarity whether spinner max is inclusive or exclusive

Currently the spinner uses exclusive max when wrapping from low to high
and inclusive max when wrapping from high to low. Fix this by adopting
*inclusive* max everywhere. The call sites are similarly confused.

Fix this!

Signed-off-by: Daniel Thompson <daniel@redfelineninja.org.uk>

wasp/apps/alarm.py

@@ -58,8 +58,8 @@ class AlarmApp():
     def __init__(self):
         """Initialize the application."""
         self.active = widgets.Checkbox(104, 200)
-        self.hours = widgets.Spinner(50, 60, 0, 24, 2)
-        self.minutes = widgets.Spinner(130, 60, 0, 60, 2)
+        self.hours = widgets.Spinner(50, 60, 0, 23, 2)
+        self.minutes = widgets.Spinner(130, 60, 0, 59, 2)
 
         self.hours.value = 7
         self.ringing = False

wasp/apps/timer.py

@@ -62,7 +62,7 @@ class TimerApp():
     def __init__(self):
         """Initialize the application."""
         self.minutes = widgets.Spinner(50, 60, 0, 99, 2)
-        self.seconds = widgets.Spinner(130, 60, 0, 60, 2)
+        self.seconds = widgets.Spinner(130, 60, 0, 59, 2)
         self.current_alarm = None
 
         self.minutes.value = 10

wasp/widgets.py

@@ -386,7 +386,7 @@ class Spinner():
         self.value = mn
 
     def draw(self):
-        """Draw the slider."""
+        """Draw the spinner."""
         draw = watch.drawable
         im = self._im
         fg = draw.lighten(wasp.system.theme('ui'), wasp.system.theme('contrast'))
@@ -417,7 +417,7 @@ class Spinner():
             else:
                 self.value -= 1
                 if self.value < im[2]:
-                    self.value = im[3] - 1
+                    self.value = im[3]
 
             self.update()
             return True