On Sun, 17 Feb 2008 13:31:47 +0100, W. Watson <[EMAIL PROTECTED]>
wrote:
> Thanks very much. I'm somewhat new to this, but I would think that Frame
> might carry some properties not available to the root. If so, then there
> might be some advantage to it.
(Please don't top-post... It makes t
Thanks very much. I'm somewhat new to this, but I would think that Frame
might carry some properties not available to the root. If so, then there
might be some advantage to it.
7stud wrote:
> On Feb 16, 8:40 pm, "W. Watson" <[EMAIL PROTECTED]> wrote:
>> The following two examples are from Grayso
I did run them both, but not simultaneously. They looked the same to me. I
should have probably captured both. I'll check for a small one somewhere.
Francesco Bochicchio wrote:
> On Sat, 16 Feb 2008 19:40:51 -0800, W. Watson wrote:
>
>> from Tkinter import *
>>
>> class App:
>> def __init__
On Feb 17, 9:29 am, Francesco Bochicchio <[EMAIL PROTECTED]> wrote:
>
> Anyway, Tk() already opens a frame, so in the first example the buttons
> are created inside that frame, while in the second example two frames
> are created: the one creaded by Tk() il left empty but you should see it
> (mayb
On Feb 16, 8:40 pm, "W. Watson" <[EMAIL PROTECTED]> wrote:
> The following two examples are from Grayson's book on Tkinter. He's making a
> simple dialog with three buttons. In the first example, he does not use the
> Frame class, but in the second he does. Doesn't the first example need a
> contai
On Sat, 16 Feb 2008 19:40:51 -0800, W. Watson wrote:
> from Tkinter import *
>
> class App:
> def __init__(self, master):
> fm = Frame(master)
> Button(fm, text='Left').pack(side=LEFT)
> Button(fm, text='This is the Center button').pack(side=LEFT)
> Button
The following two examples are from Grayson's book on Tkinter. He's making a
simple dialog with three buttons. In the first example, he does not use the
Frame class, but in the second he does. Doesn't the first example need a
container? What's the difference here?
==5.1
