This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author gpolo
Recipients gpolo, loewis, pysquared
Date 2008-06-26.16:57:36
SpamBayes Score 0.052935045
Marked as misclassified No
Message-id <ac2200130806260957m7b816207m184455e0f37d00f8@mail.gmail.com>
In-reply-to <1214496147.0.0.36105157946.issue1774370@psf.upfronthosting.co.za>
Content
On Thu, Jun 26, 2008 at 1:02 PM, Graham Horler <report@bugs.python.org> wrote:
>
> Graham Horler <grahamh@users.sourceforge.net> added the comment:
>...
> When you create a Checkbutton widget without giving a variable=SomeVar,
> a default variable is created which Tkinter does not give you easy
> access to.

I'm aware of that and that is why everywhere I see Checkbutton being
used I see a explicit variable being created.

> ...
> What do you mean by "add it to all the other widgets that play with it"?
>

I was referring to the other widgets that accepts *variable options.
Ideally I would to prefer to never need to instantiate Variable or any
of its subclasses, adding methods at the correct places. So what I
meant was to add this functionality everywhere it would cause some
benefit, not only for Checkbutton.
History
Date User Action Args
2008-06-26 16:57:38gpolosetspambayes_score: 0.052935 -> 0.052935045
recipients: + gpolo, loewis, pysquared
2008-06-26 16:57:37gpololinkissue1774370 messages
2008-06-26 16:57:36gpolocreate