Happy new decade everyone!
Interesting enough, removing the "deiconify()" the problem didn't reoccur.
Maybe, not enough people test it, but I am happy that works on windows, linux
and mac
for the moment without the problem.
Vasilis
________________________________________
From: Michael Lange [klappn...@web.de]
Sent: Friday, December 27, 2019 08:20
To: Vasilis Vlachoudis
Cc: tkinter-discuss@python.org
Subject: Re: [Tkinter-discuss] wait_window exception
Hi,
On Wed, 25 Dec 2019 17:04:04 +0000
Vasilis Vlachoudis <vasilis.vlachou...@cern.ch> wrote:
> Thanks Michael
> my best wishes to you too.
> The close method is the following, apart some bookkeeping nothing
> special.
> # ----------------------------------------------------------------------
> def close(self):
> FileDialog._active = False
> FileDialog.width = self.winfo_width()
> FileDialog.height = self.winfo_height()
> FileDialog.sash = [self.fileList.paneframe.sash_coord
> (i)[0] for i in range(len(self.fileList.listboxes())-1)]
> tkExtra.ExListbox.resetSearch()
> self.grab_release()
> self.destroy()
>
> I've realized that the "deiconify()" was creating some problems on
> Windows, so I removed it, and it seems it works better. When I will
> deploy this version I will know after if it still generates problems.
it seems rather odd if actually deiconify() is the culprit here.
Another thought that occurred to me, is the window path name ".!flair.!
configdialog3.!opendialog\" assigned manually? If yes, is it possible
that a second window that tries to go by the same path name interferes
here?
Regards
Michael
.-.. .. ...- . .-.. --- -. --. .- -. -.. .--. .-. --- ... .--. . .-.
If some day we are defeated, well, war has its fortunes, good and bad.
-- Commander Kor, "Errand of Mercy", stardate 3201.7
_______________________________________________
Tkinter-discuss mailing list
Tkinter-discuss@python.org
https://mail.python.org/mailman/listinfo/tkinter-discuss
