Re: [Tkinter-discuss] Correct order for dialog display

2010-09-30 Thread Michael Lange
Hi, Thus spoketh Bob Greschke unto us on Thu, 30 Sep 2010 11:06:49 -0400: > The .withdraw() should be right after the statement that creates the > Toplevel window. Creating it, then making the call to this def show() > is giving the system time to make the window visible. If the Toplevel > ()

Re: [Tkinter-discuss] Correct order for dialog display

2010-09-30 Thread Bob Greschke
The .withdraw() should be right after the statement that creates the Toplevel window. Creating it, then making the call to this def show() is giving the system time to make the window visible. If the Toplevel() and the .withdraw() are together the window doesn't show up until the .deiconify().

Re: [Tkinter-discuss] Correct order for dialog display

2010-09-30 Thread Vasilis Vlachoudis
Thank you Michael for the suggestion, I don't understand why you are using the withdraw() before. Now on my linux, it pops up the window (with Tk dimensions) then it remove it and then it displays it correctly with my dimensions. Cheers Vasilis On 09/30/10 11:38, Michael Lange wrote: Hi,

Re: [Tkinter-discuss] Correct order for dialog display

2010-09-30 Thread Michael Lange
Hi, Thus spoketh Vasilis Vlachoudis unto us on Thu, 30 Sep 2010 09:30:27 +0200: > Dear all, > > In my application I have several custom made Toplevel windows when they > close they remember their position and size, so the next time to open > them using with the same geometry. > > Therefor

[Tkinter-discuss] Correct order for dialog display

2010-09-30 Thread Vasilis Vlachoudis
Dear all, In my application I have several custom made Toplevel windows when they close they remember their position and size, so the next time to open them using with the same geometry. Therefore in the show method I have the following sequence def show(self): self.deiconify()