TomSchimansky / TomSchimansky/CustomTkinter
Weird dpi scaling messages
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 13.6k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
after closing an app written with CustomTkinter, a vere easy app, there are sometimes dpi scaling error messages, though not always.
Like these, from 2 different runs, so this seems to be something dynamically generated
invalid command name "2166016445632check_dpi_scaling"
while executing
"2166016445632check_dpi_scaling"
("after" script)
or
invalid command name "2282063737792check_dpi_scaling"
while executing
"2282063737792check_dpi_scaling"
("after" script)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported behavior with a minimal CustomTkinter app that is closed repeatedly, and capture when the dpi scaling messages appear. Investigate the dpi scaling entry point and its shutdown behavior; done means closing the app no longer produces an invalid check_dpi_scaling command.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100