Re: [Tkinter-discuss] Unicode range
04.01.21 11:09, Vasilis Vlachoudis пише: > how can I "replace/strip" unicode characters that are out of the > accepted tk range before inserting them to Text()? > > File "/usr/lib/python3.6/tkinter/__init__.py", line 3272, in insert > self.tk.call((self._w, 'insert', index, chars) + args) > _tkinter.TclError: character U+1c784 is above the range (U+-U+) > allowed by Tcl Upgrade Python. Since 3.7.6 Tkinter supports characters outside of the range U+-U+. ___ Tkinter-discuss mailing list Tkinter-discuss@python.org https://mail.python.org/mailman/listinfo/tkinter-discuss
Re: [Tkinter-discuss] PanedWindow widget
03.03.18 23:13, adil gourinda пише:
print(help(tkinter.PanedWindow.paneconfigure))
print() is not needed here. help() itself prints the description.
I have two questions:
-Does "tagOrId" is the equivalent of "window" in TCL?
Yes, it is.
-What is "cnf" parameter which is present in all Tkinter classes and
methods?
A dict of options. You can specify options either as keyword arguments
paneconfigure(wnd, height=200, width=100)
or as a dict (if you have a variable set of options).
options = {}
options['height'] = 200
options['width'] = 100
paneconfigure(wnd, options)
or even combine both ways
paneconfigure(wnd, options, padx=10, pady=5)
In modern Python this parameter mostly redundant since you can pass a
variable number of keyword arguments as **options.
paneconfigure(wnd, **options, padx=10, pady=5)
This output return the description of two Tcl commands (pathName *sash
coord* index and pathName *sash dragto* index x y) in one Tkinter
methods, is it an error?
This looks like a bug. Please open an issue on https://bugs.python.org/.
___
Tkinter-discuss mailing list
Tkinter-discuss@python.org
https://mail.python.org/mailman/listinfo/tkinter-discuss
Re: [Tkinter-discuss] tcl/tk's syntax to python's syntax
23.10.17 12:27, Michael Lange пише: Actually the widgets' names (as "b" and "f" in the above example) go to the widget's "name" option in Python, which is hardly ever used though (in Tkinter we usually let Python assign the widget names automatically which leads to something that looks like ".1234567890.1234567891" instead of ".f.b"). In Python 3.6 automatically assigned names look more human-readable, e.g. ".!frame2.!button5". ___ Tkinter-discuss mailing list Tkinter-discuss@python.org https://mail.python.org/mailman/listinfo/tkinter-discuss
Re: [Tkinter-discuss] About making Text.tag_*range methods more consistent
09.06.14 09:36, Michael Lange написав(ла): I have encountered similar objects instead of the expected return values from tk methods at what appears to me as random places from time to time with hevery new version for years since the Tkinter developers invented the object layer (sorry, no idea how they actually call it) in Python-2.4 or so. In Python2 you can disable it altogether by setting Tkinter.wantobjects = False early in your code to restore the classic behavior, unfortunately this does not seem to work in Python3 anymore (at least the last time I tried). Probably these objects can easily be converted into strings if you know where they appear. Setting Tkinter.wantobjects = False should work in Python 3 now (at least in 3.3+). If this doesn't work, please report a bug. ___ Tkinter-discuss mailing list Tkinter-discuss@python.org https://mail.python.org/mailman/listinfo/tkinter-discuss
Re: [Tkinter-discuss] About making Text.tag_*range methods more consistent
08.06.14 16:55, Saimadhav Heblikar написав(ла):
I propose that Text.tag_ranges(tag) return a list of tuples (start
index, end index), instead of a list like [start index1, endindex1,
startindex2, endindex2etc]
To be more even more consistent, tag_ranges tuples should contain
indexes similar to the ones returned by tag_prevrange/tag_nextrange i.e.
strings instead of textindex objects.
So, the above output would have been
text.tag_ranges('red')
(('1.0', '1.2'), ('1.6', '1.8'))
If there is a reason for current behavior, can you link me to it?
Tk command returns a list, not a list of pairs.
___
Tkinter-discuss mailing list
Tkinter-discuss@python.org
https://mail.python.org/mailman/listinfo/tkinter-discuss
[Tkinter-discuss] Fixing Tkinter
Please could somebody make a review of patches for Tkinter issues? http://bugs.python.org/issue13153 http://bugs.python.org/issue19020 ___ Tkinter-discuss mailing list Tkinter-discuss@python.org https://mail.python.org/mailman/listinfo/tkinter-discuss
Re: [Tkinter-discuss] Problem with event.widget.grid_info()
08.12.13 13:18, Horace Stoica написав(ла): Not sure this is the place to submit such a query, please re-direct me to the correct place. Report bugs on http://bugs.python.org/. But first test last bugfix releases, perhaps this bug had fixed in 2.7.6 and 3.3.3. I implemented a simple Lights Out game which works with the old Python 2.6 (and 2.7 in Windows). After upgrading to SUSE 13.1 which comes with Python 2.7.5 I get the following error: I guess Tcl/Tk version was changed too. ___ Tkinter-discuss mailing list Tkinter-discuss@python.org https://mail.python.org/mailman/listinfo/tkinter-discuss
