CPTextField setStringValue: behaves strangely when CPTextField is firstResponder
Reported by Nick Takayama | October 9th, 2008 @ 04:36 PM
A CPTextField that is editable will render both old and new values over the top of eachother when a user is editing it and some code calls to [_textField setStringValue:].
This is because the setStringValue: method does not take the DOM input element into account when re-rendering.
I've attached a git email formatted patch for this, which is just 7 lines of code.
Comments and changes to this ticket
-
admin (at 280north) October 9th, 2008 @ 08:16 PM
- State changed from “new” to “resolved”
(from [c2b1130e23182bab14493d475b2163caad6efa24]) Fix for setStringValue on CPTextField being broken if first responder.
First commit by Nick Takayama! Thanks!
[#100 state:resolved] http://github.com/280north/cappu...
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
The Cappuccino Web Framework, including AppKit, Foundation, and Objective-J.
People watching this ticket
admin (at 280north)
Nick Takayama
Attachments
Referenced by
-
100
CPTextField setStringValue: behaves strangely when CPTextField is firstResponder
[#100 state:resolved]
http://github.com/280north/cappu...