I want to do a draggable UITableView (this part is working), but when I long press on one row I want to show boxes to change cell's content.
The problem is that long press in editing mode is fired when I am pressing drag or delete button, causing drag event to be stopped. I can't use [[self tableView] isDragging] to ignore long press when I am dragging because it only returns true when I have already dragged far enough.
To summarise I need:
Drag event not to be stopped when long press is fired.
Ignore long press inside drag or delete buttons.
Any ideas?
Related
My question is that i have a UIButton inside my app. When touch it and move my finger outside of button, highlighting continues to specific points around it and then returns back to normal.
My expectation is that when i go to outside of button boundary it should return back to normal immediately.
Do you have any idea for this problem ?
I think you need to target drag event when drags fingers goes out side the boundary of the button it should release the content and here you can check dragoutside event
Triggering a UIButton's method when user drags finger into button's area?
I'm building custom keyboard and i want to make response like stock keyboard.
- I can press and hold on one key and drag to other key and so release, the letter will be enter is the one at current finger position
- Can press and hold one key and use other finger to press on the other key and so 2 letters will be entered at the same time.
I've tried many methods in UIButton ( TouchUpInside, TouchDown, TouchUpOutside ... but didn't successed.
You are going beyond the abilities of UIButton. You need to look at creating a custom view which handles Multitouch Events.
It's not easy, but it's not impossible either.
I have a question about programming my own third-party keyboard for iOS8. My keyboard already looks pretty good, but some functionalities are missing. If you look at the standard keyboard on an iPhone you can press any button and if you swipe your finger to another button, the touch event of the first button gets cancelled and your second button is "active". So e.g. if I press the button "E" and swipe my finger to "R" and release my finger, the letter "R" is the selected one. But I don't know how to implement this.
Now in my app when I press a button and swipe my finger around, this button never gets "released". Seems like I'm stuck on that button as long is I have my finger put on the display.
I think I need these touch events:
TouchUpInside: when the user taps a button, and releases it inside the buttons' frame, this event gets fired (that's when I want to write a letter)
TouchDragInside: That's the event when I already have my finger on the display and swipe my finger "inside" the buttons' frame.
TouchDragOutside: Same as above, just swiping outside the buttons' frame.
But here's the problem: TouchDragInside just get's fired for the button I tap. So when TouchDragOutside gets fired, I have to "release" the button and make the button active where my finger is at the moment.
I hope you understand my question, if you need some further information or some details just let me know.
You could consider not using UIControl at all.
Just use a transparent overlay on top of all the keys so that you can manually deal with which key the message should be dispatched towards.
I have a UIButton whose IBAction has been setup though XIB file. Following is the IBAction method. When I press button multiple times very quickly, this method gets called only once for the last press. I have to wait little more time between the presses. Is there anything like long press time for UIButton that I can reduce or any other settings to make it responding quicker. This button does the similar job of Keyboard's back button to delete last character. I want it to respond very quick like Keyboard's button does. Thanks.
- (IBAction)deleteButtonPress:(id)sender {
NSLog(#"Click");
if(self.numpadTextFiled.text.length > 0)
self.numpadTextFiled.text = [self.numpadTextFiled.text substringToIndex: [self.numpadTextFiled.text length]-1];
}
Is the button by any chance positioned within a UIScrollView? If so, then touches are delayed?
This question already has answers here:
Closed 11 years ago.
Possible Duplicate:
Dismiss keyboard by touching background of UITableView
How do I make the keyboard go away when the user clicks somewhere else?
Note: I know how to make the keyboard disappear with sending the resignFirstResponder command to the UITextField. At present the "Done" button is connected to all the correct code to do this and this works.
I have a UITableView with different UITableViewCells, and if the user moves onto another cell I want the keyboard to disappear.
So what events do I also need to include the resignFirstResponder in, for the keyboard to disappear.
Suppose UITableViewCell A has the UITextField, and UITableViewCell B has a button. If the user presses the button in cell B, then I will need to send the command resignFirstResponder back to the UITextField in cell A. First of all the button has no idea which cell it should sent the command to, and second even if the button did know which cell to send the command to how would it?
There's no trivial way to do this. You can put a transparent set of "shield views" all the way around the text field that take up the rest of the screen, and use any touches on them to dismiss the keyboard.
You can create a generic 'hideKeyboard' method in which you can include all text fields that can be first responders. For example,
-(void) hideKeyboard {
[textFieldName resignFirstResponder];
[textFieldSurname resignFirstResponder];
for (UITextField * txtField in arrTextFields) {
[txtField resignFirstResponder];
}
}
Then, at various sections in your class, depending on the functionality required, call;
[self hideKeyBoard];
This simple method means you won't need to keep track of the individual item that 'has the focus' / first responder status.
How to touch any part of the screen to make the keyboard go away
To touch somewhere outside the UITableView and have the keyboard disappear, place an invisible button on top of the 'touch area' that you want to respond to. Then, simply call [self hideKeyboard] from the touch event for that invisible button. Using IB, drag a new rounded button onto your view, then size it to take up the full size of the screen. Next,drag the button up or down the controls list in the IB document window so that button is behind all text fields and buttons, but in front of anything else (like images etc.). Finally, change the type of the button to 'Custom' to make it invisible, but still respond to events. Now all you have to do is to connect the new button's 'touch up inside' event to trigger the 'hideKeyboard' method.
Additionally, see this post for a brilliant solution to dismiss the keyboard when the above solution doesn't work : stackoverflow question 1823317