Since we’ll be changing future databases to store the data as our own “PIColor”
that can be made into an NSColor/UIColor, the issue isn’t all that important
for long/term/future - but simply backups made already from the last 5 years.
So if there is a way that we can get it working 9 times out
Would it be correct to not care about UIColor or NSColor, encode the data to be
stored in 64 bit NSData, store that and when accessed, decode it?
Sent from my iPad. Please pardon typos.
On Feb 20, 2015, at 2:15 PM, Alex Kac a...@webis.net wrote:
We have a CoreData database on iOS that we want
On Feb 20, 2015, at 11:15 , Alex Kac a...@webis.net wrote:
So with that in mind, has anyone tackled a conversion process of reading in
UIColor data into NSColor via CoreData?
I suspect that *really* solving this is going to be impossible.
When you say “UIColor data”, do you mean the data
That would only work it UIColor and NSColor would encode themselves in exactly
the same way. Any guess what, they aren’t.
Georg
On 20 Feb 2015, at 22:53, Alex Zavatone z...@mac.com wrote:
Would it be correct to not care about UIColor or NSColor, encode the data to
be stored in 64 bit
We have a CoreData database on iOS that we want our users to be able to restore
in our OS X app from backups. It uses UIColor while our desktop app uses
NSColor for now. The correct method for us is to save our color info in a
non-platform specific way…but people have database backups where its
