From 13487ff7630851f0b9105d3eb97c96da47ec95dd Mon Sep 17 00:00:00 2001 From: Ben Peddell Date: Sat, 4 Oct 2025 21:58:21 +1000 Subject: [PATCH] [Bugfix] Fix EDDN queue not processing at startup Workaround the `.after()` queue being cleared (or invalidated) when the widget that call was made through is destroyed after that call is made, which in this case resulted in the EDDN queue not being processed until some other action re-triggered processing of the EDDN queue. --- plugins/eddn.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/plugins/eddn.py b/plugins/eddn.py index 39ecf147..028c29c5 100644 --- a/plugins/eddn.py +++ b/plugins/eddn.py @@ -183,7 +183,7 @@ class EDDNSender: f"First queue run scheduled for {self.eddn.REPLAY_STARTUP_DELAY}ms from now" ) if not os.getenv("EDMC_NO_UI"): - self.eddn.parent.after(self.eddn.REPLAY_STARTUP_DELAY, self.queue_check_and_send, True) + self.eddn.parent.winfo_toplevel().after(self.eddn.REPLAY_STARTUP_DELAY, self.queue_check_and_send, True) def sqlite_queue_v1(self) -> sqlite3.Connection: """