NSTextField with an date formatting
-
I have an NSTextField that is bound to a date in a Core Data program.
The text field has an NSDateFormatter attached to it. All connections
are set up using IB. The odd thing is that the user needs to enter
the date into the text field twice for the text field to correctly
update to the new date. Using key value observing, the text field
object correctly updates it's data on the first enter. The text field
simply does not display the new value. Calling setNeedsDisplay or any
other similar method does not do anything. Interestingly, when I
modify the program to add a second text field (ie now have two text
fields, both with date formatters and bound to the same date in Core
Data), when the user changes the date in text field 1, it will result
in text field 2 but not text field 1 correctly updating to the new
date, and vice versa. I suspect this may be a bug, has anyone else
experience anything similar and what is the process of reporting to
Apple if it is a bug?
Kind Regards -
On Sat, 31 Jan 2009 18:04:48 +0000, minapre999 <minapre999...>
said:
>
> I have an NSTextField that is bound to a date in a Core Data program.
> The text field has an NSDateFormatter attached to it. All connections
> are set up using IB. The odd thing is that the user needs to enter
> the date into the text field twice for the text field to correctly
> update to the new date. Using key value observing, the text field
> object correctly updates it's data on the first enter. The text field
> simply does not display the new value. Calling setNeedsDisplay or any
> other similar method does not do anything. Interestingly, when I
> modify the program to add a second text field (ie now have two text
> fields, both with date formatters and bound to the same date in Core
> Data), when the user changes the date in text field 1, it will result
> in text field 2 but not text field 1 correctly updating to the new
> date, and vice versa. I suspect this may be a bug, has anyone else
> experience anything similar and what is the process of reporting to
> Apple if it is a bug?
Can you reduce the problem to a little tiny project and show it? m.
--
matt neuburg, phd = <matt...>, <http://www.tidbits.com/matt/>
A fool + a tool + an autorelease pool = cool!
One of the 2007 MacTech Top 25: <http://tinyurl.com/2rh4pf>
AppleScript: the Definitive Guide - Second Edition!
<http://www.amazon.com/gp/product/0596102119> -
I put together a tiny little project & it actually behaves perfectly
as it is supposed to! As far as I can tell it is identical to my
current project exept it just has the one entity with one attributes
and one window with a table view of dates and a couple of text
fields. The text fields and the table view are hooked up to the MOC
via binding in an identical manner to my main project, so I am stumped
on this one. Meanwhile I have a workaround for the immediate problem
(two text fields, one on top of the other, one hidden, one not, when
the user sets the date in the text field then it becomes hidden and
the other one becomes visible).
Peter F
On 1 Feb 2009, at 17:20, Matt Neuburg wrote:
> On Sat, 31 Jan 2009 18:04:48 +0000, minapre999 <minapre999...>
>>
> said:
>>
>> I have an NSTextField that is bound to a date in a Core Data program.
>> The text field has an NSDateFormatter attached to it. All
>> connections
>> are set up using IB. The odd thing is that the user needs to enter
>> the date into the text field twice for the text field to correctly
>> update to the new date. Using key value observing, the text field
>> object correctly updates it's data on the first enter. The text
>> field
>> simply does not display the new value. Calling setNeedsDisplay or
>> any
>> other similar method does not do anything. Interestingly, when I
>> modify the program to add a second text field (ie now have two text
>> fields, both with date formatters and bound to the same date in Core
>> Data), when the user changes the date in text field 1, it will result
>> in text field 2 but not text field 1 correctly updating to the new
>> date, and vice versa. I suspect this may be a bug, has anyone else
>> experience anything similar and what is the process of reporting to
>> Apple if it is a bug?
>
> Can you reduce the problem to a little tiny project and show it? m.
>
> --
> matt neuburg, phd = <matt...>, <http://www.tidbits.com/matt/>
> A fool + a tool + an autorelease pool = cool!
> One of the 2007 MacTech Top 25: <http://tinyurl.com/2rh4pf>
> AppleScript: the Definitive Guide - Second Edition!
> <http://www.amazon.com/gp/product/0596102119>
>
>
>
