From 56709a077a37ca2337793a5653f0988742ed4ca0 Mon Sep 17 00:00:00 2001
From: Joe Bacal <bacalj@gmail.com>
Date: Fri, 16 Aug 2024 15:37:57 -0400
Subject: [PATCH] restore state setters that are triggering table "glitch"

---
 src/grasp-seasons/components/seasons.tsx | 13 +++++--------
 1 file changed, 5 insertions(+), 8 deletions(-)

diff --git a/src/grasp-seasons/components/seasons.tsx b/src/grasp-seasons/components/seasons.tsx
index d9f1ab2..7f53e16 100644
--- a/src/grasp-seasons/components/seasons.tsx
+++ b/src/grasp-seasons/components/seasons.tsx
@@ -201,7 +201,7 @@ const Seasons: React.FC<IProps> = ({ lang = "en_us", initialState = {}, log = (a
   const handleLatSliderChange = (event: any, ui: any) => {
     setSimState(prevState => ({ ...prevState, lat: ui.value }));
     setLatitude(formatLatLongNumber(ui.value));
-    // setLocationSearch("");
+    setLocationSearch("");
   };
 
   const handleLatInputChange = (event: ChangeEvent<HTMLInputElement>) => {
@@ -211,17 +211,14 @@ const Seasons: React.FC<IProps> = ({ lang = "en_us", initialState = {}, log = (a
 
   const handleLatIncrement = (increment: number) => () => {
     setSimState(prevState => ({ ...prevState, lat: prevState.lat + increment }));
-    // TODO: commenting these out prevents the "glitch"
-    // but lets test other examples of these being called and see if they are glitchy
-    // there might be something circular going on?
-    //setLatitude(formatLatLongNumber(simState.lat + increment));
-    //setLocationSearch("");
+    setLatitude(formatLatLongNumber(simState.lat + increment));
+    setLocationSearch("");
   }
 
   const handleLongSliderChange = (event: any, ui: any) => {
     setSimState(prevState => ({ ...prevState, long: ui.value }));
-    //setLongitude(formatLatLongNumber(ui.value));
-    //setLocationSearch("");
+    setLongitude(formatLatLongNumber(ui.value));
+    setLocationSearch("");
   };
 
   const handleLongInputChange = (event: ChangeEvent<HTMLInputElement>) => {