Leak_Technologies/VideoTools
Leak_Technologies/VideoTools
2
1
Fork 1
Code Issues 3 Pull Requests Actions Packages Projects Releases Wiki Activity

Fix Fyne threading error by using async Do() instead of DoAndWait()

Browse Source 
The setContent function was calling fyne.DoAndWait() from the main goroutine,
which created a deadlock. Changed to use fyne.Do() (asynchronous) to properly
marshal UI updates without blocking.

This resolves the error:
  'fyne.Do[AndWait] called from main goroutine'

The async approach is correct here since we don't need to wait for the
content update to complete before continuing.
This commit is contained in:
Stu Leak 2025-11-29 20:25:57 -05:00
parent 4f68fe39f8
commit 3e0d30d425
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
main.go
View File

@ -346,8 +346,8 @@ func (s *appState) setContent(body fyne.CanvasObject) {
s.window.SetContent(container.NewMax(bg, body)) s.window.SetContent(container.NewMax(bg, body))
} }
// Always marshal content changes onto the Fyne UI thread // Use async Do() instead of DoAndWait() to avoid deadlock when called from main goroutine
fyne.DoAndWait(update) fyne.Do(update)
} }
// showErrorWithCopy displays an error dialog with a "Copy Error" button // showErrorWithCopy displays an error dialog with a "Copy Error" button