Are you trying to update the Wallpaper from your app? I dont think this is possible. You can however, save an image to the Camera Roll and then have the user pick it for Wallpaper. Check out the App "If Found".
Are you trying to update the Wallpaper from your app? I dont think this is possible. You can however, save an image to the Camera Roll and then have the user pick it for Wallpaper. Check out the App "If Found".
Yes. I was hoping it was possible to allow the user to do it in one step. The closest I have seen is in the Watchmen App, which lets you pick a photo from a screen and "save" it to the photo library. You then obviously have to switch to the Photos App and select it from there to email, wallpaper, etc.
Yes. I was hoping it was possible to allow the user to do it in one step.
Not within the SDK. You can generate an image, save it to the camera roll, but beyond that there's nothing you can do. I've filed an enhancement request with Apple for this functionality.
Not within the SDK. You can generate an image, save it to the camera roll, but beyond that there's nothing you can do. I've filed an enhancement request with Apple for this functionality.
Thanks for this info. Saves me banging my head against the wall trying to do something that's not possible.
I am curious how they are saving the image. Are they able to save the file directly from the application? I am guessing so, since there is a "save" button on top of the image in the application but it doesn't show up in the graphic that ends up in the Camera Roll. I have not seen how to save directly, but if they were saving the View, that "save" button would show up as well and the image quality would be second generation. Right?
I am curious how they are saving the image. Are they able to save the file directly from the application? I am guessing so, since there is a "save" button on top of the image in the application but it doesn't show up in the graphic that ends up in the Camera Roll. I have not seen how to save directly, but if they were saving the View, that "save" button would show up as well and the image quality would be second generation. Right?
I'm doing this in my app - maybe not the best way to do it, but you get the idea:
I'm doing this in my app - maybe not the best way to do it, but you get the idea:
Thanks for sharing this brandons. Am I correct in understanding that you're opening a view that you've populated with an image in Interface Builder, then saving that view? Does this result in saving a second generation image that will be lower quality than the original (e.g. if you told it to save a file from your bundle based on a path name)?
Long story short - there's no Interface builder involved but I'm basically using a scrollview with an imageview in it to allow for manipulation of the image by the user. When they hit the save button I grab that layer, dump it into another imageview and put some labels on it. That is then saved as the final image.
I'm going to re-work this process because its convoluted right now, but it works fine for right now.
To answer your specific question though ... Yes, this would be second generation since its not using the original image data but creating a whole new image from the view. However, if there's any image degradation its minimal from what I can see and for my purposes its not really an issue.
I can't say I'd do the same thing if I was planning on creating works of art =)
Yes, this would be second generation since its not using the original image data but creating a whole new image from the view.
Thanks for the clarification brandons. I'm not using any works of art, but just wanted to make sure I understood what is happening.
What I might do, if I can figure it out, is show a preview of the image on the screen in a view but then tell the button to save the original file. It's not so much that the quality has to be great, but I will have a "save" button on the screen and I don't want it included as part of the image.