Guilherme Polo <[EMAIL PROTECTED]> added the comment:
> Graham Horler <[EMAIL PROTECTED]> added the comment:
>
>> I'm aware of that and that is why everywhere I see Checkbutton
>> being used I see a explicit variable being created.
>
> Absolutely the reason for this patch, to get rid of unnecessa
Graham Horler <[EMAIL PROTECTED]> added the comment:
> I'm aware of that and that is why everywhere I see Checkbutton
> being used I see a explicit variable being created.
Absolutely the reason for this patch, to get rid of unnecessary code.
What's not to like?
> I was referring to the other wi
Guilherme Polo <[EMAIL PROTECTED]> added the comment:
On Thu, Jun 26, 2008 at 1:02 PM, Graham Horler <[EMAIL PROTECTED]> wrote:
>
> Graham Horler <[EMAIL PROTECTED]> added the comment:
>...
> When you create a Checkbutton widget without giving a variable=SomeVar,
> a default variable is created w
Graham Horler <[EMAIL PROTECTED]> added the comment:
I referred to the man page, as it says this:
Command-Line Name:-variable ... Defaults to the name of the button
within its parent.
When you create a Checkbutton widget without giving a variable=SomeVar,
a default variable is created which T
Guilherme Polo <[EMAIL PROTECTED]> added the comment:
The checkbutton widget doesn't have get and set commands, so I'm not
sure why you said to look at its man page.
But the idea of not needing to play with SomeVar creation is good, I
like it, but then I would prefer to add it to all the other w
