TomSchimansky / TomSchimansky/CustomTkinter
Enhancement request: CTkComboBox button arrow colour
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 13.6k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Description
It would be a useful enhancement if the v-arrow on CTkComboBox widget buttons had an independent property.
Presently CTkComboBox takes the v-arrow colour from the widgets text colour. I have found that this can become problematic when trying to coordinate with other enter-able widget colours. Here is an example. I want the Combo button to be dark, but I also want my ComboBox to be consistent with CTkEntry. Here is where the problem starts. Because the button is dark, it's hard to see the arrow when adopting the text and entry fg_color, and text_color from CTkEntry. Hopefully, you can see what I mean here:
The upshot is, that quite often, you have to compromise and create inconsistent visuals, which might confuse the user into thinking that the combo box is not an enter-able widget, because the fg_color is different than other enter-able widgets. Either that or you can't easily see the v-arrow on the button.
Here is the kind of compromise I generally make:
The other issue which can occur is where the disabled text color is applied to the v-arrow, this can also have negative results, causing the v-arrow to disappear.
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 locating the CTkComboBox implementation and trace how the button's v-arrow colour is obtained from text or disabled text colour. Done means the arrow has an independent configurable colour while preserving the requested dark-button and entry-colour use cases, including disabled widgets.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100