The app copies photos from Facebook to the users contact list. By default, it won't replace existing photos, as you may have photos from other sources and it'd be poor to overwrite them (there is a checkbox you can tick to replace the existing photos).
But now there is a problem - when you run the sync again, it should replace the photos it copied last time. Otherwise you run it once, and then it'll never work again because every photo is "original". So I used a database for this. Big mistake. Now I get lots of people saying my app doesn't work, because they used it once, uninstalled it, and now of course it won't overwrite the existing photos by default because the database is gone. I'm hoping to move the database onto the sdcard to solve this problem. I think it's partly an artifact of the G1s limited storage. I suspect Magic users won't be so quick to uninstall apps. On May 3, 3:27 pm, jarkman <[email protected]> wrote: > As a amtter of interest, why do you want your data to survive > uninstall & reinstall ? In the usual run of things, it doesn't seem to > cause trouble with the users. And the ones that really don't want your > app any more will be glad if it cleans itself up completely on > uninstall. > > Richard > > On May 2, 2:48 pm, Mike Hearn <[email protected]> wrote: > > > I wasn't able to find a good, free Java steganography library that can > > survive recompression. I think I'll just store the data on the SD > > card. It's not as nice as having it associated with the contact in the > > contacts db, as the user can delete the database, swap SD cards or buy > > a new phone and the stuff won't work any more. But I don't see other > > options. > > > On May 2, 12:10 pm, Mike Hearn <[email protected]> wrote: > > > > No :( I'm needing to store data about individual contacts. Does > > > anybody else have ideas? I really want to avoid steganography that can > > > survive JPEG recompression, it would be an astonishing amount of suck. > > > > On May 2, 10:12 am, jarkman <[email protected]> wrote: > > > > > The sync process seems to re-encode the jpeg. You'll need to use a > > > > robust steganographic method... :-) > > > > > I had read Contacts.Settings as storing settings for sync accounts, > > > > not settings for individual contacts. Is that what you're after ? > > > > > Richard > > > > > On May 2, 1:00 am, Mike Hearn <[email protected]> wrote: > > > > > > I would like to store some app-specific data in the contacts db. Is it > > > > > safe to stuff random things into the Contacts.Settings table? Will it > > > > > affect the GUI? Does anybody have an example of doing that? It's not > > > > > really clear to me if there's a proper mechanism for this, or if the > > > > > settings table is reserved for the systems own use. > > > > > > BTW my first attempt was to use an app specific database, but then > > > > > users would uninstall the app, reinstall it later and wonder why it > > > > > didn't work. My second attempt was to stuff the data into the JPEG > > > > > headers but the sync process deletes them, presumably for security > > > > > reasons. So if there's no way to store my things in the contacts db > > > > > directly, I think I'm out of luck - I'll have to look at > > > > > steganographically encoding the data into the raw pixels themselves! > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
