i get confuse in apply and save button. whether Save will save the settings. Apply will save and apply the settings or apply will save the setting for instance or what?
This is a good explanation, it's for joomla 1.5 but it's the same principle:
http://www.ostraining.com/blog/joomla/joomla-save-and-apply-buttons/
"Save" saves your changes and forces you out of the current screen
Apply" saves your changes but keeps you on the current screen
Related
On iOS, my requirement is disallow user to take manual screenshot from my application, either disallow or blur the captured screenshot. How?
The only solution is to simulate the iOS controls you have in your View using DRM'ed videos.
For each widget you need to create a video subclass that renders the widget, and apply DRM to the video.
You can try to do it yourself, or use a commercial solution such as the following:
https://screenshieldkit.com
It is possible but I don't recommend it because of the room for error. It was easier to do in the past, in iOS13 you will have to do it like this:
You will have to ask for the user's permission to read and edit their photo library, then you have a listener which is checking the number of photos in their library while they are using your app, if that number changes, they have just taken a screenshot (unless you allow other things in your app like tap and hold to save image, etc). When this happens, read said photo and apply a blur, then delete the photo from their library and save the blurred photos.
Warning: There are times where a user may get a photo while using your app that is not a screenshot (e.g. they received an airdrop) and you will now be tampering with their photos, which is very bad. To prevent this you may need to use key value pixel encoding on your screen at all times, for example the first 3 pixels of the screen are 3 very specific RGB values, that way if a new photo is detected and the first 3 pixels are those exact RGB values you know it's a screenshot of your app and not just another photo that was somehow saved while the user was using the app.
There isn't any regular solution to your problem!
You can do some tricks such as if you force the user to have their finger on the screen for the image to show then I don't think they can create screenshots. Because as soon as you press the home+lock keys to actually take the screenshot, the screen seems to behave as if there are no fingers touching it.
BUT what if the user takes a screenshot by AssistiveTouch?!
OR what do you want to do if user records screen and taking screenshot from the video?
I think it's better to change your strategy for example notify the owner of picture for taking screen shot by another one (like SnappChat)!
I have a view which has images, this images are added by the user, once the user decide the image to add, the user drag the image to a specific position in the screen, the number of images is completely dynamic.
What I want is to save in a file, an array or whatever you suggest the view with the images for lately the user could edit the images or positions.
I'm not asking for code I just want a hint for accomplish what I need. What do you think is the best way to archive this?
Thank you all!
If you want to exit the app use NSUserDefaults to save it and use later.
If you are not going to exit you can set a global NSMutableArray and add the UIImageViews for later use.
I have been searching the net for a while, but can't seem to find an answer, so hopefully someone in here will know.
I am using TweetSheet & FacebookSheet for users to post their scores after a game. I have the initial text set there with some text and their score, but the user is able to edit this message, meaning they could easily write whatever score they want in there. Is there a way to stop the user from being able to edit my initial text?
Thank you
No, you have no control over the user editing your default text when using the sharing sheet. As soon as you present the sheet, the user can change the text to whatever he wants. If you must make a post with immutable content (not recommended, for the user's sake), look into making an SLRequest.
I am writing an iPhone app. My next step is to create a card object. I know how to do this theoretically, but my problem is coming from my lack of experience in Xcode.
This is my add item page
I want the user to specify a name and then choose an icon, either from the 3 most popular choices, another page of premade options, or take their own picture and use that.
Now, how do I show those choices in a way that the user can select one and I can collect their response? Right now, they are simply buttons, I can add my background image to them, but I don't know how to record their response. I would like it to show them their selection by adding that shadow around the box.
I'm not sure if a button is the best approach.
Also, I will need the same selection behavior for the image they take themselves, but I figure if I get the icon choices to work, I can figure out using a picture taken by the user.
Thanks for any help.
I would create button "Select image" below the uiimageview.
This button would present action sheet where you would have two options
a) select form existing
b) take a picture.
Then I would probably use Grid view to present the existing icons and UIImagePicker for taking pictures :)
I am working with a small camera app for a client and I have now finished all functionality of it. In the standard camera controls i need to modify one thing , the cancel button should say gallery instead.
But unless i am missing something i will need to remove the overlay by setting showsCameraControls to NO and then building my entire overlayView from scratch.
I have found this solution but I am afraid to go this route due to the warning in the beginning of the post.
So is there any valid way of doing simple small modifications to the existing camera overlay control UI or do you have to build it from scratch if you need to change one tiiiiiiny thing?
Unfortunately, having been in this situation I can safely say you need to build the controls from scratch. You really only have two options: create your own camera overlay, or use the default one.
Now, you could use the techniques described in the link you cite, and iterate through the various subviews and modify them 'blind'. The rather large danger with this is every time Apple change the internal structure of the image picker it could potentially break your solution. So I'd definitely stay clear of it.