From e40ad68b9b31c62c1a507f5f31d3da660f42bf66 Mon Sep 17 00:00:00 2001
From: Your Name <room3dev@gmail.com>
Date: Fri, 26 Dec 2025 23:30:21 +0700
Subject: [PATCH] Fix progress bar update logic

---
 save_webp_sequence.py | 13 +++++--------
 1 file changed, 5 insertions(+), 8 deletions(-)

diff --git a/save_webp_sequence.py b/save_webp_sequence.py
index a32ae75..6312702 100644
--- a/save_webp_sequence.py
+++ b/save_webp_sequence.py
@@ -122,15 +122,12 @@ class BatchSaveImageSequenceWebP:
                 if skip_identical:
                     seen_hashes[h] = path
                 
-                # Update pbar immediately for "processed" tasks, 
-                # strictly speaking, we should update when future is done, 
-                # but for UX responsiveness it's often fine to update on submission 
-                # OR we iterate futures differently. 
-                # Let's simple update here as we 'processed' the decision to save.
-                pbar.update(1)
-            
             # Wait for all to finish ensuring files are properly closed
-            for f in futures:
+            # Update pbar as tasks complete
+            from concurrent.futures import as_completed
+            for f in as_completed(futures):
+                pbar.update(1)
+                # Check for exceptions
                 f.result()
 
         return (saved_paths,)