| 91b47c64e1ca8323f01633c0e890c9d6bc3f605e |
|
26-Oct-2010 |
Georg Brandl <georg@python.org> |
Fix import.
/external/python/cpython3/Tools/pynche/pyColorChooser.py
|
| bf82e374ee737992235cbe944c9ddbd58236a892 |
|
16-May-2008 |
Georg Brandl <georg@python.org> |
More 2to3 fixes in the Tools directory. Fixes #2893.
/external/python/cpython3/Tools/pynche/pyColorChooser.py
|
| d91085598f5185b267ea51a3f615da9527af2ed2 |
|
17-Mar-2006 |
Neal Norwitz <nnorwitz@gmail.com> |
Remove apply()
/external/python/cpython3/Tools/pynche/pyColorChooser.py
|
| 698c14936a2f933c709ea3b412af16478ba8594d |
|
10-Jul-2001 |
Barry Warsaw <barry@python.org> |
Update a comment.
/external/python/cpython3/Tools/pynche/pyColorChooser.py
|
| 74a7ece9f3b56d82ffc11a31307f3ad1382adb97 |
|
01-Feb-2001 |
Barry Warsaw <barry@python.org> |
Move the "from Tkinter import *" out of the method and into the module
scope (still inside the __name__=='__main__' guard). Necessitated by
recent addition of nested scopes.
/external/python/cpython3/Tools/pynche/pyColorChooser.py
|
| 80d83e38ab8000bfcfcb92a1b228b143a8f7b231 |
|
27-Apr-1999 |
Barry Warsaw <barry@python.org> |
askcolor(): databasefile and wantspec can now be set on every
invocation, instead of just the first.
/external/python/cpython3/Tools/pynche/pyColorChooser.py
|
| 61ba0721db1d3f31beb6a04dd8983114d1ee9d5b |
|
26-Mar-1999 |
Barry Warsaw <barry@python.org> |
Removed unnecessary import `from PyncheWidget import PyncheWidget'
/external/python/cpython3/Tools/pynche/pyColorChooser.py
|
| 2be858230a1253b773a7e0d004ac84fae785d8b9 |
|
22-Oct-1998 |
Barry Warsaw <barry@python.org> |
__init__(): Removed initialcolor keyword.
show(): added color keyword here so that the selected color can be
chosen on each invocation of askcolor().
Also fixed this class, and askcolor() so that the same Chooser
instance can be re-used instead of creating a new one on each
invocation of askcolor().
Added a module function save() which can be used to explicitly save
the option database in ~/.pynche. This does not happen automatically
when used as a modal.
/external/python/cpython3/Tools/pynche/pyColorChooser.py
|
| a20f6af8627228fd52701310f85874c5edbf9966 |
|
22-Oct-1998 |
Barry Warsaw <barry@python.org> |
Chooser.__init__(): Added `wantspec' keyword to conform exactly to
tkColorChooser.askcolor() interface (i.e. don't return a color name
even if there is an exact match).
/external/python/cpython3/Tools/pynche/pyColorChooser.py
|
| ca07ba00acdd020e0c179277ed829a8ce1664245 |
|
22-Oct-1998 |
Barry Warsaw <barry@python.org> |
Many changes to support a second mode of operation. Pynche can now be
run either as a standalone application (by running pynche or
pynche.pyw), or as a modal dialog inside another application. This
can be done by importing pyColorChooser and running askcolor(). The
API for this is the same as the tkColorChooser.askcolor() API, namely:
When `Okay' is hit, askcolor() returns ((r, g, b), "name"). When
`Cancel' is hit, askcolor() returns (None, None).
Note the following differences:
1. pyColorChooser.askcolor() takes an optional keyword `master'
which if set tells Pynche to run as a modal dialog. `master'
is a Tkinter parent window. Without the `master' keyword
Pynche runs standalone.
2. in pyColorChooser.askcolor() will return a Tk/X11 color name as
"name" if there is an exact match, otherwise it will return a
color spec, e.g. "#rrggbb". tkColorChooser can't return a
color name.
There are also some UI differences when running standalone vs. modal.
When modal, there is no "File" menu, but instead there are "Okay" and
"Cancel" buttons.
The implementation of all this is a bit of a hack, but it seems to
work moderately well. I'm not guaranteeing the pyColorChooser.Chooser
class has the same semantics as the tkColorChooser.Chooser class.
/external/python/cpython3/Tools/pynche/pyColorChooser.py
|