Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

CPTextField setStringValue: behaves strangely when CPTextField is firstResponder

#100

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.

Reported by Nick Takayama · October 9th, 2008 @ 04:36 PM

State: resolved
Milestone: none
Assigned to: nobody

Activity

  1. admin (at 280north)
    admin (at 280north)
    • 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 CPTextField setStringValue: behaves strangely when CPTextField is firstResponder state:resolved] http://github.com/280north/cappu...

    October 9th, 2008 @ 08:16 PM

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.