Thanks, why didn't I think of that? Sounds obvious once known :)
Thanks also for the transient property tip, will keep it at the back of my head
for future use. In this case however I will go with the method as it is more
suitable in my particular case.
Thanks for the tip. However, the value
On Oct 30, 2009, at 3:01 PM, Squ Aire wrote:
Thanks for the tip. However, the value transformer idea did not
work. Even though it ended up showing exactly the same date (the
value transformer just strips the time from the date) for each row,
selecting multiple rows still leaves us with
My last message seems to have messed up newlines. Sorry about that. I will now
try again.
The test app I made contains no code except for the value transformer. The
stuff that is not code is just a Core Data model with one entity called User,
with two attributes name (string) and lastLogin
On 10/30/09 7:01 PM, Squ Aire said:
Thanks for the tip. However, the value transformer idea did not work.
Even though it ended up showing exactly the same date (the value
transformer just strips the time from the date) for each row, selecting
multiple rows still leaves us with Multiple values in
On Fri, Oct 30, 2009 at 1:26 PM, Sean McBride s...@rogue-research.com wrote:
Instead of a value transformer, in your NSManagedObject subclass add a
new method called 'timelessDate' which returns a modified version of
your 'date' attribute. Then bind your table to 'timelessDate' instead
of
On 10/30/09 1:34 PM, Kyle Sluder said:
Instead of a value transformer, in your NSManagedObject subclass add a
new method called 'timelessDate' which returns a modified version of
your 'date' attribute. Then bind your table to 'timelessDate' instead
of 'date'. Also use
Let's say I have a table view bound to an array controller which in turn is
bound to a MOC... you all know how it works.
The table view has two columns: Name and Last Login Date. The thing is that
in underneath in the model, the last login date is stored with both date and
time information.
