Fix: disabled CTkEntry placeholder becoming an actual value - #2863
Open
jackaopen wants to merge 1 commit into
Open
Fix: disabled CTkEntry placeholder becoming an actual value#2863jackaopen wants to merge 1 commit into
jackaopen wants to merge 1 commit into
Conversation
Collaborator
|
Hi, |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
When a CTkEntry with an active placeholder is disabled and clicked, its
placeholder is deactivated. Because the underlying tkinter.Entry cannot delete
text while disabled, the placeholder remains and is returned as an actual value
after the entry is enabled again.
Fix
Prevent placeholder deactivation when the entry state is either
disabledorreadonly.Testing
Verified locally with this sequence:
get()returns an empty string instead of the placeholder.The local regression test passed.